On Thu, 2010-07-29 at 16:36 +0100, Robert Osfield wrote: > Hi Jeremy, > > Great news to hear you've beaten your illness.
Yeah, it was an interesting year and a half for sure. Now I just need some time for the new immune system to get strong and I'll be better than ever. :) > Interesting thoughts on osgWidget, not one I was expecting from you, > but I can see the logic behind it. osgQt does require Qt which isn't > a small dependency so for a lightweight users interface osgWidget > still has value. Before we could fully replace osgWidget with osgQt I definitely think it still has value; it just doesn't fill (what I believe) is it's niche. (more below) > we'd need to address performance and threading issues that Qt > introduces. > > When you say osgWidget should have been far small and more generic > could you explain what you have in mind for a what osgWidget should > have been? Sure. This is something I touched on briefly earlier this year as I was recovering but still frequently in the hospital, so couldn't produce much code. What osgWidget "tries" to be right now is a lightweight 2D interface library. Widgets are always quads, Windows are always Geodes, etc. What osgWidget "should" be is an even lighter wrapper around any generic Drawable. It should feed input events to these Drawables in an OSG-like way (perhaps by accumulating input data from the mouse/keyboard and stuffing it into a NodeVisitor). It should provide some very basic "positioning" rules for Widgets using their bounding boxes, not their dimensions in 2D space. Once that is done, I can take the "old" osgWidget and turn it into simply a 2D implementation of the real, more flexible "new" osgWidget. Quads would be a 2D, 4-vertex specialization of Widgets... so forth and so on. I'll be simplifying things immensely by providing just the hooks, and by NOT trying to cover every possible use someone might have. First of all, people will reach for things like QT instinctively if they need a FULL BLOW 2D interface in their app. Secondly, there are so many modern UI classes that people expect in any reasonable UI toolkit that providing even one opens the door to the question: hey, where are the rest? :) > Robert. > > On Thu, Jul 29, 2010 at 3:27 PM, Jeremy Moles <[email protected]> wrote: > > As more work goes into osgQt towards OSG3 (and as we get closer to > > having full, fist class 2D widgets), I think that osgWidget (in it's > > current form) should be removed. It was designed with the very futile > > goal of trying to be a 2D UI kit, when it should have been far smaller > > and far more generic from the very beginning. > > > > I have been working on--in-between paid OSG work and medical > > maintenance--this newer version, but it is not ready for anyone to look > > at. > > > > And also: I was officially declared "in remission" about a month ago, so > > my short (but interesting!) bout with blood cancer at 29 is over. > > Yay. :) > > > > _______________________________________________ > > 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 _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
