#touch ui

[aemclub-blog]

How to fetch current resource path in Datasource ?

Need to fetch the current component resource path in repository, use below code in your datasource file

String suffix = slingRequest.getRequestPathInfo().getSuffix(); if (suffix==null){ return; } Resource res = resourceResolver.getResource(suffix); if(res == null) { return; } log.info("Path {}", res.getPath());

 View On WordPress

[dragoni]

Follow these guidelines for designing touch-based interactions on mobile and tablet devices to increase application usability and user enjoyment.

So how big should you make the touch targets on a touch UI?

The MIT Touch Lab study of “Human Fingertips to Investigate the Mechanics of Tactile Sense” found that the average human finger pad is 10–14mm and the average fingertip is 8–10mm.

That means the magic number is 10mm.

Most users can comfortably and reliably hit a 10mm by 10mm touch target. Different mobile platforms express this size recommendation differently, however.

For example, in the iPhone Human Interface Guidelines, Apple recommends a minimum target size of 44 pixels by 44 pixels (88px on retina display) or about 8mm round. Since physical pixel size can vary by screen density, Apple’s pixel specifications apply best to the iPhone’s 320 by 480 pixel, 3.5-inch display (164ppi). Since the release of the iPhone 4’s retina display (326ppi), Apple has updated these specs to points instead of pixels.

In the “Windows Phone UI Design and Interaction Guide,” Microsoft suggests a recommended touch target size of 9mm/34px, and a minimum touch target size of 7mm/26px. Since different phone platforms will have different guidelines, it’s best to check with the platform’s specifications and design accordingly. However, regardless of platform, a minimum touch target of 10mm x 10mm is a good estimate/rule of thumb to apply to all your touchscreen designs (see Figure 8.5). For desktop designers, this will feel ridiculously large—toy-like even! But have faith, it’s important to make touch targets easy for users to engage with.

[aemclub-blog]

Touch UI dynamic selection of multiple drop downs in AEM 6.1

Touch UI dynamic selection of multiple drop downs in AEM 6.1

This articles show the use case of have multiple chained drop down in Touch UI. Values in the next drop down depends on what has been selected on previous one. 

Brief on how it works:-

There are two drop downs with name Language and Country. When you select a Language from drop down, Country down down gets populated with the name of the countries using that language. For example if you select…

View On WordPress

[aemclub-blog]

Implement DataSource for drop down using Sightly AEM 6.1

Implement DataSource for drop down using Sightly AEM 6.1

In Touch UI component, DataSource is very useful when it comes populate drop down dynamically. This article will help you to understand how datasource can be used with Sightly and leaving JSP behind.

Let’s get started with authoring…

Component contains a simple drop down, values for this will be populate dynamically using DataSource.

Here is the code used…

1. DataSource is present…

View On WordPress

[dragoni]

Touch UI with LukeW

applies to mobile as well

In the Windows design guidelines, Microsoft outlines a couple minimum thresholds for what makes a control touchable. More precisely, they recommend applications use controls that are at least 23 by 23 pixels in order to be touchable. That translates to about 6mm by 6mm in physical dimensions. This size is important for reducing the number of errors when we try to hit targets with our fingers.

...

Touchable is different than touch-enabled. For touch enabled controls, we generally want to make things bigger. That is, we are aiming for around 10mm in physical size for our touch targets. This number isn't arbitrary. It comes from studies which found the size of the average human finger pad is 10-14mm and the average human fingertip is 8-10mm. It's especially important for commonly used controls and elements that could result in significant errors if touched erroneously to fit in the 10mm range -sometimes even bigger. For both touchable and touch-enabled controls, we need to consider the spacing between targets as well. A minimum of 2mm of space between targets should do the trick.

Why is touch target size such a big deal? Taking a look at the number of errors that occur per touch target size reveals that when touch targets get too small , that is when they fall below the 7mm marker, error rates shoot up. And as you get smaller and smaller touch target sizes, error rates climb higher and higher. Obviously we don't want people making errors in our software - that's a recipe for frustration. So sizing controls appropriately for touch is an important consideration.

And before you assume it's just people with large fingers that have problems with touch target sizes, consider that many of our current interfaces are too small even for a baby's finger size. Much less a basketball players or the average human index finger width of 11mm.

[dragoni]

MIT Invents A Shapeshifting Display You Can Reach Through And Touch

We live in an age of touch-screen interfaces, but what will the UIs of the future look like? Will they continue to be made up of ghostly pixels, or will they be made of atoms that you can reach out and touch?

At the MIT Media Lab, the Tangible Media Group believes the future of computing is tactile. Unveiled today, the inFORM is MIT's new scrying pool for imagining the interfaces of tomorrow. Almost like a table of living clay, the inFORM is a surface that three-dimensionally changes shape, allowing users to not only interact with digital content in meatspace, but even hold hands with a person hundreds of miles away. And that's only the beginning.

[conormusic]

London-based creative design and invention studio Dentaku has developed a small device that allows users to create their own musical instruments out of everyday items.

The Ototo is a simple printed circuit board (PCB) synthesizer that combines sensors, inputs and touchpads as a means of producing sounds. The device can be used as a keyboard straight out of the box or can be attached to conductive materials using crocodile clips to create entirely new instruments.

The sounds produced by the Ototo can be manipulated by connecting electronic modules to its sensors. By way of example, Dentaku suggests that it can be used to create a "light theremin" that uses a light sensor to control the pitch of the sound. Other suggestions include making an electric drum kit out of saucepans or origami that “sings when touched.”

source

[gadzets-blog]

New Post has been published on Gadzets.Net-The ultimate resource for gadget information

New Post has been published on http://www.gadzets.net/nokia-asha-501-is-now-shipping-in-select-asian-countries/

Nokia Asha 501 is now shipping in select Asian countries

Nokia has announced that the Asha 501 is now shipping in select Asian markets. The phone is now on sale in Thailand and Pakistan and will be releasing in India shortly. The phone will eventually go on sale in other parts of the world, including Europe, the Middle East and Africa, Asia-Pacific and Latin America. The Asha 501 is based on Nokia’s new Nokia Asha software platform that brings some smartphone functionalities to a traditional feature phone. It has a 3.0-inch, QVGA touchscreen, 3.2 megapixel camera, Bluetooth, Wi-Fi, expandable memory, FM radio and dual-SIM support. The phone also comes with removable colors with multiple color choices.