Re: [osg-users] Serialization of osg::Image data into OSGT
Hi, It might be interesting other models seems to be saved and loaded without problems into OSGT including texture data. I've tested it with the OSG-Data clock.osgt, for example. But actually I didn't yet get the difference. Thank you! Cheers, Johannes -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=55180#55180 ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Serialization of osg::Image data into OSGT
Hi, I have some objections. The textual format in my understanding is for portability and debugging. Texture data can be saved as reference to a file, so textures are included but not as a BLOB. I simply do not like the idea of scrolling through a 100Mb textfile looking for some stateset when there is garbage binary data obfuscating the structure. Why do you need to have the textures saved directly into the file? Personally I prefer keeping references, this makes the data exchangeable. If your problem stems from wanting a compact archive (i.e. single file) containing a bigger data set, then use the archiving capabilities of OSG. Nevertheless: As long as serializing into the text file stays strictly optional I don't have real issues with it. cheers Sebastian Hi guys, some time ago I discoverd that inlining osg::Image data into the native OpenSceneGraph serializer formats is possible for the binary format (OSGB), only. Now that we also need to support inling osg::Image data in the .osgt format, I am curious to ask why this is currently not supported by the OSG? As there is at least one Public Domain Base64 encoder/decoder available, one might consider including that into OSG and using it to put the binary osg::Image data into the osg-text stream. Thoughts? Best regards, Johannes lightweight-replace-engine: A lightweight C++ template based text document preprocessor - https://code.google.com/p/lightweight-replace-engine/ -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=55126#55126 ___ 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
Re: [osg-users] Serialization of osg::Image data into OSGT
Hi Sebastian, I get your points. The situation we come from is: We have Image data that is produced during application runtime that never existed on disk separately. So our osg::Image has no filename defined. So we decided to inline the data rather than pushing them to disk. When writing our data into OSGT, the WriteImageHint=IncludeData gets accepted, but nothing will get written as OutputStream.cpp checks for binary mode. Then the result is an empty definition of osg::Image inside the OSGT. As far as I remember that does not even produce a warning. Now if you would like to have OSGT and OSGB have to behave equivalently, one might consider, to never use “IncludeData” or to extend OSGT to inline the data regardless of its file size. In the end the users must choose whether they are fine with increasing their file sizes by image data when using IncludeData in ASCII mode. But at least then the OSG behavior is consistent with its plugin options. Cheers, Johannes -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=55187#55187 ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
[osg-users] Serialization of osg::Image data into OSGT
Hi guys, some time ago I discoverd that inlining osg::Image data into the native OpenSceneGraph serializer formats is possible for the binary format (OSGB), only. Now that we also need to support inling osg::Image data in the .osgt format, I am curious to ask why this is currently not supported by the OSG? As there is at least one Public Domain Base64 encoder/decoder available, one might consider including that into OSG and using it to put the binary osg::Image data into the osg-text stream. Thoughts? Best regards, Johannes lightweight-replace-engine: A lightweight C++ template based text document preprocessor - https://code.google.com/p/lightweight-replace-engine/ -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=55126#55126 ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
