I think for consistancy, it might be desirable to define an interface that
bindings to specific languages can be defined. A good example of this is
SAX (Simple API for XML) which is an API specification which allows for
binding to many different languages, all of which make the same calls. What
kind of interfaces do we need to interact with a scripting language? I
would assume we need some way of interfacing with the odb server, which may
be a good source of scripting language bindings. From this, the odb may
allow us to handle the filling the visual stuff which are defined in a
descriptive section which could be partiually provided by the scripting
Using scripting languages which have to be interpretted, has always been one
of the bottle next in using a scripting language like that. Since if within
3Dsia you call a python script, then you have to instanciate a python
interpretter, execute the code, and interface with the 3Dsia code.
Crystal Space still has python support in it...just as a side reference.
> From: On Behalf Of M.Haisenko@...
> Sent: Wednesday, January 24, 2001 6:05 AM
> Fast as in system-performance: I don't know, but I ran a little Python
> script that prints primes within 3Dsia... and that was fast :-)
> Fast as in development-time: Absolutely ! Later on we need some components
> to handle with, say primitve 3D objects and stuff. If we've implemented
> one and want to test it it'll be the fastest way to do that with some kind
> of scripting language. Same goes for any other primitive operation,
> especially if we don't want it to be part of our code base.
> From: "Lars Weitze" <chromedemon@...>
> Sent: 01/24/01 12:52 PM
> > The main question is: is it worth the 'overhead' ? I think so, because
> > it'll save us a lot of work in the future... Th main questin for 3Dsia
> Is it fast?