Changes between Version 5 and Version 6 of GUIGuide


Ignore:
Timestamp:
Mar 10, 2011, 10:53:21 AM (9 years ago)
Author:
Luke
Comment:

Add Finger Friendliness section, Do some formatting

Legend:

Unmodified
Added
Removed
Modified
  • GUIGuide

    v5 v6  
    55= SHR GUI Guide =
    66
    7 Hopefully this guide will help you design better graphical user interfaces for small screens, namely when the window manager behaves as Enlightenment (with Illume2).
     7This guide has information on how to create graphical user interfaces for small screens, namely when the window manager behaves as Enlightenment (with Illume2).
    88
    9 == No UI Clutter! ==
     9
     10
     11= Clear Design =
    1012
    1113Whenever possible, try to hide buttons, toolbars, and other unimportant GUI elements.
     
    2325See [#TouchingEvents Touching Events] for some more suggestions.
    2426
    25 == No Close Button! ==
     27== No Close or Quit Buttons ==
    2628
    27 Do not use a close button. It will only hurt the [#NoUIClutter No UI Clutter] principle. SHR has a softkey which will provide as a nice way to close windows. It's that X!
     29'''Do not use a close button.''' It will only hurt the [#NoUIClutter No UI Clutter] principle. SHR has a softkey which will provide as a nice way to close windows. It's that X in the picture below:
    2830
    29 [[Image(shr_elm_softkey.png,align=center,150px)]]
     31[[Image(shr_elm_softkey.png,align=center,150px)]][[BR]]
     32[[BR]]
    3033
    31 === What About a Quit Button? ===
     34'''Do not use a quit button.''' Unless your application has several windows, they won't help a lot. If you do have one such button, make it really quit, not just close the window.
    3235
    33 That too. Unless your application has several windows, a quit button won't help a lot. If you do have one such button, make it really quit, not just close the window.
     36[[BR]]
    3437
    35 == Touching Events ==
     38= Touch =
    3639
    37 Use press and hold (click and hold) events for popupping up stuff. Preferably contextual stuff to *where* one presses.
     40== Finger Friendliness ==
     41
     42
     43Keep in mind that most handsets today (e.g. htcleo, nexusone in SHR) have '''capacitive touchscreen''' which require finger friendliness from the GUI. Please '''do not include very small surfaces''' and '''avoid surfaces that have small borders to neighboring surfaces'''. When developing on a device with resistive TS please do not forget that -it will allow for broader use of your program.
     44
     45
     46The current SHR on screen keyboards are a good example of what to not do. '''An additional keyboard layout must be created''' to suite the needs of devices with capacitive touchscreens. See this example:
     47http://www.androidtapp.com/wp-content/uploads/2008/12/chompsms-on-screen-keyboard-type.jpg
     48
     49
     50== Touch behavior ==
     51
     52
     53Use press and hold (click and hold) events for popping up stuff. Preferably contextual stuff to *where* one presses.
    3854
    3955Use touch events (click) for showing up hidden stuff in certain areas (like [#NoUIClutter No UI Clutter]).
    4056
    41 == Gesture ==
     57
     58== Gestures ==
    4259
    4360When possible, use gestures that make sense (eg, viewing images, swipe in a direction for previous, the other for next).
     61
     62
     63''Idea: Implement Ubuntu's gesture API''