Tim Moore wrote:
You don't need to do anything special for a ReaderWriter that you wish to
link into your application. You write the class in exactly the same way,
including the REGISTER_OSGPLUGIN macro. Your plugin will be registered early
and OSG will use your code to load that file
Hi Thomas,
as far as I know there's no developer documentation that describes the steps
for writing a new readerwriter plugin. You are welcome to write down your
experiences while developing your own readerwriter.
You will probably first need to create a new Wiki account. See
That's good to know, I've registered for a wiki account and will do my best to
post useful tips that I figure out. Most of the information I've seen on there
up to this point seems to be related to developing around OSG rather than
developing to extend it, which seems a little silly given how
Hi Thomas,
In svn/trunk there is support for extensible native binary format, the
serialization scheme that underpins this also support reading/writing
to ascii and xml format as well. This will of be part of the 2.9.9
I'll make next week. The author of this work is Wang Rui, and he's
wirtten a
Hi Robert,
Thank you for the time you take to make your response, and the level of
information you included in it. Unfortunately I think you may have
misunderstood my original question. I was not inquiring about the possibility
of serializing my own classes into the native binary format, but
Hey everyone,
Is it possible for osgDB to load classes implementing ReaderWriter
functionality out of my application binary, or must they be stored in a
separate .so in the plugin directory? If so, are there any special directions I
need to follow to get this working?
Secondly, what is proper
6 matches
Mail list logo
