View Single Post
Texrat's Avatar
Posts: 11,700 | Thanked: 10,045 times | Joined on Jun 2006 @ North Texas, USA
#183
Originally Posted by ragnar View Post
But... I guess the problem might not be self-evident for somebody who has not done designs on this area, but what exactly would you control with the d-pad?

You're talking for instance about navigating in menus. That assumes that there is a focus element on screen. Look at the iPhone UI, for instance. There is no focus element there. For a proper touch UI, you shouldn't have a focus element.

A traditional UI style is to have focus elements and then means to move this focus element around; first click to move the focus to position on screen, second click to confirm. Another style is to have no focus on lists and menus: first click always selects whatever you click. But you can't really mix these styles together very well.
I was completely with you until that last statement ragnar.

The question is, why not?

Why can't there be contextual info that determines whether the UI is presently modal or non-modal? Why can't I have a pure touch experience (ie, no focus elements) for the most part but then a change to a modal/focus approach when a specific app or usage demands it?

As a huge proponent of contextual UIs I'm discouraged by the Maemo OS retreat from certain aspects (such as abandonment of the finger-vs-stylus detection). In fact I'm convinced that, more than any other input experience, touchscreens MUST make high use of contextual elements.

So... why not?
__________________
Nokia Developer Champion
Different <> Wrong | Listen - Judgment = Progress | People + Trust = Success
My personal site: http://texrat.net

Last edited by Texrat; 2009-01-11 at 18:12.
 

The Following 2 Users Say Thank You to Texrat For This Useful Post: