The way i see it we should first design the language.
I think the whle thing should be programable. for instance.
Instead of haveing a button called "a" on a card you could have a make
file:
<cd>
name="card1"
<button>
name="a"
</button>
</card>
Any way you get the general idea. that way files could be edited in text
editors as well.
We could include a resorce file for the card pict and other resorces.
That would also make it more compatible with windows becasue they have
.res files.
We should then make a compiler:
We write the compiler in C/C++.
The compiler compiles both the make code and the OpenTalk scripts.
The compiler can compile to a application or a java applet.
Java applets we would just have to compile to byte code for interpreting
from the java VM.
Ok at this stage we can make stacks in text form and compile them with
our compiler. Fine.
Now to prove the flexability of our wonderful new compiler we write an
editor in our language to be compiled by our compiler.
The editor would look and feel just like HC but underneth would just
automaticly create code to compile.
eg.
i place a button on a card.
the card code would already be there and inside that will be:
<button>
name="new button"
left="200"
...
and so on
</button>
As we work in OpenCard it just generates code behind it depending on
what we do. It could write the resorces to the resorce file.
This would be the eisiest,fastest and most reliable was to do it.
Think about it.
julian b
