Hi Johan, You can simply run osgconv --formats to list all the details of the plugins including options supported. osgconv --format vrml would list just the details on the vrml plugin.
Robert. On Tue, Nov 9, 2010 at 2:43 PM, Johan Nouvel <[email protected]> wrote: > Hello Robert, > > I will add supportsOption() calls. > But I'd like to see the result of these calls, so is there an example to > print on console options, extensions and protocol supported by a plugin ? An > osgplugin(s)infos for example ? > If not, how to do that ? By using osgDB::PluginQuery class ? > > Cheers, > Johan. > > On 08/11/2010 16:52, Robert Osfield wrote: > > Hi Johan, > > > I've merged and checked-in your changes. > > The options are a bit cryptic though. In the latest version of the OSG > there is support for reporting the options and a description string, > so perhaps this would be something that would be good for the new > writer options that you've added. For instance the following can now > be found in src/osgPlugins/osg/ReaderWriterOSG.cpp's ReaderWriterOSG > constructor: > > supportsOption("precision","Set the floating point > precision when writing out files"); > supportsOption("OutputTextureFiles","Write out the texture > images to file"); > supportsOption("includeExternalReferences","Export option"); > supportsOption("writeExternalReferenceFiles","Export option"); > > Could you do something similar for the options you've added to the VRML > plugin? > > Thanks, > Robert. > > > On Wed, Nov 3, 2010 at 4:47 PM, Johan Nouvel > <[email protected]> wrote: > > > Hello, > > Some times ago, I have coded an osg to vrml2 writer. Today, I have updated > our writer to osg 2.9.9. > As it works (for our needs at least) I've done and attached a tar.gz file > for the VRML2 plugin with a new part to write a VRML2 file from an osg one. > > The read part is the same as in osg 2.9.9. > > The write part code is in convertToVRML.cpp and .h files. It works for some > osg nodes (group, geode, matrixTransform, positionAttitudeTransform and > geometry). Textures are converted to jpeg (if not translucent) or png (if > translucent). > There are some options that could be given to the writer (with -O switch) : > > convertTextures=0 to copy textures without converting them to jpeg or png > convertTextures=-1 do not copy textures, keep them in their original format > and location > convertTextures=-2 do not use textures, parse only geometry > convertTextures=-3 (default) convert textures to jpeg or png ones. > > textureUnit=X in case of multiple textures, X= texture unit to use (default > value=0) > > directoryTexture=aPath when texture will be copied, it will be in this > directory, not in the current one. > > Cheers, > Johan. > > -- > Johan Nouvel, research engineer > http://www.archivideo.com > tel : +33 (0)2 99 86 30 20 > ARCHIVIDEO, 40 rue des Veyettes, 35000 RENNES, FRANCE > > _______________________________________________ > 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 > > > -- > Johan Nouvel, research engineer > http://www.archivideo.com > tel : +33 (0)2 99 86 30 20 > ARCHIVIDEO, 40 rue des Veyettes, 35000 RENNES, FRANCE > > _______________________________________________ > 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
