Robert Osfield wrote: > Hi Neil, > > On 11/30/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> Hi All, <snip> >> Voila. I'm now able to read 3DS files from URL's. The methodology >> should migrate to any datasource, though I haven't actually done so. >> I'd like to make it more elegant at some point in the future, but for >> now if you wanted to use it for a different plugin, you would need to >> re-engineer the plugin to use the data object buffer - not difficult, >> just niggling that one has to do it. >> >> If anyone is interested in looking at this approach, drop me a mail >> and I'll see about packing and sending it to you. > > I think this would be a local workaround for standard C style file > support rather than istream support. One could create a helper class > for this, but it needn't be a general requirement for all plugins.
This seems vaguely apropriate for me. I'm currently looking for a way to read and write via iostreams to/from a char buffer. Currently I make do with the .osg reader/writer and stringstreams, but as far as I can tell this also means losing textures (and other resources?). Ideally I'd like a char* backed iostream that handles binary io. That way I could use any iostream-capable writer (that should be all of them, right?) If anyone else has a good suggestion on how to create a (semi-)distributed scenegraph between independent machines (and programs), I'm all ears! -- - Ole-Morten Duesund Senior Developer Visual Development AS _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
