jan p. springer wrote: > Christoph Fünfzig said the following on 10/31/06 17:14: > [ snip ] > >> Python bindings for OpenSG are really cool :-) >> > > actually they are :) > > >> But I think executing GraphOps after reading a model/scene can be done >> easily, already in Version 1.6. >> You can create a GraphOpSeq by a string, listing all graph ops you want >> with their parameters, >> see method void GraphOpSeq::setGraphOps(const std::string params); >> and SceneFileHandler::read can receive a GraphOpSeq to apply after loading. >> >> So no need for weird filenames, I think ;-) >> > > yes and no. the intention, again, for having pseudo loaders is when i want > to > specify per model xforms, etc. but am going to merge them via a cmdline > tool. > the model created is actually the one i want to use in the (final) > application. > that is sth. like a poor-man's work flow not reallying on modeller tools. > > I see. Where do the pseudo-loaders of OpenScenegraph (trans, rot, scale) get there parameters from, also from the filename, I guess? Can you chain them, like rot and then trans? > having graphops in a pseudo-loader style would be cool too, but using them > on a file and using them on a loaded scene in an application are two > different > animals (at least to me). > For the trans, rot, scale behaviour there is just a small difference in execution time between the pseudo-loader and the GraphOp approach, if at all.
Christoph ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
