Didn't mean to start a discussion really, was just my two cents.
I think we are on the same page - and it seems we have a similar history too (in terms of where we come form with toolkits). :-)
Didn't mean to start a discussion really, was just my two cents.
I think we are on the same page - and it seems we have a similar history too (in terms of where we come form with toolkits). :-)
==========================signature=============== ==================
S.O.L.I.D principles (use them!):
https://en.wikipedia.org/wiki/SOLID_...iented_design)
Do you write clean code? - if you are TDD'ing then maybe, if not, your not writing clean code.
I use both. Try Qt first.
OK, so why? Is it easier to learn Qt first and then pick up wxWidgets? Some other reason?I use both. Try Qt first.
<=== The Great Pumpkin says ===>
Please use CODE tags when posting source code so it is more readable. Click "Go Advanced" and then the "#" icon to insert the tags. Paste your code between them.
The question is tricky because Qt and wxWidgets are really on different layers of software development. Correct me if I'm wrong but wxWidgets is basically a toolkit that wraps functionality of other toolkit engines into its own APIs ("wxWidgets defines a common API across platforms, but uses the native graphical user interface (GUI) on each platform, so your program will take on the native look and feel that users are familiar with."). There is even a port of it that uses Qt as its backend.
Qt on the other hand is an application development framework and goes far beyond just being a toolkit.
Of course I may be biased but I'd say you should go for Qt because by using it you will be able to do so much more compared to wxWidgets.
Qt works great on Linux and Mac OS X with native look.
Bookmarks