From: Jon S. <js...@so...> - 2004-09-09 12:53:28
|
> > 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. > I'm excited to hear about these developments, but got lost in the trees of your description of the issues. On the off chance that you too are lost in the trees of coding, I want to make sure that the basic vpython aesthetic is not being overlooked. Pixels, for example, are several levels more molecular than I would likely want to work. I'd want to be able assign texture and transparency to an *object*'s surface. The positioning of the texture on the object might be controlled by rotating the texture around the center of the object. The texture would automagically slide around on the surface of the object. Since transparency is now an option (and this is very good news!) The surfaces of objects might also have thicknesses (with defaults of course). And the interiors might have a density/opacity parameter as well. The default condition I think should be thickness=.00001 (just enough to put a texture on) and opacity=1. And then vpython would do all of the per-pixel calculation (and shadowing and light scattering) under the hood, as is its "true nature". I hope this is helpful or suggestive. Regards, =-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Jon Schull, Ph.D. Associate Professor Information Technology Rochester Institute of Technology 102 Lomb Memorial Drive Rochester, New York 14623 sc...@di... 585-738-6696 |