Skip to main content

Submenu

4 replies [Last post]
Anonymous

Hi all
is there a simple way to implement submenu in command menu ?
Thanks
[att1.html]

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
vprise
Offline
Joined: 2003-11-07
Points: 0

I added instructions to the blog about implementing your own sub menu support and some preface explanation on why we think this is bad:
http://lwuit.blogspot.com/2008/07/shoot-yourself-in-foot-using-sub-menus...

Thanks,
Shai.

copprhead
Offline
Joined: 2007-11-29
Points: 0

For me too this would be very helpful. More complex applications are hard to implement with just one level of menu commands or the menu would get very large. One of the reasons why I'm using Polish is exactly that feature.

Shai, if you can describe why it's not a good idea to have submenus and you have a solution for screens/apps requiring many different menu commands (that could be grouped nicely), please explain.

Shai Almog

> Shai, if you can describe why it's not a good idea to have submenus
> and you have a solution for screens/apps requiring many different
> menu commands (that could be grouped nicely), please explain.

Generally nested menus are very hard to navigate on some devices you
need to explicitly click where on others you just pause on the nested
menu for a while (really annoying).
Nesting in general is considered bad user interface design talk to
any user interface expert about directories and files and you won't
hear the end of it. On the desktop we don't have much choice due to
the complexity of the general environment but on a device there is a
limit to how many features can be crammed to a single phone.
Nested menus don't work well with the dial pad and generally confuse
the novice user who finds them very hard (and annoying) to navigate.

Solutions should be used on a case by case basis:

1. Unify commands: rather than have a command go into a nested menu
have the command prompt you with a dialog which is pretty much the
same thing only clearer. In the dialog you can put a list of options
or buttons. Much simpler.

2. Remove commands: I can't see why people need that many command in
a cellular application... Commands are added for every conceivable
option which is cluttered and unhelpful.

3. Build additional forms: Fewer commands but more forms make the
application clearer, split it up rather than concentrate all of your
logic (and commands) in one huge form.

4. Use buttons: since the trend towards finger based touch screens is
very strong menus are really inconvenient with such UI's and nested
menus would be even worse. Buttons OTOH work great with touch screen,
are immediately visible and accessible.
In fact for this reason alone one early LWUIT reviewer chastised us
for having commands at all!

As I said we might add nested menus in the future against my better
judgement since customers have asked for it and we generally support
shooting yourself in the foot if you do so desire ;-)

For me the really annoying thing about adding a feature like that is
that it must be added to the core of LWUIT thus increasing the size
of all LWUIT applications regardless of whether the leverage this
feature or not, I'm trying to come up with a way to avoid this
penalty...

Shai.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
For additional commands, e-mail: users-help@lwuit.dev.java.net

Shai Almog

Hi,
not in the current version.
We are considering it as an option for a future version despite the
disdain both Chen and myself feel for such a nested UI.

Thanks,
Shai.

> Hi all
> is there a simple way to implement submenu in command menu ?
> Thanks

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@lwuit.dev.java.net
For additional commands, e-mail: users-help@lwuit.dev.java.net