Dirk Reiners wrote: > Marcus Lindblom wrote: >> Other dev priorities from my point of view: >> - Getting 1.8 out the door is good. >> - Focus on 2.0 build. >> - Getting everyone in on the 2.0 release game. >> > Easier said than done. Quick poll: what would we need to do to make you > (meaning everybody who reads this) move to 2?
For myself, exactly what I said. Our current project is 50-70% complete and 3-6 months away from delivery, so we will stick to CVS/1.8 for that. Once the 2.0 scons build is ready for the public, we can start trying it out, giving input on what to port and start submitting patches. This is if it has all functionality in 1.8 that we use (which is pretty basic, graph + shaders + FrameBufferObject) and has no really serios bugs (it needs to start and run, and blockers need to have workarounds). I think I can see us trying 2.0 beta early next year, as we move our current project into finalization mode and start looking to the next. There has been talk to migrate a few other code-bases (which use WTK, Optimizer and a home-grown SG) to OpenSG where I work. I'm thinking 2.0 for them, as there won't be begin/endedit (gentler learning curve) and that API will be what is supported over time. Our 2.0-project will then be a benchmark of sorts to see if that is possible. I would like to know how stable is 2.0 at the moment? (i.e. bugs to fix and api-changes to make). How far down the road are we? Cheers, /Marcus ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
