>True. I think we should ditch the built-in dial command, add full control
>of serial ports, and then just have a dial function in the home stack.
Anthony,
Would work if we allow multiple stacks in one file. Then we could just
merge a home stack with minimal contents into the standalone. If we gave
the users a choice which home stack to include, they could create their
custom versions that don't have certain commands, or could add commands
like dial etc. they need and start using that stack.
>The problemn is writing a parser that can be extended at runtime is not
>easy. The Nuparser plans _might_ allow it, but the plugins would be hard to
>write, and would require absolute perfection, or the whole thing would fall
>apart.
>(...)
>And in either case, if you thaught extension conflicts were bad, just wait
>until you see plugin conflicts.
I don't think we should allow any syntax structure to be plugged in, but
adding support for additional commands and functions won't be that hard, I
guess. You'd just have to look up every command in a list to which plug-ins
would be added, too.
>I thaught we were talking about search paths, not bookmarks?
Me too. Bookmarks can be implemented easily by hand. Not a feature for OC,
you'd just put the names of stacks in one menu and then have a domenu
handler like:
on domenu mItem, mName
if mName = "Links" then
go stack mItem
else
pass domenu
end if
end domenu
Search paths are what's reauired to find stacks on a certain computer.
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
