• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • paul wheaton
  • Paul Clapham
  • Ron McLeod
Sheriffs:
  • Jeanne Boyarsky
  • Liutauras Vilda
Saloon Keepers:
  • Tim Holloway
  • Carey Brown
  • Roland Mueller
  • Piet Souris
Bartenders:

Command Type

 
Ranch Hand
Posts: 147
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
It seems to me that the Command Type like BACK, STOP, EXIT... don't have any control or default behavior, except they may only have the device dependent soft-key mapping for the Command Type. But nothing for the implementation. So I can use the "STOP" type to implement the start action, or "EXIT" to implement the "OK" action. Sounds ridiculous, but it's possible. Correct me if I am wrong.
 
Ranch Hand
Posts: 3178
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yes you are right. They are device-dependent implementation...
 
Ranch Hand
Posts: 51
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Alibabra , This is what I have noticed as well.
 
Ranch Hand
Posts: 379
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
This is quite true.

Since the way a command is represented in a device is device-specific, due to the varied implementations, I guess the creators wisely chose a Command object along the lines of the classical COMMAND pattern.

As per the spec and javadoc, the intention of the constants is to 'suggest' to the device on which position to place the command (aka button). In many phones, the Exit button always is placed on the right-side and the menu button is always placed on the left side.

So, if you want your users to feel comfortable with your application, you should use the appropriate constants to ensure that the commands of your application are placed in appropriate places where the users are used to seeing those commands. If you defy them and use them willy-nilly, while it might amuse you, it might not amuse your users

The priority value, on top of the constants, can be used to decide the relative position of the command (highest priority button more accessible than the lowest priority button) to help in usability.

I guess these are unique considerations for a screen-restricted device such as a cell phone where screen space is at a premium.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic