>I agree. We're really talking about a load of bullshit that's unimportant
>@ this stage. How about a "file view" of all the files included. We can
>drag-drop and import. Wouldn't that suit the purpose much better?
Dylan,
I personally also consider include to be something that's not very useful
in OpenCard. But if you consider we have a stand-alone interpreter planned
as one of the milestones before we get to the actual OpenCard application,
this interpreter might have a use for "include" and as it'll only execute
one text file and then quit, there's no problem with adding a "include"
feature there. But it should be a simple preprocessor token that's replaced
with the file it includes. For that Anthony has my "go ahead" if he
encloses it in a compiler flag so we can leave it out of OpenCard.
This "file view" would suffer the same problems as an "include" statement,
and is thus no better, only maybe a better UI for newbies. "start using"
and "insert script" will serve the purpose of including some library in
OpenCard perfectly, I assure you. Just for the OpenTalk interpreter
("OpenScript") we can't use that as we don't have a message-passing
hierarchy or objects, which is why that may have "include".
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
