On Tue, Dec 15, 2009 at 11:23 PM, Jan Pečiva pec...@fit.vutbr.cz wrote:
I like Coin (Open Inventor clone, OSG competitor) since:
1. it has intuitive consistent API and excellent design
IMHO, Inventor has a terrible design for a scene graph, the state
system breaks the ability to have a high
Robert Osfield wrote:
On Tue, Dec 15, 2009 at 11:23 PM, Jan Pečiva pec...@fit.vutbr.cz wrote:
I like Coin (Open Inventor clone, OSG competitor) since:
1. it has intuitive consistent API and excellent design
IMHO, Inventor has a terrible design for a scene graph, the state
system
Hi John,
On Wed, Dec 16, 2009 at 12:15 PM, Jan Pečiva pec...@fit.vutbr.cz wrote:
We can never agree in the discussion. Inventor became de-facto standard for
visualization and simulations for its design that was revolutionary in 90's.
Inventor was the defacto standard in the 90's for scientific
Hi John et. al,
On Wed, Dec 16, 2009 at 1:34 PM, Robert Osfield
robert.osfi...@gmail.com wrote:
To be clear automatically setting ReaderWriter::_supportedExtensions
from osgDB won't be generally be safe. For specific plugins it might
be possible to use it, and for these I would recommend you
Paul Martz wrote:
Thrall, Bryan wrote:
When you add an alias, though, aren't you saying to the plugin,
Trust me, even though you don't recognize the file extension, handle
it?
Hi Bryan - Exactly! This is what I had on mind. If I tell the plugin:
This is MY alias, it should take my word and
I think there is no need to do any work in the plugins.
Registry::createLibraryNameForExtension(const
std::string ext) gives you the name of the library (plugin) you have to
load having in mind all the aliases. And I like this design and I think it
is ok
Nick
http://www.linkedin.com/in/tnick
On 14/12/09 9:27 PM, Paul Martz wrote:
I have always been able to register an extension alias by calling
addFileExtensionAlias directly from my code, the calling readNodeFile
passing in a file name using the alias.
What extension/plugin did you use it with?
As I understand it
Hi John,
On Mon, Dec 14, 2009 at 10:21 PM, Jan Pečiva pec...@fit.vutbr.cz wrote:
OSG plugin takes one look at the foo extension and returns an error.
(This is correct behavior; the .osg plugin doesn't support the foo
extension.)
This is exactly the point I am trying to point out! The plugin
On 15/12/09 10:29 AM, Ulrich Hertlein wrote:
As I understand it 'addFileExtensionAlias' really only works with plugins
that don't check
the extension name.
I should add: ... or that have the extension in their supportsExtension list.
From a software engineering p.o.v I'd say this isn't
Ulrich Hertlein wrote:
On 15/12/09 10:29 AM, Ulrich Hertlein wrote:
As I understand it 'addFileExtensionAlias' really only works with plugins that
don't check
the extension name.
I should add: ... or that have the extension in their supportsExtension list.
Exactly.
It will not
Hi Ulrich,
On Tue, Dec 15, 2009 at 9:43 AM, Ulrich Hertlein u.hertl...@sandbox.de wrote:
On 15/12/09 10:29 AM, Ulrich Hertlein wrote:
As I understand it 'addFileExtensionAlias' really only works with plugins
that don't check
the extension name.
I should add: ... or that have the extension
Robert Osfield wrote:
Hi John,
On Mon, Dec 14, 2009 at 10:21 PM, Jan Pečiva pec...@fit.vutbr.cz wrote:
OSG plugin takes one look at the foo extension and returns an error.
(This is correct behavior; the .osg plugin doesn't support the foo
extension.)
This is exactly the point I am
Hi John,
On Tue, Dec 15, 2009 at 10:49 AM, Jan Pečiva pec...@fit.vutbr.cz wrote:
I will do, although it is nearly more work than to, say, improve these
aliases. Inventor plugin (ReaderWriterIV) does not have istream methods
implemented. I will consider to implement them and submit them
Hi Robert,
On 15/12/09 11:33 AM, Robert Osfield wrote:
On Tue, Dec 15, 2009 at 9:43 AM, Ulrich Hertlein u.hertl...@sandbox.de
wrote:
On 15/12/09 10:29 AM, Ulrich Hertlein wrote:
As I understand it 'addFileExtensionAlias' really only works with plugins
that don't check
the extension name.
Paul Martz wrote on 2009-12-14:
Thrall, Bryan wrote:
When you add an alias, though, aren't you saying to the plugin,
Trust me, even though you don't recognize the file extension, handle
it?
Hi Bryan -- That might be what you're saying, but that's not how
osgDB::Registry is interpreting
Ulrich Hertlein wrote:
Isn't the following the case?
- plugin X will automatically be associated with extension 'X'.
- to support more extensions the plugin must say that it supports 'Y' *and*
the Registry must map extension 'Y' to 'X', because otherwise plugin 'X'
won't be
Robert Osfield wrote on 2009-12-15:
FYI, if you really want to try forcing a plugin to handle extensions
it was never designed to handle you could try loading the plugin and
then calling supportsExtension on it.
Just to be pedantic, supportsExtension() is protected, so you'd need to:
1)
Ulrich Hertlein wrote:
What extension/plugin did you use it with?
I've used this with proprietary plugins that support multiple different
extensions for the same file type.
As I understand it 'addFileExtensionAlias' really only works with plugins that
don't check
the extension name.
I
I think we've all been saying supportsExtension when we meant to say
axxeptsExtension (which is public). I know I always get them confused.
Paul Martz
Skew Matrix Software LLC
_http://www.skew-matrix.com_ http://www.skew-matrix.com/
+1 303 859 9466
Thrall, Bryan wrote:
Robert Osfield wrote
On 15/12/09 3:57 PM, Paul Martz wrote:
Ulrich Hertlein wrote:
Isn't the following the case?
- plugin X will automatically be associated with extension 'X'.
- to support more extensions the plugin must say that it supports 'Y'
*and*
the Registry must map extension 'Y' to 'X', because
Paul Martz wrote on 2009-12-15:
I think we've all been saying supportsExtension when we meant to say
axxeptsExtension (which is public). I know I always get them confused.
acceptsExtension() checks if the plugin handles that extension; if you want to
add an extension so the plugin handles it,
Hi Bryan,
On Tue, Dec 15, 2009 at 2:49 PM, Thrall, Bryan
bryan.thr...@flightsafety.com wrote:
Yep, I was proposing that users of the Registry could interpret adding an
alias differently than is currently implemented (exactly as Jan did).
But it sounds like Robert isn't open to changing the
why not using Registry::createLibraryNameForExtension or
Registry::getReaderWriterForExtension it checks the aliases and returns
the right thing
Nick
http://www.linkedin.com/in/tnick
Sent from Gümüşsuyu, İstanbul, Turkey
On Tue, Dec 15, 2009 at 5:34 PM, Robert Osfield
Robert Osfield wrote:
Hi Bryan,
On Tue, Dec 15, 2009 at 2:49 PM, Thrall, Bryan
bryan.thr...@flightsafety.com wrote:
Yep, I was proposing that users of the Registry could interpret adding an alias
differently than is currently implemented (exactly as Jan did).
I like Coin (Open
Hi John,
On Mon, Dec 14, 2009 at 1:17 PM, Jan Pečiva pec...@fit.vutbr.cz wrote:
Question: Is is possible to register the ivx alias?
You have two options, to preload your plugin so it gets tried before
any other plugin so can intercept and handle all .iv file reads, or to
use an osgDB::Registry
Robert,
thanks for the comment, however it does not work. Do I need to
extend/patch OSG?
An investigation showed that many plugins check once again in readNode
method whether the extension is accepted. At this moment, ivx is
refused. I am not sure, but the explicit alias that user makes
Hi John,
Extension alias certainly does work - it's used all the time by osgDB,
go look inside src/osgDB/Registry.cpp to see lots of examples of it in
action. What is happening at your end I can't guess, I don't have
your code.
Robert.
On Mon, Dec 14, 2009 at 2:08 PM, Jan Pečiva
I have always been able to register an extension alias by calling
addFileExtensionAlias directly from my code, the calling readNodeFile
passing in a file name using the alias.
I have never tried the asserts that you are using.
If this is broke, this is a new breakage. Perhaps by debugging the
Just to convince myself that this really does still work, I took an
existing app and added the following code to the top of main():
osgDB::Registry::instance()-addFileExtensionAlias( foo, osg );
osg::ref_ptr osg::Node testload(
osgDB::readNodeFile( cow.foo ) );
Then I
OSG plugin takes one look at the foo extension and returns an error.
(This is correct behavior; the .osg plugin doesn't support the foo
extension.)
This is exactly the point I am trying to point out! The plugin reports
that it does not support the extension!
I am telling that this is NOT
Paul Martz wrote on 2009-12-14:
Jan Pečiva wrote:
OSG plugin takes one look at the foo extension and returns an error.
(This is correct behavior; the .osg plugin doesn't support the
foo
extension.)
This is exactly the point I am trying to point out! The plugin reports
that it does not
Thrall, Bryan wrote:
When you add an alias, though, aren't you saying to the plugin, Trust me, even
though you don't recognize the file extension, handle it?
Hi Bryan -- That might be what you're saying, but that's not how
osgDB::Registry is interpreting it. :-)
Without aliases at all,
32 matches
Mail list logo
