From: Simon Francis (thejello_at_[hidden])
Date: 2007-10-21 10:25:35
I agree, wxWidgets isn't very "C++ like". For what I would call an ideal C++
widget library look at creating GUIs with Adobe's Future through Eve. It is
a GUI library without inheritance.
On 10/21/07, Felipe Magno de Almeida <felipe.m.almeida_at_[hidden]> wrote:
> On 10/21/07, Jurko Gospodnetic' <jurko.gospodnetic_at_[hidden]> wrote:
> > Hi Felipe.
> Hi Jurko,
> > > I'm already working on a GUI library for some time (three weeks). And
> > > come up with some designs and code.
> > We use wxWidgets for a portable GUI framework and it works fine for
> > us. Good points are:
> I'm well aware of wxWidgets.
> > I do not mean to infer that no one should explore implementing the
> > 'ultimate GUI library' but from my viewpoint it seems more reasonable to
> > hook up to this project and mold it into something better if something
> > does not suit you.
> Not to be too hard on wxWidgets, but wxWidgets isn't even near what I
> expect from a C++ GUI library.
> > The whole GUI support has so many niches and platform
> > specific implementation details in it that I do not believe one can make
> > it ideal but only 'good enough' and strive to constantly improve it.
> I agree with you here.
> > And an existing library such as wxWidgets already has a giant lead in
> > right direction.
> But I disagree with this.
> > Starting a boost.GUI library just for the sake of 'implementing the
> > whole world as a part of boost' does not seem like a good way to go. One
> > possibly good way I see to go about this would be to merge with an
> > external library such as wxWidgets,
> To get anything near of what I want, it would be needed to rewrite
> wxWidget from scratch, so I don't see much difference in approach.
> > the same as was done for the
> > (excellent!) asio library, with great benefits for both sides.
> Asio was at boost quality expectations, and that's why after review it
> was accepted. I believe those are two completely issues.
> > Boost would get GUI support and the GUI library would get the benefits
> > existing excellent boost libraries and not have to reimplement them
> Why doesn't wxWidgets use boost? It doesn't have to be included in
> boost to use it. boost.asio used boost even before it was added
> (boost.bind) IIRC.
> > (thus removing the need for double maintenance efforts). Also, users
> > would find it easier to learn/access both of the libraries.
> I can't see how. IMO, there would probably be more discussion than
> development, because of the two different views at C++ development
> from wxWidgets developers and boost developers.
> > Just my 2 cents worth...
> > Best regards,
> > Jurko Gospodnetic'
> Felipe Magno de Almeida
> Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk