-----Original Message----- On Behalf Of Matt S Trentini Subject: [boost] Re: [gui] The Big Picture [and wxWidgets]
Heya Rene,
That all sounds great; perhaps we should be helping out the wx guys rather than come up with our own library...?
Does anyone else have any good reason why we should create a completely new library assuming that those issues are addressed? (License could be one problem quite aside from the technical issues.)
Keep in mind that starting a GUI library from scratch is going to take *significant* time.
And is wxWindows our "best bet"? It's certainly going to be easier
than
trying to convince the Qt folks to get rid of their preprocessor... ;)
It'd be fantastic if all the issues I brought up with wxWidgets were addressed and we ensured that it worked well with the other boost libraries.
Is there anything anyone else wants or needs that wxWidgets couldn't supply?
[Brian Braatz] I have been watching this whole thread closely, and just wanted to send out a mail in support of the idea of collaboration. I have written many UI Frameworks ON TOP of things like MFC and OWL, and even just writing something ON TOP Of one of those things is a huge task. In one case this was my primary job for several years. It is one of those things where to get something demo-able is easy. But "Completing" it is a different issue entirely. If you look at all the fundamental issues discussed in this thread, i.e. do we have our own point coordination system etc, you can see that there is more here than meets the eye. I will end my thoughts here with the (repeated) suggestion that making a thin layer above the current WxWindows will allow for a Boost.Gui in a short timeframe that has an incredible API interface. :) Brian