[EMAIL PROTECTED] wrote: > Hi all, > > we are using OpenSG 1.8 stable for our project. Now there is the question if > and > when we should switch to OpenSG 2.0. > I don't know much about 2.0 and the website is unfortunately down.
http://opensg.vrsource.org/ works for me? > So I have a few questions. > How mature/stable is 2.0? It hasn't been released, and there are still things that haven't been ported from 1.8 to 2.0 > What are the benefits of 2.0 (what do we gain)? Simpler pointer types, performance, better FBO/VBO support, Better plugin support... http://opensg.vrsource.org/trac/wiki/Dev/Changes1To2 > Is there anything we loose? There is stuff that needs doing, and that hasn't been categorized yet: http://opensg.vrsource.org/trac/wiki/Dev/FeaturesToPortFrom1to2 > How much work will it be to switch to 2.0 (is it really a switch or do we need > to rewrite large parts of our application)? Not that much rewriting, but 2.0 might not be ready for you yet. If you don't know me from the list, I am not one of the core devs, so they might have extra info about where things are going. I'm going to try to get PyOpenSG to run on trunk somehow, and that will hopefully yield some info about what needs doing that I can post on the wiki. /Marcus ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
