I've cleaned this up to use HC object names as Uli suggested and changed the text a bit. Also, as I noted in passing in my message to Uli, my object here is to provide a starting point for a list of general goals and capability requirements, NOT to propose any particular solution. I hope by defining and "fleshing out" generalities first we can achieve a common vision and create a list of criteria by which individual solutions can be evaluated and coordinated:
FreeUI
Overview:
The user interface (UI) is the means by which creators and viewers of FreeCard stacks interact with the FreeCard application and obtain instructions/assistance in it's use. Individual FreeCard stacks can build upon FreeUI or create an entirely different UI.
Capabilities:
The capabilities supported by FreeUI include:
* Creation and maintenance of new stacks, cards, and individual objects (eg: buttons, fields), including changing the properties of any object where appropriate
* Navigation from document to document and page to page
* Interaction with the FreeCard application via keyboard, mouse (trackball, etc) and display, with audio and visual feedback.
* Object scripting, including handler debugging and variable/message viewing
* Direct command input (ie: message box)
* Online and/or printed instructions on how to use FreeCard
* Import/conversion of HyperCard stacks
Goals:
1. Consistency: All aspects of FreeUI should share a common look and feel. It should appear to the user/developer as wholly integrated. A consistent look and feel should permeate every aspect of FreeUI, including documentation and help/error messages.
2. Simplicity: The FreeUI metaphor should be simple to understand & learn and provide convenient access to help.
3. Solidity: FreeUI must not be released to the public until it has been sufficiently tested to know it is stable and robust.
4. Velocity: FreeUI must perform adequately on the hardware base for which it is targeted.
5. Expandability: FreeUI must be modifiable.
I did not include Uli's comments in this repost, but that doesn't mean they shouldn't be in the group version (if there is one). In a subsequent post I'll offer some thoughts on ways to achieve consistency.
Rob Cozens, CCW
http://www.serendipitysoftware.com/who.html
"And I, which was two fooles, do so grow three;
Who are a little wise, the best fooles bee."
from "The Triple Foole" by John Donne (1572-1631)
