>Hmm, I think the one thing that is wrong with MC's interface is the fact
>that it uses palettes. They just get in the way. I much prefer HC's
>semi-modal (can still switch to a different app) dialog interface. I
>will see if I can do up a design for the interface I imagine soon, but I
>can make no guarantees as I have other paid work to do right now which is
>falling behind.
Adrian,
if you put the stuff that's relevant into the palettes it's no problem.
Being able to collapse palettes also helps. I'd say we at least need
modeless dialogs for "button info" and the likes.
>Perhaps we need to support plug-in interfaces. This is obviously
>possible if the entire interface is written in FreeScript, just change
>home stacks. I'd like to see buttons be able to change design and
>appearance as well though. I'll try and formulate these ideas more
>later, I'm incapable of thinking straight just now.
Well, the UI will certainly be switchable by changing home stacks (or
maybe calling "start using" on a different editor stack), but allowing
buttons to look different might be harder. I'd say that is a 2.0 feature.
Maybe we'd add a "user part" that receives messages when it needs to be
drawn, and that could be used to implement custom buttons etc. Having every
part work this way might really slow down the engine.
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
