Return to Main Menu.rtf CVS log

Up to [NeXTSTEP 3.3 examples] / Examples / AppKit / BusyBox / English.lproj / HelpFiles

Annotation of Examples/AppKit/BusyBox/English.lproj/HelpFiles/Main Menu.rtf, revision 1.1

1.1     ! root        1: {\rtf0\ansi{\fonttbl\f2\fswiss Helvetica;\f1\fmodern Courier;}
        !             2: \paperw11780
        !             3: \paperh9540
        !             4: \margl120
        !             5: \margr120
        !             6: {\colortbl\red0\green0\blue0;}
        !             7: \pard\tx1140\tx2300\tx3440\tx4600\tx5760\tx6900\tx8060\tx9200\tx10360\tx11520\f2\b0\i0\ul0\fs36\fc0 The Main Menu
        !             8: \fs24 \
        !             9: \
        !            10: The main menu works best when it's short (so that commands are easy to find) and narrow (so that it doesn't take up much screen space).  Applications should try to have not many more than eleven or twelve commands in the main menu.  (Nine commands are shown for the standard menu, and only three of them�Info, Hide, and Quit�are required of all applications.)\
        !            11: \
        !            12: The main menu is also, for the most part, a menu of menus.  Commands that are added to the main menu should typically be ones that bring up submenus.  When designing your user interface, you can move a command that the guidelines place in a submenu up one level to the main menu, provided that:\
        !            13: \
        !            14: 
        !            15: \pard\tx160\tx2300\tx3440\tx4600\tx5760\tx6900\tx8060\tx9200\tx10360\tx11520\fi-160\li160\fc0 �        The main menu is short enough to accommodate another command (see the guideline above).\
        !            16: \
        !            17: �      The command provides functionality that's considered central, even crucial, to the application.  For example, a text editor might bring the Font command up to the main menu from the Format menu, but a spreadsheet would not.\
        !            18: 
        !            19: \pard\tx1140\tx2300\tx3440\tx4600\tx5760\tx6900\tx8060\tx9200\tx10360\tx11520\fc0 \
        !            20: Like any other command that's added to the main menu, a command that's raised from a submenu should generally control another submenu.  When a command is promoted to the main menu, it should, for continuity, be located immediately after the command for the submenu it would otherwise be in.  For example, if the Font command is raised from the Format menu, it would logically follow the Format command.  If the Find command is promoted from the Edit menu, it follows the Edit command.\
        !            21: 
        !            22: \pard\li1200 \
        !            23: 
        !            24: \pard\tx1140\tx2300\tx3440\tx4600\tx5760\tx6900\tx8060\tx9200\tx10360\tx11520 There's a great deal to be gained if commands shared by most applications are arranged similarly in similar menus.  Every application should strive to lay out its main menu like the model illustrated by BusyBox.\
        !            25: 
        !            26: \pard\tx1700\tx2200\tx2720\li1200 \
        !            27: 
        !            28: \pard\tx1320\tx2420\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\tx9600\b\fi-1320\li1320 Command   Action
        !            29: \b0 \
        !            30: Info   Attaches the Info menu, which contains commands for application information, preferences, and help.  
        !            31: \fc0 If an application doesn't support any of the commands in the Info menu except Info Panel, it should dispense with the menu and make the Info command in the main menu bring up the panel instead.\
        !            32: 
        !            33: \
        !            34: Document       Attaches the Document menu, which contains commands affecting windows and the files displayed in windows.  
        !            35: The Document menu is a menu that will be named differently in different applications.  Therefore, it's important that the command be in a prominent, well-defined location (second).
        !            36: \
        !            37: \
        !            38: Edit   Attaches the Edit menu, which contains commands affecting the current selection in editable documents.\
        !            39: \
        !            40: Format         Attaches the Format menu,  which 
        !            41: contains the principal formatting commands for the application.
        !            42: \
        !            43: \
        !            44: Windows        Attaches theWindows menu, which contains commands to bring windows to the front of the screen and to close and miniaturize windows.\
        !            45: \
        !            46: Print...       Brings up a panel that permits the user to print a document.  This panel is defined in the Application Kit.\
        !            47: \
        !            48: Services       Brings up a menu with commands that request services from other applications.  For example, users can request the dictionary application (Webster) to look up the current selection, or the Workspace Manager to open a file.  
        !            49: The Services menu will become increasingly important over time and therefore is placed in an easy-to-find position (just above Hide).  It's not higher in the main menu because it isn't a gateway into the application's own functionality (but often invokes a systemwide service or activates another application).\
        !            50: 
        !            51: \
        !            52: \
        !            53: Hide   Hides all the windows of the application. \
        !            54: \
        !            55: Quit   Terminates the application.  If the application has any open files that the user has altered but not saved, this command should bring up an attention panel giving the user the option of canceling the command and perhaps also of saving the altered files.
        !            56: }

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.