2.0 Main Window
3.0 Dialogs and Druids
The target users for the Panel Menu Editor are GNOME desktop end-users and GNOME desktop system administrators.
bla bla bla
Although functionaly complete, the current (GNOME 1.4) method of Menu/Panel editing is not obvious to the end-user. It is also not accessible via keyboard navigation. The following design will present a more familliar UI paradigm and allow for keyboard navigation.
This design will follow the GNOME Style Guide - which will hopefully posted sometime on http://developer.gnome.org/projects/gup/.
The GNOME desktop
|Menu Item / Shortcut||
|Gadget||The end-user term for applet|
The default desktop & panel for GNOME 2.0 is shown below:
File, Edit, View, Help, and User Level.
The tree consists of a Desktop node; it can only have Panels as children. Panels can have Menus, and Gadgets as children. Menus can have Menu Items as children.
Shows any child objects
The Panel Menu Editor is invoked from the Control Center.
Main window size, position, and view state parameters should be automatically saved on a per user instance . That is, every time the console (configuration) is exited, the following parameters are automatically saved:
These parameters should be loaded automatically when the editor is next invoked.
Note: ----- denotes a separator.
|>>> Undo Ctrl-Z <<<||Optional standard action|
|>>> Redo <<<||Optional standard action|
|>>> Cut Ctrl-X <<<||Optional standard action|
|>>> Copy Ctrl-C <<<||Optional standard action|
|>>> Paste Ctrl-V <<<||Optional standard action|
|>>> Delete Ctrl-D <<<||Optional standard action|
|Properties...||Launches properties of selected object|
|Select All Ctrl-A||Selects all objects in Results Pane|
Note: "Menu Item >" denotes cascading menu.
Note: [x] and (o) denote a check box and radio button respectively.
User Level Menu
The Toolbar is (TBD):
All toolbar buttons have Tooltips.
We should also still support direct editing of the panel and menus, in a similar fashion to GNOME 1.4.
For the beginner user, the editor would be in read only mode.
For the intermediate level user, a druid would be used to edit the Menu Item.
For the advanced level user, a properties sheet would be used to edit the Menu Item. The following are modified versions of the existing menu props windows. These will be updated to exposed all the data as found in .desktop files and vfolders.