The following couple of months will be frigid icy for a large portion of us, yet we'll oppose wearing gloves in light of the fact that it implies we won't have the capacity to utilize our iPhones while we're out on the town. Luckily, this may not be an issue with future Apple gadgets.
Another Apple patent distributed by the U.S. Patent and Trademark Office uncovers the organization has been attempting to make the iPhone's showcase perfect with gloves. In a recording titled "Glove Touch Detection," Apple depicts a showcase that can distinguish touch info through specific boundaries.
"Notwithstanding utilizing a sign thickness make limit to distinguish a data patch as touching the surface, a sign thickness soundness edge can be utilized to recognize the information patch as touching the surface," Apple clarifies.
This implies you won't need to draw off your glove to answer to instant messages, snap a photo, or answer an approach your iPhone — or purchase unique touchscreen gloves. It would likewise permit you to utilize your gadget with swathes or mortars on your fingertips.
Apple wouldn't be the first organization to do this, obviously. Truth be told, the Cupertino organization is really late to the gathering, with adversaries like Samsung as of now offering elements that permit their gadgets to be utilized with gloves on. Ideally it won't take Apple too long to make up for lost.
Thursday, November 26, 2015
Monday, November 16, 2015
Samsung Galaxy Android 6.0 Marshmallow Update Roadmap leaked
The newest version of the Android platform-- the Android 6.0 Marshmallow --was introduced to the world earlier than expected. We speculated what the new sweet dessert 'M' would be and it turned out to be the fluffy Marshmallow. The mobile OS is slowly rolling out after the latest Nexus phones were launched by Google. Following the Nexus 6P and the Nexus 5X, several companies have also announced when they will be rolling out Android 6.0 to their devices in different markets.
Mobile carriers are also making their announcements so we know that the "flufiness" is out there. One of the top brands expected to push this important update to its products isSamsung because it's the top Android device maker today. Its numbers may be declining but the South Korean giant still has captured a large percentage of the mobile market not only in the US but in major regions.
Unfortunately, Samsung has not made any formal announcement regarding the update. The likes of HTC, Huawei, Sony, and Motorola have been very eager with the updates. As for Samsung, we have yet to hear from the company but here is an exclusive information shared by Times News.
Check out the Samsung Galaxy Android Marshmallow update schedule below:
According to Times News, Samsung will push the updates in two phases. During Phase 1, the following Galaxy Devices will receive the Marshmallow update: Samsung Galaxy Note 5, S6 Edge+, S6, S6 Edge, Note 4, Note Edge, S5, and Galaxy Alpha. The last two models are still waiting for approval while the rest have already been approved. Updates will be released anytime between December 2015 to February 2016.
During Phase 2, the lower specced Samsung Galaxy devices will get a taste of Android 6.0 Marshmallow: Samsung Galaxy A8, A7, A5, A4, E7, and E5. All updates are still waiting for approval so no information on release date yet.
This roadmap doesn’t include Phase 3 but initial testing is expected to begin soon. Let's wait for the official announcement from Samsung. It's happening very soon. Just. You. Wait.
Mobile carriers are also making their announcements so we know that the "flufiness" is out there. One of the top brands expected to push this important update to its products isSamsung because it's the top Android device maker today. Its numbers may be declining but the South Korean giant still has captured a large percentage of the mobile market not only in the US but in major regions.
Unfortunately, Samsung has not made any formal announcement regarding the update. The likes of HTC, Huawei, Sony, and Motorola have been very eager with the updates. As for Samsung, we have yet to hear from the company but here is an exclusive information shared by Times News.
Check out the Samsung Galaxy Android Marshmallow update schedule below:
According to Times News, Samsung will push the updates in two phases. During Phase 1, the following Galaxy Devices will receive the Marshmallow update: Samsung Galaxy Note 5, S6 Edge+, S6, S6 Edge, Note 4, Note Edge, S5, and Galaxy Alpha. The last two models are still waiting for approval while the rest have already been approved. Updates will be released anytime between December 2015 to February 2016.
During Phase 2, the lower specced Samsung Galaxy devices will get a taste of Android 6.0 Marshmallow: Samsung Galaxy A8, A7, A5, A4, E7, and E5. All updates are still waiting for approval so no information on release date yet.
This roadmap doesn’t include Phase 3 but initial testing is expected to begin soon. Let's wait for the official announcement from Samsung. It's happening very soon. Just. You. Wait.
Wednesday, November 11, 2015
HTML5 Native Drag and Drop API
Everybody cherishes a simple to-utilize and intelligent client interface and following the time when the presentation of cell phones there has been a bounce in desires from clients; The desire is that your site will be instinctive, will utilize all around comprehended activities, and general demonstrating a simple approach to draw in with your site.
Giving your clients the capacity to drag, drop, and sort makes your site more instinctive as individuals see how to move component X to position Y and that moving item A before article B makes protest A start things out.
Taking care of dragging, dropping, and sorting has dependably been an errand for JavaScript and engineers have beforehand had the choice of building their own particular cooperations or to utilize a prebuilt arrangement . With the approach of the HTM5 Drag and Drop API , engineers will have the capacity to guide into local occasions and credits to handle these connections.
A Brief Introduction
Gives up through the API so we can get an outline of how everything functions.
The local API gives us a chance to characterize components that are draggable by utilizing the draggable="true" characteristic on your wanted components. A few components are as a matter of course draggable even with no adjustments, (for example, pictures or content).
As a matter of course when draggable components are dragged, just shape components, for example, info will have the capacity to acknowledge them as a drop. You would have seen this before; on the off chance that you select some content and drag it into a textarea the content is duplicated into the textarea component.
The local API likewise handles drags from outer zones on your OS onto your drop zones. All great Content Management Systems give move and customize transferring of substance. Since these components are outer, everything you need to design is the drop zone (furthermore have a perfect program).
Move and customize API Events
The local API gives the accompanying occasions that you can listen for. These occasions will apply to either the draggable thing or the drop zone and will be activated at set times.
At the point when these occasions are let go, we have entry to a neighborhood item (which we will call occasion ). This article holds more data about the occasion itself and will give you access to the dataTransfer item where you will set the majority of your strategies and properties.
Drag-related Events
These occasions are activated just on draggable things.
dragstart Triggered when we begin dragging. It's here we should inform the API concerning what we will be dragging and set up different qualities. Utilize the setData() technique to set the information you need to spare, set the effectAllowed property for the draggable component, and characterize the draggable aide with setDragImage() .
drag This occasion is activated constantly amid dragging. The quantity of times it happens relies on upon the program. This is helpful for deciding precisely where the draggable thing is.
dragend This is occasion fires when the draggable is dropped (paying little mind to where it is dropped) and for the most part activated straightforwardly after the drop zone's drop occasion. You can utilize this occasion to reset styles connected while dragging or to perform other cleanup activities. The dragend occasion has admittance to the draggable so you can do computations subsequent to dragging has finished (for instance looking so as to check whether the drop occasion was effective for recently included components and afterward uprooting the first draggable).
Drop-related Events
These occasions are activated just on components that you determine as drop targets (or are as of now actually drop targets, similar to frame components):
dragenter Triggered only once when a draggable enters a droppable zone. This will trigger when more than half of the draggable is inside the drop zone.
This occasion sets the dropEffect of the drop zone. Of course drops on non-structure components won't do anything. You should physically call event.preventDefault() and event.stopPropagation() to tell the API this drop ought to occur.
You can check the dataTransfer item for the effectAllowed esteem that has been set by the draggable and after that contrast it with the quality your drop zone has for its dropEffect . In the event that these qualities won't cooperate (i.e one is duplicate and the other is connection ) then the program won't drop the thing effectively (regardless of the fact that you counteracted defaults and halted proliferation).
You can utilize the sorts property to get a rundown of all information sorts that have been set in the dragstart occasion. You can't see the information however you can see its sort. It's here you can utilize another system called contains to check whether a sure sort of information has been set up. This is done by means of the event.dataTransfer.types.contains(type) technique. You could utilize this to guarantee that something has been set to the content/html sort for instance.
You can set classes or trigger activities now that you know your draggable has gone into the drop zone (a typical subject is to style the drop zone diversely to demonstrat to it is being actuated).
dragover This occasion is basically the same as dragenter yet it is called consistently while the draggable thing is inside the drop zone. This occasion is immaculate on the off chance that you need to decide the definite position of the draggable (in light of the fact that it is overhauled consistently).
This occasion sets the dropEffect of the drop zone and, as dragenter , you should forestall default and spread.
dragleave This is activated once a draggable has moved far from a drop zone. It's by and large used to evacuate styles included either the dragenter or dragover occasions and flames once the draggable is not covering with the drop zone.
drop This occasion is activated once the draggable has been discharged and the drop territory consents to acknowledge the drop. This will just fire if the draggable component and the drop range have right dropEffect and effectAllowed values. On drop you should gather the data utilizing the getData() technique.
Giving your clients the capacity to drag, drop, and sort makes your site more instinctive as individuals see how to move component X to position Y and that moving item A before article B makes protest A start things out.
Taking care of dragging, dropping, and sorting has dependably been an errand for JavaScript and engineers have beforehand had the choice of building their own particular cooperations or to utilize a prebuilt arrangement . With the approach of the HTM5 Drag and Drop API , engineers will have the capacity to guide into local occasions and credits to handle these connections.
A Brief Introduction
Gives up through the API so we can get an outline of how everything functions.
The local API gives us a chance to characterize components that are draggable by utilizing the draggable="true" characteristic on your wanted components. A few components are as a matter of course draggable even with no adjustments, (for example, pictures or content).
As a matter of course when draggable components are dragged, just shape components, for example, info will have the capacity to acknowledge them as a drop. You would have seen this before; on the off chance that you select some content and drag it into a textarea the content is duplicated into the textarea component.
The local API likewise handles drags from outer zones on your OS onto your drop zones. All great Content Management Systems give move and customize transferring of substance. Since these components are outer, everything you need to design is the drop zone (furthermore have a perfect program).
Move and customize API Events
The local API gives the accompanying occasions that you can listen for. These occasions will apply to either the draggable thing or the drop zone and will be activated at set times.
At the point when these occasions are let go, we have entry to a neighborhood item (which we will call occasion ). This article holds more data about the occasion itself and will give you access to the dataTransfer item where you will set the majority of your strategies and properties.
Drag-related Events
These occasions are activated just on draggable things.
dragstart Triggered when we begin dragging. It's here we should inform the API concerning what we will be dragging and set up different qualities. Utilize the setData() technique to set the information you need to spare, set the effectAllowed property for the draggable component, and characterize the draggable aide with setDragImage() .
drag This occasion is activated constantly amid dragging. The quantity of times it happens relies on upon the program. This is helpful for deciding precisely where the draggable thing is.
dragend This is occasion fires when the draggable is dropped (paying little mind to where it is dropped) and for the most part activated straightforwardly after the drop zone's drop occasion. You can utilize this occasion to reset styles connected while dragging or to perform other cleanup activities. The dragend occasion has admittance to the draggable so you can do computations subsequent to dragging has finished (for instance looking so as to check whether the drop occasion was effective for recently included components and afterward uprooting the first draggable).
Drop-related Events
These occasions are activated just on components that you determine as drop targets (or are as of now actually drop targets, similar to frame components):
dragenter Triggered only once when a draggable enters a droppable zone. This will trigger when more than half of the draggable is inside the drop zone.
This occasion sets the dropEffect of the drop zone. Of course drops on non-structure components won't do anything. You should physically call event.preventDefault() and event.stopPropagation() to tell the API this drop ought to occur.
You can check the dataTransfer item for the effectAllowed esteem that has been set by the draggable and after that contrast it with the quality your drop zone has for its dropEffect . In the event that these qualities won't cooperate (i.e one is duplicate and the other is connection ) then the program won't drop the thing effectively (regardless of the fact that you counteracted defaults and halted proliferation).
You can utilize the sorts property to get a rundown of all information sorts that have been set in the dragstart occasion. You can't see the information however you can see its sort. It's here you can utilize another system called contains to check whether a sure sort of information has been set up. This is done by means of the event.dataTransfer.types.contains(type) technique. You could utilize this to guarantee that something has been set to the content/html sort for instance.
You can set classes or trigger activities now that you know your draggable has gone into the drop zone (a typical subject is to style the drop zone diversely to demonstrat to it is being actuated).
dragover This occasion is basically the same as dragenter yet it is called consistently while the draggable thing is inside the drop zone. This occasion is immaculate on the off chance that you need to decide the definite position of the draggable (in light of the fact that it is overhauled consistently).
This occasion sets the dropEffect of the drop zone and, as dragenter , you should forestall default and spread.
dragleave This is activated once a draggable has moved far from a drop zone. It's by and large used to evacuate styles included either the dragenter or dragover occasions and flames once the draggable is not covering with the drop zone.
drop This occasion is activated once the draggable has been discharged and the drop territory consents to acknowledge the drop. This will just fire if the draggable component and the drop range have right dropEffect and effectAllowed values. On drop you should gather the data utilizing the getData() technique.
Subscribe to:
Comments (Atom)