I use wxWidgets and remember dismissing Qt for two main reasons; Licensing and it seemed to me at the time, less intuitive than wxWidgets. However as my experience with wxWidgets amassed, I started the realize some of its shortcomings; most notably the fact, while it supports the STL, the framework is not built on it and makes the integration with my STL based objects harder and more expensive. Templates, are missing too. Plans exist to slowly start moving the code base, but this will certainly be a very slow process.

I however prefer the wxWidgets community based development (Qt new webKit integration, for instance is old news on wxWidgets) and a more easily reached support. The merits of Open Source I guess.

Originally Posted by brewbuck:Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.

Qt is really cool, if it was not there, I would have switched to Java!

Mario, I have wxPython. It looks a little ugly. Tell me, can we write really beautiful looking GUI also using wxWidgets? I do not mean more work on my part, I mean does it have nice looking GUI stuff also?

Tell me, can we write really beautiful looking GUI also using wxWidgets? I do not mean more work on my part, I mean does it have nice looking GUI stuff also?

Yes. You can build your own versions of GUI controls and elements (aka widgets) or download the work from someone else who made it available. Typically writing your own is very rewarding and will allow you to gain an intimate knowledge of the framework. I'd advise this method in your spare time.

wxWidgets uses the system own native controls, so I'm unsure as to why you are seeing ugly versions of these controls with wxPython. Probably it uses its own controlset based on Tk... dunno.

Originally Posted by brewbuck:Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.