Xref: utzoo comp.sys.amiga:24345 comp.sys.amiga.tech:2211 Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!ames!mailrus!cornell!rochester!rutgers!bellcore!faline!thumper!ulysses!sfsup!coco From: coco@sfsup.UUCP (+Lugo F.) Newsgroups: comp.sys.amiga,comp.sys.amiga.tech Subject: Re: Standardization Keywords: file requesters Message-ID: <4120@sfsup.UUCP> Date: 21 Oct 88 02:40:00 GMT References: <1304@nmtsun.nmt.edu> <4166@boulder.Colorado.EDU> <8XLHINy00VsfM0Z1FF@andrew.cmu.edu> <4183@boulder.Colorado.EDU> Reply-To: coco@attunix.att.com (Felix A. Lugo) Organization: AT&T Bell Laboratories Lines: 42 How about designing a standard set of functions which every file requester should have (i.e. a minimum set.) For example: o multitask while scanning for files, o access to available devices and volumes, not pre-defined gadgets with device names o scroll bar, arrow gadgets, double click selection, o keyboard shortcuts (i.e. use arrow keys to scroll file list, ALT+arrows to go to the top/bottom files, SHIFT+arrows to scroll by pages, Ok/CANCEL shortcuts, etc. o pattern specifications (*, ?, ranges, etc.) o PARENT directory gadget (with keyboard shortcut). o RESTART gadget for restarting file scanning o single file name string gadget o any other I may be missing Let's face it, some people have better things to do than spend their time developing/testing simple file requesters. Others can just create their own designs as long as they start with this minimum set. Other standards: CUT/PASTE, how about pop-up menus (don't you get tired of going to the top for menu operations.), window iconizing (with true image icons, not window fakes), Virtual screens, color requesters which adjust to screen's type/resolution, more, morE, moRE, mORE, MORE, MORE, MORE, ... 8*) // --Coco \X/ __________________________________________________________ E-Mail: coco@attunix.att.com Real: AT&T Bell Laboratories c/o Felix A. Lugo 190 River Road Rm. 1-139 Summit, NJ 07901 Tel. (201) 522-5098