what is better for windows development? i was thinking about buying programming windows but im not sure if mfc is better or not.
Printable View
what is better for windows development? i was thinking about buying programming windows but im not sure if mfc is better or not.
There are free GUI Frameworks out there, so you don't need to buy MFC if you don't want to.
But I'll agree that a Framework is far better than pure Win32 API.
Typical good frameworks are wxWidgets or maybe Qt.
They are portable, and in some ways, possibly simplified.
You would be surprised of the capabilities of C++, that the API, which is C, cannot even begin to fathom. In essence, a good framework is ALWAYS better than the raw api. Especially for C++.
MFC is a Framework/wrapper itself and not an API, so...
MFC is not portable. It's locked to Windows and Microsoft Visual C++.
2 questions
is mfc really not free?
and
is all the api's for windows just in windows.h?
MFC is not free (requires Standard+ version of Visual Studio, which is not free).
All APIs are located in windows.h.
It depends on your application. MFC is better for GUI, API is better for core functionality like multithreading, network connectivity, direct hardware interfaces. If you have no prior programmign experiece I recommend you start with the API, which is much easier to learn. MFC can be a bit obtuse at time.
Learning the API itself is not necessary and painstaking. It's better to specialize yourself in the framework you use instead.
Otherwise you're going to end up learning both, which is usually a waste of time. Win32 API is not user friendly.
mfc is also $300 mininum and the api seems kind of lower-level code which is what i like, even if its in C
MFC is not C.
It's your choice, ultimately. You can try out several GUIs before deciding. If none of the free ones suits your fancy, then you can try MFC.
ROFLMAO, elysia, the api is simpler and more straight forward than MFC any day of the week. It's about as user friendly as you can get, I have no idea where you get off implying that MFC is in any way shape or form user friendly. Maybe you just can't understand a function description without trying to think of it as a class.
Oh really?
I've had my share of experience with both and I find MFC a thousand times simpler and easier.
Wow.
Oh really?
Maybe that's the case for YOU, but not necessarily the case for OTHERS. There's a REASON why frameworks were invented and why so many companies use MFC. I wonder why...
Duh.