On Tue, Dec 15, 2009 at 11:23 PM, Jan Pečiva <[email protected]> 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 performance cull traversal. For me Inventor is good example of object composition gone mad, seemingly a good idea, but in practice it breaks what should be the key asset of a scene graph - performance. > 2. if there is something where SGI experts failed the design, the place is > well documented with examples and explanations of specialties of the design You can't fix the state system in Inventor, it's broken. The only way to fix it is to dump it and adopt parental inheritance rather than sibling inheritance. It's worth noting that Performer and Inventor existed side by side because neither could solve the full range of problems that scene graph users wanted to tackle. Inventor might be been more OO inspired, but Performers parent inheritance scheme made it far more suitable for high performance, something that Inventor could never attain and SGI knew it. The OSG is far more inspired by the example of Performer than Inventor, but is has strong OO routes, which enables it to be extensible whilst still retaining the performance. > I wish OSG to constantly improve and to become even better with powerful and > intuitive API. > To name the strengths of OSG: > - it follows the latest technology and design patterns > - there is a working mailing list, patches and discussions There are political and technical reasons why Inventor has been on life support, and the OSG is alive and healthy. >> >> [...] for the specific purpose of one user [...] >> > > Maybe two? > But we understand, you are the authority deciding how it will be... > Reference for other people: By the alias extension, people would not lose > anything of the current plugin features - all the current extension > protection would still work as well as it is working just now. They would > just get one additional feature for OSG. Your suggestion on forcing aliases onto plugins will break existing plugins. For instance take the the quicktime plugin which handles many different formats - it requires the extension to have a specific mapping to file format to enable it to know which format to use. Are we to tell Apple to adopt your scheme for re-interpreting extension names? Clearly your suggestion can't be applied to all plugins, just ones that are agnostic about their extensions. I have given already given two ways you can already do this - even one telling you how to implement the scheme you want - injecting aliasing directly into the plugin, just doing it manually. Please re-read my posts. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
