Hi All,
after trying to clean up the lib deps a bit I understand better what the
problem
is. ProxyGroup needs SceneFileHandler and forces Group to depend on FileIO, and
obviously FileIO depends on Group. That's kinda annoying...
I see a few options:
- Split off the base pieces that are visible from the outside and put them
inside System. That's the current version, but it breaks down if those pieces
need other libs (which can happen fairly quickly, like FileIO needing GraphOps
needing Geo needing pretty much the whole thing...).
- Split the libs more finely into basic pieces and the parts that need higher
level functions. For a node to need FileIO is a fairly unusual thing, IMHO. The
danger is very finely split libs that are hard to understand. I see that danger
anyway, if we want to get to a point where whatever depends on an external lib
is in a separate OSG lib, so we will need to have a reasonable way to handle
that. Having info which library a class is in in the docs will go a long way
towards that. I opened a ticket for a way to automate that.
I'm tending towards 2. Splitting the components into base and non-base pieces
seems a bit hard to keep functional, having cleanly split pieces smells better
to me. For my current problem I would open a new lib OSGComplexNodes to contain
ProxyGroup. There's probably more to go into that, maybe Terrain or a Point
node
that I will be working (or rather have somebody working on ;) fairly soon.
Comments?
Dirk
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Opensg-core mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-core
