Want to start making some applications beyond the cli in windows. I heard some things about MFC but this was a while back and I don't know much about it other than a few 8 year old articles I've seen.
Well, if you're going to use something other than MFC, be sure it's not some cross-platform toolkit with GNU license. They are generally badly designed.
Name:
Anonymous2008-06-17 13:59
>>5
On the other hand, platform specific toolkits suck too. The only sane choice is to keep using the command line.
- It's practically undocumented (don't point me at their doxygen crap unless you have used it in a large project and found it helpful; I for sure found it completely useless).
- It claims to use native widgets, but it often uses them in strange ways and alters their default behaviour so that your programs won't look or feel native on any platform.
- It suffers from tons of bad design decisions made in its early days, which practically forces you to write a wrapper to shield your code from its suckiness. They should've completely rewritten it years ago.
- It fails to fullfill the #1 requisite of cross-platform GUI toolkits: being cross-platform. You have to actively look out for platform-specific functionality, which is only spastically pointed out in their documentation.
Name:
Anonymous2008-06-17 18:23
>>13
I'm having a good time so far using wxWidget. I was a little peeved that the slider only supported int and not double, and some minor stuff like that, but overall it works well and lets me do quick crud toolbars and stuff with the dialog designer. In a few weeks I went from being a green "C++ console app programmer" to making a cool GUI app integrating NI drivers, wxAUI, multi-threading, etc. I've found the date, picture, and thread classes very useful.
MFC is really really nice though, as in good-looking (check out the office examples - awesome), and has more meat in widgets than wxWidgets, but the wizards, FABULOUS class names & hungarian notation, etc. make my eyes bleed.