I'm encouraged to hear that this process works for Python. OSG already has a wiki, and although there is some documentation present, I'd hardly call it a community-written book as you appear to be describing.
This is my fear with the "OSG Recipes" book -- If no one is willing to write and post documentation to the OSG wiki, will they be willing to write and submit material for a recipes book? We'll see; Bob and I are still intending to launch it in the near future. Paul Martz Skew Matrix Software LLC http://www.skew-matrix.com +1 303 859 9466 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Martin Beckett Sent: Monday, February 09, 2009 10:24 AM To: [email protected] Subject: Re: [osg-users] OSG Books (was: RE: Number of contributors) Could I suggest a wiki cookbook which could then be turned into a printed book? This seems to have worked for Python (the O'Reilly Python Cookbook is in it's 3rd Ed) Paul's excellent intro book covers getting started and the source provides the details but there is a need for 'the OSG way to do X' guide. I can certainly think of a dozen questions which are more community type answers than strictly programming. eg. Whats the best way to handle something like a grid which is part of the scenegraph but not part of the model? Do I store things like switch/PAT nodes in the file or create them from scratch when I load it? Martin _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
