> One things is reading it - making changes to it is a different matter. I
> wouldn't be able to keep track on lots of small changes without coding them
> little by little and testing that they work on the way.
>

I wasn't really thinking about making major changes, just some
simplifications on certain algorithms, or variable-usage (there are
tons of them right now, and I probably don't need THAT many)
to save some RAM. And testing afterwards is of course a must.

> [...]
> One time for every frame, or once and for all for the entire animation?
>

I could go both ways, either for every frame, or once and for all,
though the emitting-objects wouldn't move then (I can only save
a certain time-frame, not actual animations, at least not yet)

> We'll see - I'm pretty sure the interfaces are completely different from
> each other.
>

I agree to that, but nontheless I could look at your system in order
to make my macros fit yours, and perhaps vice versa? Just that
someone could put your system in a macro of mine, and my
system in a macro of yours (in case your actually supporting
that many macros, I've made it possible for EVERYTHING to
be user-defined with a macro... but I'm not sure if that was
a good idea...)

When I'm back from my civil service course, I'll probably work
on some images and the particle system (docs, algorithms, examples),
so expect some funky (and crappy) ideas when I'm back... ;-)

--
Tim Nikias
Homepage: http://www.digitaltwilight.de/no_lights/index.html

Post a reply to this message