Hi,
On Wed, 24 Nov 1999, Ian C. Smith wrote:
> I was wondering through the documentation of .2.4 and I was
> wondering if the script stuff was close to completion for
> your basic, everday SCI0 game, if there is such a thing.
There still are some missing system calls and ambiguities (especially
with very early SCI interpreters). The basic interpreter commands have all
been covered, though, and most system calls have been, too.
> And I was also wondering if you were going to produce an
> amateur SCI 'standard'. That is, a strict set of guidelines
> on the best version of SCI0 to use when creating your own
> games.
"Creating your own games" is not the goal of the FreeSCI project. We'll
try to document and support as much as we can, but code generation tools
(like Magnus' SCI toolchain) were originally intended to provide some
way to create code for testing purposes.
> The reason why I ask, was that I was hoping to maybe start
> putting together some code to give an SCI script compiler
> some... body? Anyway, I know that I probably won't be
> developing anything for Linux yet, due to the fact that I
> have neither the expertise, nor the experience, knowledge
> and a whole lot of other things that are needed.
If you try to expand on Magnus' toolchain, you'll only need a semi-current
Python interpreter.
> (Such as an
> up-to-date version of the Linux kernel.)
I wouldn't recommend developing anything specifically for the Linux
kernel, anyway. There are lots of other OS kernels out there, and all of
them want to be supported.
> I've got a lot of free time currently, and I want to make
> as much use of it as possible.
Well, there *is* a lot that needs to be done... <evil grin>
> BTW, is it really necessary to use CVS? I can't use it due
> to the fact that I cannot access a computer upon which I can
> use the software needed. Is it okay if I just mail it to the
> list and ask someone to use CVS to upload?
Please don't send patches to the mailing list; there are several lurkers
out there who wouldn't want to be spammed with that. Send it to one of the
developers.
> I don't exactly have anything to offer, as I still need to
> get going with looking through the code and identifying
> positions of interest. That is bugs.
So you can't see the forest for the trees... ;-)
llap,
Christoph
