I was referring to the osgManipulators nodekit. The website is still stuttering..
I just checked the revision log, and there were a view since the first 2.8.2 tag: r10429, r10431, r10434, r10436, r10443, r10523 and r10794 (most are small revisions) The changes do make the usage of manipulators more accessable to 'quick' usage, and more in line with the rest of the nodekits (thanks robert). and also fix a possible crash on certain platforms (r10794). I do admit it is a little late in the process ;-) "make 2.8.3 equal to the trunk?" haha, yeah, my guess is that the trunk has much more larger updates, then the refactoring of this nodekit, but i see what you mean. about the collada dom, the dilemma is this: the usage of the plugin will increase if it is build out of the box. leaving it out because there is only a small portion using it, doesn't.. Maybe there should be a seperate link/zip file with binaries/precompiled libraries on the dependencies page. or the knowledgebase. It also seems that the collada-dom will introduce dependecies of its own (wereas png and freetype don't). Have a good day! René 2010/3/21 Jean-Sébastien Guay <jean-sebastien.g...@cm-labs.com> > Hi René, > > > Maybe the DOM 2.2 binaries could go into the 3rdparty folder or repository? >> that way the plugin becomes 'out of the box' like png and freetype >> or do we want a limited set of 3rdparty binaries? >> > > I think we'd have to survey to see how many people use it, because it's a > pretty big dependency (over 12MB for the dynamic version, and over 70MB for > the static version! and that's just for VC9sp1). If only a small portion of > users use it... The png and freetype libs are pretty much required to do > anything useful with OSG... > > > About the 2.8.3 release: >> I recently updated sources to use the new manipulators in 2.9.7 . >> Is there a stable release to be expected that include these (nice!) >> improvements? >> >> I wouldn't mind these changes in 2.8.3 but other users of the old >> manipulator code will have to change some code. >> > > It's pretty easy to add #if OSG_VERSION_GREATER_THAN in your code so that > it works for both versions of OSG. That's what I did when I tested if our > framework worked with OSG 2.9.7 (in particular for the changes in > osgManipulator). > > At some point Paul will have to draw a line, or else why not merge all the > changes and make 2.8.3 equal to the trunk? Anyways, there should be a 2.10 > release eventually, right? :-) > > > J-S > -- > ______________________________________________________ > Jean-Sebastien Guay jean-sebastien.g...@cm-labs.com > http://www.cm-labs.com/ > http://whitestar02.webhop.org/ > _______________________________________________ > osg-users mailing list > osg-users@lists.openscenegraph.org > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org >
_______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
