On Wed, Apr 04, 2007 at 12:53:33PM -0400, Zach Miller wrote: > the reason scene and world are distinct was class soy.Node(soy.World), but > soy.Node was largely a carry over from soya.group and obsolete + > incompatable with the physics integration. i see no reason why they cannot > be combined.
Got it, thanks. > i just saw your http://pysoy.org/wiki/Layout and am wondering what happened > to the modes, controller, and network modules? Ah I may need to clarify the process I'm doing. The handful of modules I got from everyone had their own setup.py's and compiled separatly, working as a whole only through their Python API. I understand that make development easier because you could compile and test the pieces without the whole being built. However, the process of getting attributes from PyObjects is 20-25 times slower than with C variables. Pyrex lets us embed C variables easily, such as references to ODE body ids, which lets us grab that data via the PyObject's struct rather than preforming a dict lookup for an attribute. Using audio as an example - yes refering to an object's .position is a valid way for openal to obtain this information but it's slow. A signifigantly faster way is pass that object's _id_ to dBodyGetPosition. SO I've built a new unified setup.py and am constructing a new project tree, file by file, class by class, with the internal API based on cdef and cimport. It's easiest to do this by getting the basics worked out and then rebuilding the higher level classes (ie, the Modes) to match. Nobody's work is getting chucked out entirely, it's just getting shifted around and rearranged as I develop the new API. > On 4/4/07, Arc Riley <[EMAIL PROTECTED]> wrote: > > > >Mike/Seth, I'd specifically like your input on this since you've both put > >a > >ton of research and effort into this, but also for everyone to chime in > >on: > > > > > >While it's nice to have physics in the soy.physics submodule, since > >everything > >in 3d-land inherits Body, it's pretty silly to have Body be > >soy.physics.Body > >with everything else in core or a separate submodule. > > > >It's also pretty silly to have Scene inheriting from physics.World and > >that > >being the only real use of the World class. > > > >What do you think about merging Scene and World directly and moving Body > >to > >the same submodule as the 3d objects (camera, light, mesh, etc)? > > > >I'm thinking of calling said submodule soy.bodies, with everything in it > >inheriting soy.bodies.Body akin to how everything in soy.widgets inherits > >soy.widgets.Widget. This seems clean and intuitive to me. > >_______________________________________________ > >PySoy-Dev mailing list > >[email protected] > >http://www.pysoy.org/mailman/listinfo/pysoy-dev > > > _______________________________________________ > PySoy-Dev mailing list > [email protected] > http://www.pysoy.org/mailman/listinfo/pysoy-dev -- Arc Riley US2005022962 NE aRC: Publications NY-007-I Chapter Coordinator NY-007-I Venue Storyteller: Scheria Rising (Mage: The Awakening) http://ny007.neregion.net/ _______________________________________________ PySoy-Dev mailing list [email protected] http://www.pysoy.org/mailman/listinfo/pysoy-dev
