> >>>snip
>
>Cluster? No, I think that would be a bad idea for VPython. Any recent
>video card will be able to handle pretty much anything you can throw at
>it from VPython. A scene with several translucent and textured objects,
>some using a source image of 1024x2048 pixels, can be rendered in only a
>few ms on common PC hardware. You really can't notice that it takes any
>time at all, and the UI remains buttery-smooth.
>
>Speed is not the problem. Picking the right parts of a complex
>environment (or completely reformulating the appearance of what you are
>doing) to expose to client programs in Python is the hard part, and that
>is what I would appreciate some feedback on.
>
>-Jonathan
One of the favorable attributes of VPython is its ability to quickly focus
on the dynamics of an animation. Rather than trying to duplicate the
functionality of POV-Ray or other 3D rendering packages, why not let
VPython import objects (stored in one of the standard 3D formats) created
in a 3D rendering package. This would minimize the number of attributes
that need to be exposed in VPython and let the bulk of the object creation
be done in an appropriate package.
Bruce Peterson
425 466 7344
|
