Being consistent with the general user interface is generally a good way to start.
As Romain said, you could of course include a view in your layout that looks like a menu, always present, and thus hide or show it depending on user preferences. The rest of your layout would reflow accordingly. There are alternatives too. Maybe you don't need to strickly emulate the menu look. For example the email app have buttons at the bottom of a thread, with only the minimal choices one need (e.g. reply). The rest, the non-frequent operations, are in the menu. Another example is to have a row of buttons at the bottom that depends on what element is currently selected. Yet another example: you can reduce this row of buttons to merely icons with no text, thus saving space. Place the full icon+text in the context menu => the menu helps for the learning curve and once you know the icons you can just press them directly. R/ On Sat, May 2, 2009 at 7:32 AM, Raja Nagendra Kumar <nagendra.r...@tejasoft.com> wrote: > > ok. > > One of the point we were considering was to allow the users to choose > if he needs always visible menu (specially if the menu items or one or > two). > Also application using both menu and layout buttons could possibly > confuse the users and may not be a good UI design. > > Regards, > Raja Nagendra Kumar > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
