Re: [osg-users] [osgPlugins] Reader-Plugin Callbacks for unsupported data-types

2012-06-13 Thread Robert Osfield
Hi WeSee,

On 13 June 2012 05:17, We See alois.wis...@swiss-simtec.ch wrote:
 My suggestion would be common for all plugins.

I can't see a plausible general purpose callback system for all
plugins, the loaders all target such different types for file formats
that they really have next to nothing in common.  Now if you have a
suggestion got for it, put it forward.  Please bare in mind that I
won't merge changes that have a high complexity overhead for a small
gain. For very niche tasks like extended loaders one will really have
to justify every line of code and keep it localized to not effect the
rest of the OSG code base.

In very special cases there may be opportunities to handle elements in
some of the plugins.  OpenFlight may be one of them, but to support it
one would need a specific solution to handle the types of records that
OpenFlight has.

 Is there a person responsible for all plug-ins?

There is no single person responsible for all the plug-ins.  I am the
overall project lead and am responsible for merging the majority of
submissions to the OSG code base.  In case like OpenFlight plugin I am
not the lead developer, and others have write access such as Paul
Martz and Brede Johansen.

Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


[osg-users] [osgPlugins] Reader-Plugin Callbacks for unsupported data-types

2012-06-12 Thread We See
Hi,

When reading models in OpenFlight format, not all data will be read (i.e. 
surface material code or feature id will not be read). But some application 
need this data, therefore my idea is, there could be a callback-function, which 
the reader-plugin is calling when it reads an unsupported data-type (Similar to 
update-callbacks). So the application could solve the problem.

Are there any comments or drawbacks about this idea?

@Robert Osfield: Does such a solution have a change to come into the trunc of 
osg?

Thank you!

Cheers,
WeSee

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=48025#48025





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] [osgPlugins] Reader-Plugin Callbacks for unsupported data-types

2012-06-12 Thread Robert Osfield
On 4 June 2012 14:06, We See alois.wis...@swiss-simtec.ch wrote:
 Hi,

 When reading models in OpenFlight format, not all data will be read (i.e. 
 surface material code or feature id will not be read). But some application 
 need this data, therefore my idea is, there could be a callback-function, 
 which the reader-plugin is calling when it reads an unsupported data-type 
 (Similar to update-callbacks). So the application could solve the problem.

 Are there any comments or drawbacks about this idea?

 @Robert Osfield: Does such a solution have a change to come into the trunc of 
 osg?

I don't have any opinions on OpenFlight as it's not my area of
expertise - I'm not the plugin author so I'd defer to others about
OpenFlight format specifics.   The possibility of adding custom
handling of reading/writing I'm open to, but I'll defer to others with
a bit more experience with coding on the OpenFlight plugin to provide
their more learned opinions.

Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] [osgPlugins] Reader-Plugin Callbacks for unsupported data-types

2012-06-12 Thread We See

robertosfield wrote:
 On 4 June 2012 14:06, We See  wrote:
 
  Hi,
  
  When reading models in OpenFlight format, not all data will be read (i.e. 
  surface material code or feature id will not be read). But some application 
  need this data, therefore my idea is, there could be a callback-function, 
  which the reader-plugin is calling when it reads an unsupported data-type 
  (Similar to update-callbacks). So the application could solve the problem.
  
  Are there any comments or drawbacks about this idea?
  
  @Robert Osfield: Does such a solution have a change to come into the trunc 
  of osg?
  
 
 I don't have any opinions on OpenFlight as it's not my area of
 expertise - I'm not the plugin author so I'd defer to others about
 OpenFlight format specifics.   The possibility of adding custom
 handling of reading/writing I'm open to, but I'll defer to others with
 a bit more experience with coding on the OpenFlight plugin to provide
 their more learned opinions.
 
 Robert.
 ___
 osg-users mailing list
 
 http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
 
  --
 Post generated by Mail2Forum


Hi Robert,
My suggestion would be common for all plugins. Is there a person responsible 
for all plug-ins?

WeSee

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=48262#48262





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org