Hi, thanks for the replies.. I'd just like to state that the aim of my request is to get the basic swig prototypes/bindings in place, to ensure their correctness. I think that process could be automated, somewhat.
Even though the automatically generated bindings would be unwieldy for end users, from there, one could generate the appropriate end-language bindings, in a clean, 2-step process. That way, you get the universality of having swig prototypes, and then language advocates can do their thing to get more language friendly/appropriate bindings. In any case, any changes that break SWIG would automatically generate a regression, and that's a damned useful thing to have happen. Also, I'd like to point out that for all of osgswigs' goodness, it is mightily unfriendly to non-python users, and I don't think that works to our advantage, in the long term. My specific issue with the osgswig project is the way files get released (the only downloadable file from the project site is http://osgswig.googlecode.com/files/osgPython-2.6.1-0-py26.exe), and I have a philosophical issue, having been burnt *many* times, with being forced to grab files from svn, cvs or any other source control system, because things aren't stable in that regime, by definition. By including the bindings with the releases, there is some notion of stability, even if it's just at a basic level, and that is an insanely valuable thing to have. ... Thank you! Cheers, john ------------------ Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=15979#15979 _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
