On 4-5-2008 4:59, Angel Herráez wrote: > On 2 May 2008 at 13:37, [EMAIL PROTECTED] wrote: > > > >> Or is it that for >> simplicity the two just share almost all the same menu-structure code? >> > > Yes, I understand it is so. Most functionality is in the pop-up menu, so all > of > it it is shared. > > In my opinion, duplicating functions into the top menu is not worth. You just > get used to the popup menu, the same whether you are in a web page or in > the application. > > > Getting used to it isn't the problem, it's about the new user that has never seen the program. If I am to ask people to download a copy of the app so they can see my structure results they need to be able to see what they expect to see with an absolute minimum of unexpectedness. Otherwise they'll simply not use Jmol. That means that if the menus and defaults for the app stay as they are I need to be able to provide a mechanism that'll (invisibly to the user) add/modify the functionality of the app to something they expect. I understand that the needs of the app and applet are different so there is a reason for the structure of the pop-up menu of the applet. But the functionality of the app needs to be accessible from where new users expect to find it.
Rich ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
