Hi Robert,
I think I wasn't clear enough. The issue is about read/write Object, not
streams or files.
For example, the ive loader implements readObject like this :
ReadResult readObject(*const* std::string& file, *const* Options* options =
0) *const*
***{*
*return* readNode(file, options);
*}
*
but the fbx plugin does not! So, these two lines don't have the same
behaviour :
osg::Object* obj = osgDB::readNodeFile("sample.fbx"); // file won't be
loaded, as readObject is not implemented in fbx plugin
osg::Object* obj = osgDB::readNodeFile("sample.ive"); // file will be
loaded, as readObject is implemented in ive plugin
so the question is would it be profitable to make all plugins implement the
readObject / writeObject when possible?
Mourad
On Mon, Nov 22, 2010 at 6:12 PM, Robert Osfield <[email protected]>wrote:
> Hi Mourad,
>
> On Mon, Nov 22, 2010 at 4:57 PM, Mourad Boufarguine
> <[email protected]> wrote:
> > This is the case of many other plugins where readObject is not
> implemented
> > (3ds, dae, ffmpeg, ...). I think it would be useful to make all plugins
> > implement read/write Object.
>
> It's not generally possible to implement full read/write for steams
> for all file formats. One has to implement them on a case by case
> basis. The native file formats that we have complete control over
> should however support reading/writing to streams as well as files.
>
> 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
