On Mar 2, 2007, at 6:29 AM, Angel Herraez wrote:

> El 1 Mar 2007 a las 18:45, Egon Willighagen escribió:
>
>> Close is supposed to close one window but keep the application if  
>> there are
>> other windows, while Exit is supposed to close all windows and  
>> exit the
>> complete Jmol application.
>
>
> We should discuss what is the most logical behaviour that users will
> expect.
>

hi Angel,

expectations will depend on the OS of the user, I imagine; for  
example, Quit is much more intuitive than Exit to me, since I use a  
Mac. :-)  also, when I close the last window of a running app, I  
never expect the app to quit - again, colored by the behavior of my  
working OS.


> My opinion:
>   "Open" loads a molecule, so when I see "Close" beside "Exit", I
> imagine that the first will remove the molecule, and the second will
> exit the program = close the window.
>
> I would propose:
>
> File
>     New window *
>     Open file *
>     Open URL
>     Recent files
>     Export
>     Print
>     Script console *
>     Close                             = zap
>     Exit                                      = close window
>     Exit all windows *                
>
> (those with * are new or renamed)
>
> Another option could be:
> File
>     New *                             = zap
>     New window *
> [...]
>     Exit                                      = close window
>     Exit all windows *                
>


I'll add my suggestions, too:

File
    New Viewer Window
    Open Model...
    Open Model from URL...
    Open Recent->
    -------
    Close Window
    Remove Model->
    Save As...
    Export...
    -------
    Print...
    Exit


Console
    Open
    Run Script...
    Run Script from URL...
    -------
    Close
    Save Script...


since Jmol can have several models loaded, it might be useful to be  
able to selectively remove them (using the Remove Model sub-menu).   
Close Window would automatically remove all models loaded in that  
window.

also, it might be helpful to be fairly explicit in the menu commands,  
to avoid confusion with users of varied platforms.  and finally, I  
think the Console commands should be promoted to their own menu. (is  
there a way to save a script from the app?)

just a thought, prompted by Bob's comment that he only uses the app  
for script development: it would be cool if Jmol had a built-in  
script editor - a user could open a script file in Jmol, edit it, run  
it, run only pieces of it, even debug it, all in Jmol.  tab-complete  
for script commands? ;-)



tim
-- 
Timothy Driscoll                                em: [EMAIL PROTECTED]
Virginia Bioinformatics Institute               ph: 540-231-3007
Bioinformatics I: M-1                           im: molvisions
Washington St., Blacksburg, VA 24061



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users

Reply via email to