Personal tools
You are here: Home Developer Incubation Kepler Graphical User Interface Archive Menus and Toolbars

Menus and Toolbars


STATUS:
Red TriangleThe content on this page is outdated. The page is archived for reference only. For more information about current work, please contact the GUI Group.

 

 

Overview

 Design and proposed design of Kepler Menu and Toolbar.

 Status 12/8/2006 by LLD: Toolbar re-design complete in Kepler 1.0 Beta 2, menu bar re-design not complete and several decisions to be made regarding functionality and some wording issues.

Menus

Main Menu - Kepler 1.0 Beta2

 

RCM menus - Kepler 1.0 Beta2https://code.kepler-project.org/code/kepler-docs/trunk/legacy-documents/dev/usability/RCMs.png

Proposed Menus

 Design Rationale:

  • Group related operations together.
  • Utilize standard menu organization.
  • Add mnemonics and shortcuts.
  • Provide full set of menu operations in main menu.
  • Limit number of right click menu options where possible.
  • Add standard and expected menu items.

 

https://code.kepler-project.org/code/kepler-docs/trunk/legacy-documents/dev/usability/screen_designs/pro-main-menus-3142006.png

 

Instantiate Entity, Instantiate Attribute added back in to Workflow Menu -- we may possibly rename these.

More Notes: Developers use Configure and Open Actor most often.

Discussion on IRC regarding KAR files and adding actors to the tree. We decided on three menu items whose functionality is:
  • Import Import Kepler Archive - import an existing KAR file into system and user selects where they want it to appear in the tree (library)
  • Export as Kepler Archive -- creates a KAR file from an existing actor on the canvas and user must name the KAR file.
  • Add to Library -- add an atomic or composite actor to the library and also be able to adjust its location in tree (library) if desired, in the case of add, KAR file is created behind the scenes but user doesn't have to name it etc.

These items have been added.

Update on KAR files and repository menu items as of 4/19/2006:
  • Import Kepler Archive -- user imports something and decides where to put it into the three
  • Export Kepler Archive -- user creates and names KAR file but doesn't do anything with it but leaves it locally stored
  • Save to Library -- user wants to add an actor from the canvas to the tree (KAR file gets created behind the scenes) -- this would be for sole use of this user
  • Upload Actor to Repository (I would probably rename this to Upload Component to Repository) -- user wants to deposit a component in the library (KAR file gets created behind the scenes) -- this would be for users to share with other users

5/18/2006 -- Shawn asks do we need a "Download Component from Repository" menu item?

ITEMS WITH QUESTIONS: Do we need Open Base Clasee and Conver to Class? What are Semantic Search and Suggested Channels?


https://code.kepler-project.org/code/kepler-docs/trunk/legacy-documents/dev/usability/screen_designs/pro-rcms-3142006.png

Toolbar

Current Toolbar

 

 

https://code.kepler-project.org/code/kepler-docs/trunk/legacy-documents/dev/usability/screen_designs/curr-toolbar.png

 

Proposed Toolbar

 

Design Rationale:
  • Improve balance by making all toolbar icons the same size.
  • Improve readability and recognition by making design elements larger and contained.
  • Communicate more effectively with appropriate symbology.
  • Apply color appropriately.

 https://code.kepler-project.org/code/kepler-docs/trunk/legacy-documents/dev/usability/screen_designs/pro-toolbar.png

 

 

Document Actions