[vos-d] thoughts and plans

[Reed Hedges]

I think we do need modes for keybindings, and I like the general tool idea.  
The GUI should not neccesarily be directly mapped to mode.n ia fixed 
configuration though.  Instead, there should be a set of GUI elements (side 
panes, etc.) for each mode, but they should be flexible in that you can bring 
up other GUI elements, minimize elements, and it should remember that layout 
configuration for the next time you enter that mode.  And, mode transitions 
should be tools/bound actions. For example, you define in configuration that 
middle mouse click means to "select" an object, and also enter editing mode 
with that object selected.  By entering edit mode, the GUI layout for that 
mode would be displayed, which might include window panes with different 
toolboxes or information about the object displayed. But maybe you want some 
panes to always be visible in all modes, etc.; maybe you want to hide the chat 
pane while you're in edit mode or minimize it so that there's a little button 
on the edge of the screen that brings it back, etc.

I think tool panes/sidebars that you optionally float and move or iconify are a 
useful way to present buttons, tools, and object trees that makes them easily
accessible and viewable.

(We should also definately adopt Firefox's method of displaying background
notifications and non-modal dialog boxes by inserting them above or below the
main viewing area rather than as popups :)

Reed