hi,

"Bald Eagle" <cre### [at] netscapenet> wrote:
> "ingo" <nomail@nomail> wrote:
> > object and material are just containers, lists/arrays..
> > there are a few specialised ordered lists with an operator attached, union,
> > intersect etc.
> >
> > A povObject/shape is like a specific composed dictionary/struct/record as is
> > texture. One could define it all in SQLite:
>
> > etc. etc. who needs type-systems and OOP if you have a database ;)

@ingo.  very happily second that.  </grin>

too, I think, organising the design around a db(ms) internally will make for
less complexity in the VM backend, and perhaps elsewhere (like providing the
"introspection" BE mentions to "the front").


> ...
> It would also be great if as many things as possible had some sort of default
> attached to it, so I could just invoke a sphere, and maybe it just had a
> POV-Unit diameter and default texture.

I so agree, everything ought to have "sensible defaults" for all but location
(and perhaps size).


regards, jr.

Post a reply to this message