HI Wang Rui, On Tue, May 18, 2010 at 4:07 PM, Wang Rui <[email protected]> wrote: > The entire code will be really clean and easy-to-read if we could make > most class methods as set/get properties. Beginners will also benefit > from that because of fewer steps to follow and then easier to learn. > I'm looking forward to keep improving OSG and introducing it to more > and more developers. :)
A worthy goal. W.r.t set/get property parings, this is indeed the best approach for most classes. There are a couple of expects such as Vec/Matrix/Quat/Plane classes where replacing .x() with getX() etc. would be clumsy, but these are the exceptions. > >> W.r.t 3D GUI/GUIChan this sounds interesting - one of the current >> restrictions of osgWidget is that it's designed around 2D projections, >> so it'd be good to loose this constraint. I'm not quite sure what you >> mean byu GUIChan though. >> > > Unfortunately, GUIChan seems to be designed on 2D screens, too. The > major advantage of GUIChan is non-intrusive, and easy to integrate and > extend. I'm investigating other 3D GUI tools at the same time, for > instance, CEGUI, Agar and Gigi. Maybe we could find a better GUI > system for integrating with the 3D world out of them. One approach to integration of 2D GUI's is to leave them in their 2D projection by render them to a texture then use a texture quad and the osgViewer::InteractiveImageHandler to re-project mouse events into the quads local coordinates. This is what is done for webbrowser integration right now. Robert. _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
