OK, no problem. My thought on osgteapot was to simply remove it, but if
you believe it, or something like it, still has value, then that's fine.
Regardless of the osgteapot example's future, I believe the teapot.osg
model has value if, for nothing else, it is one of the quintessential
models of the industry. I find the model is useful, and I thought others
would, too. But you're free to leave it out of OSG-Data if you wish.
Paul Martz
Skew Matrix Software LLC
_http://www.skew-matrix.com_ <http://www.skew-matrix.com/>
+1 303 859 9466
Robert Osfield wrote:
Hi Paul,
On Wed, Nov 25, 2009 at 3:27 PM, Paul Martz <[email protected]> wrote:
Hi Robert -- Just a ping to see if you perhaps missed this submission?
I haven't missed it, just haven't decided whether it's needed or not.
Ideally the different models we have would demonstrate different
things, or go be component of a large scene composition.
The osgteapot example demonstrates two things - extending Drawable to
add custom OpenGL code, and the the glMap/glEvalMesh functionality.
While the teapot.osg is just a model of teapot.
To port osgteaport to GLES or GL3 we'd need to replace the
glMap/glEvalMesh code, what to replace it with, if anything is my main
question.
Robert.
_______________________________________________
osg-submissions mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
_______________________________________________
osg-submissions mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
