>Take the Python (www.python.org) interpreter and revamp
>the syntax to be as xTalk like as possible.
>This would be the heart of the LGPL Embeddable
>interpreter and become the base code.
Michael,
I don't think this'll work out. Python is much more structured than
HyperTalk is. Hacking a very formal type of language to be as informal as
HyperTalk would result in a slowdown, or in a huge amount of rewrite. What
you'd be able to use from the Python code would very likely be about as
much as Anthony has already finished. I'd rather suggest you get into BISON
and help Anthony with implementing Interpreter.
>and throw some Mac programmers on the
>wxWindows project.
I'm fine with that. I'm already helping out from time to time (though I
haven't yet been able to download the new beta). This would provide both
your wxPython project as well as the current branch, which is why I don't
have any objections at all.
>Begin programming the object hierarchical message passing
>infrastructure and "stack" library in the new OpenTalk
>language. This gives us our familiar stack based card
>metaphor of objects and commands and gives the xTalk
>languages a new reputation for procedural programming.
You mean we should essentially duplicate Serf? Well, if Interpreter or
your HyperCardized Python would be that fast, I don't mind. But so far I
think we'd gain more speed in the long-term run if we did like MetaCard and
tried to do as much as possible with as few scripting lines as necessary.
Whatever may happen in the future, at the moment compiled code still *is*
faster.
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
