Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!agate!bionet!apple!bloom-beacon!tut.cis.ohio-state.edu!mailrus!nrl-cmf!cmcl2!lanl!unm-la!unmvax!nmtsun!wbnsnsr
From: wbnsnsr@nmtsun.nmt.edu (William Norris)
Newsgroups: comp.sys.amiga
Subject: Standardization
Keywords: Menus
Message-ID: <1314@nmtsun.nmt.edu>
Date: 20 Oct 88 04:22:57 GMT
Reply-To: wbnsnsr@nmtsun.nmt.edu (William Norris)
Organization: New Mexico Tech, Socorro NM
Lines: 62

NOTE ON GROUP:  Although I believe this correctly belongs in 
comp.sys.amiga.tech, I receive no response in that group.  However,
I received several responses in comp.sys.amiga.  Here goes...

First, I will post the MENU system which I have been working on.
This is what I've been working on the most, and is the most complete.
I will eventually post ideas about FileRequesters, Requesters (in general),
Cursors, String Gadgets, etc.

PROPOSED STANDARD MENUS
-----------------------

Boing (Hopefully a ball, but currently the (c) symbol)
	About...           ?  About box for program
	--------------------
	Help                  Help for this program (also HELP key)
	--------------------
	Preferences	      Run preferences
* How about the possibility of letting users add to the end of this menu
* names of programs.  Selecting the item would run that program.

File
	New                N  
	Open...            O  Will post standard file requester later.
	Close              W  
	Save               S  \ Will post standard file
	Save As...         A  / requester for save later.
	Delete...          D
	--------------------
	Print...           P  Also, print-related options should go in
			      this section.
	--------------------
	Quit               Q  Programs should inform the user that everything
			      has not been saved, and if he really wants to
			      quit.  Information on requester boxes will come
			      later.

Edit
	Undo               Z  (Redo after Undo has been done)
	--------------------
	Cut                X  \
	Copy               C   | Save information to clipboard 0
	Paste              P  /
	Clear
* Cut... Copy... Paste... could be used if program allows saving
* to other clipboards.

The font menu
* First, programs should check how many lines are on the screen
* Longer menus can be created on an interlaced screen and when
* WB 1.4 is here, overscan.

* Font names should be listed alphabetically as menuitems
* Font sizes should be listed numerically as subitems (menumenuitem)
* If you want to get fancy, include a `?' at the bottom of the sizes
* to allow the user to enter any allowable font size, and scale
* an existing font.  This routine will be provided in the library.
* Read: Hardly any extra code to implement, but many advantages!

* Question:  Should the font menu be arranged 1) across several columns
*            if there are that many fonts or 2) with a down arrow
*            at the bottom of the menu and scroll down the menu for
*            the additional columns?