>The user interface (UI) is the means by which creators and viewers of FreeCard
>documents ("stacks"?) interact with the FreeCard engine
>("interpreter/player"?)
>and obtain instructions/assistance in it's use. Individual FreeCard documents
>can build upon FreeUI or create an entirely different UI.
Rob,
I think we cab use HC and Mac terminology here, to avoid
misunderstandings. That is, FreeCard documents are stacks, the FreeCard
engine is simply called the FreeCard application, and a FreeCard page is
simply a card.
>* Creation and maintenance of new documents, pages ("cards"?), and individual
>objects, including resetting the properties of any object where appropriate
Do you mean changing objects' properties, or do you mean a "Reset" button
that discards changes made up to a prior point in time? Please clarify.
>* Navigation from document to document and page to page
Definitely. I guess you already have ideas? Go menu? Navigator palette?
Arrow buttons? None of these? All of these? ... ?
>* Interaction with the engine via keyboard, mouse (trackball, etc) and
>display,
>with audio and visual feedback.
This goes without saying, I guess.
>* Object scripting, including handler debugging and variable/message viewing
>* Direct command input (ie: message box)
An actual feature request! This is definitely one of HyperCard's most
sought-after features people request from clones.
>* Online and/or printed instructions on how to use FreeCard
Any suggestions what we should start with? A help stack, HTML docs,
PageMaker etc. files to generate printed manuals, ... ? My personal opinion
would be to start with computer-viewable docs and create printed docs at a
later date (this would probably be something people could make money off).
>* Import/conversion of HyperCard stacks
Just to provide additional technical details: Conversion should be
possible with an "exporter" HC stack and an "importer" FC stack. Actually
having FC open HC stacks would require knowledge of HC's file format, which
is a closely-guarded secret and would require a good programmer to
reverse-engineer HC's file format.
>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.
Definitely. I urge everyone actually creating a window/dialog/palette for
FreeUI to look at existing dialogs in already finished parts of FreeUI and
to make their window layout resemble this dialog. Just look at how HC's
button/field/card/stack info dialogs all look so similar.
>2. Simplicity: The FreeUI metaphor should be simple to understand & learn
>and provide convenient access to help.
We will definitely need good writers for balloon help and manual text, and
we should organize our menus in a way that reflects this metaphor and the
hierarchy in there.
>3. Solidity: FreeUI must not be released to the public until it has been
>sufficiently tested to know it is stable and robust.
I agree, there won't be a final FreeUI 1.0 unless we have tested it
thoroughly. Though it is understood that we as an open source project will
be making the UI available before it's finished to anyone who wants to help
or test it.
>4. Velocity: FreeUI must perform adequately on the hardware base for which
>it is targeted.
Yup. Though I guess this will mainly depend on the underlying FreeCard
application, which means it's mostly the responsibility of Anthony and me.
>5. Expandability: FreeUI must be modifiable.
There are several aspects to this:
1) maintainability:
all scripts will need to be heavily commented so everyone easily
understands what's happening under the hood. Also every handler should be
named in a way that it's clear what it does and what it doesn't.
2) scripter customizability:
this is optional: We could provide some way for other scripters to create
utility stacks (like "Power Tools") which will be added to the UI (like
SC's Utilities menu)
3) user customizability:
I am not sure to what degree we'd want to pursue this. There was already
talk about being able to change the default script editor font, and we
*could* go as far as MS Word does, which allows removing/adding menu items
from/to the UI (to the UI, mind you -- of course FreeCard stacks will be
able to create their own menus etc. just like they can now in HC). I'm not
very much in favor the latter, as it would make support much harder, but
OTOH it's a great deal of freedom, so if you want to put that on the
feature list, I won't complain.
>I'll leave it there for now; but I do have more to offer.
I'd be glad if you shared more of your thoughts with us. Same applies to
anyone else who'd like to speak up. Let's do a quick brain storming what
YOU all would like to see in FreeUI, ok? It'd be great if we had 100 ideas
to choose from.
Cheers,
-- M. Uli Kusterer
------------------------------------------------------------
http://www.weblayout.com/witness
'The Witnesses of TeachText are everywhere...'
--- HELP SAVE HYPERCARD: ---
Details at: http://www.hyperactivesw.com/SaveHC.html
Sign: http://www.giguere.uqam.ca/petition/hcpetition.html
