Technical details
These categorisations provided here amend and expand on documentation provided in the PRMs. The intent is to clarify the system for a logically organised iconbar, with clearly defined positioning for components, and whilst retaining the current state wherever possible.
The iconbar should be viewed as:
Iconbar layout
Object sources and sinks
These are icons for devices to which objects can be sent or retrieved from. They are ordered logically from read only devices on the left through read/write devices to write only devices towards the right. Alongside write only devices are the volatile devices; those devices whose contents are not likely to remain permanent from session to session (or even within a session).
The full ordering is:
Priority Name Meaning &76000000 Scanners Read-only device &74000000 CD-ROM Read-only device &70000000 Hard disc Read-write device
Examples: Any fixed RW medium falls into this category&68000000 Floppies Read-write device
Examples: Any removable RW medium falls into this category&60000000 Network Read-write/Read-only device
Examples: Any network filing system falls into this category&40000000 Volatiles Read-write device
Examples: RAMFS, Transient, Trash cans, Memphis, Scrap, etc&0F000000 Printers Write-only device &04000000 Accelerators Examples: ResourceFS, "Pinned" items, Director, Menon, etc. All devices in this category should have a name underneath, ideally identifying the medium name with which they are associated. If no medium is associated (eg. a removable, or unconfigured device), they should display the medium name (eg. Zip disc, Printer, LanMan, etc), or a generalised medium identifier (eg. the drive or port number).
These applications should not provide a "Quit" option.
Data source / sink controllers
This is basically a place for internet servers, connection systems and other network utilities to live, as well as local servers. Like the Object sources, these should have their name under them. Samba, TelnetD, Newsbase, InetSuite, WebServe and Netplex would fall into this category. These will grow to the right when the user loads a new controller.
These applications should provide "Quit" options. Most should provide a status window, and many will provide configuration windows.
User applications
This is where user applications appear when loaded. They will grow to the left as they are loaded, taking up the free gap space.
These applications should provide a "Quit" option.
They should not have text placed under them unless they are configured into a particular state that must be described. Such applications are discouraged unless there is a genuine need.
System control applications
This is where system control applications live. These are things that will control the machine, the desktop or the way in which the system works. Initially, this comprises the Task Manager and Display Manager. Because of its high priority, Help lives here too. This may be rationalised in future.