Thread: C++ and ...

Originally Posted by Bubba

I use MFC with Win32 when needed. A lot of GDI+ is not in MFC but I must say MFC although not perfect is a far better approach to using the outdated, clunky Win32 API.

If you can understand C++ then MFC is a snap. I can write a complete dialog app in a couple of hours as opposed to days with Win32.

Bubba, you really need to learn using copy and paste. Because these things are very useful when programming in Win32. I have made so many Win32 programs that whatever I want to do, I can just copy it from somewhere. So I can make Win32 programs very quickly.

WIN32 API CANT BE OUTDATED BECAUSE IT IS THE ONLY API THAT WINDOWS USES.
Tell me, I'm wrong.
MFC IS based WinAPI, but just "tries" to "simplify" it.

Outdated in the productivity sense, I believe that's what Bubba meant.

The MFC is a wrapper for the Windows API. It's arguable that it's a good one. However it is undeniable that you simply can't compete (assuming both have an equivalent level of proficiency. One in MFC, the other in straight API) with a MFC programmer as fast as development times are concerned. You simply can't, Max. Don't pursue this further.

Don't put "try" in parenthesis. It makes you look ignorant. Because it succeeds in simplifying the API to a great extent.

If you want you can say that the Windows API allows you a fine grain control over your GUI development. I can agree with that. But the power is not in using only the MFC or only the Windows API. However advocates that is nothing more than a mindless zealot with little knowledge on windows development. The power is in using both.

Until you realize the merits of the MFC when compared to the windows API you will not progress much in windows development. Not at least to a level that makes you an interesting candidate for a software house. It's good you like the API. It's even better you are (hopefully) becoming proficient with it to the point of coding blindfolded. But ignoring the MFC, bashing on it, moving it to second plane and otherwise refusing to acknowledge its merits... is simply degrading you to the status of an ignorant.

Sorry mate. Don't mean to offend you. Just trying to open your eyes. Take it as you may.

> Everything else, but this sentence, makes sense

Because its context is explained in the next sentence.

Bubba, you really need to learn using copy and paste. Because these things are very useful when programming in Win32. I have made so many Win32 programs that whatever I want to do, I can just copy it from somewhere. So I can make Win32 programs very quickly.

You copy/paste your code everytime you need a particular job? Why? Put your codes in some functions, put all functions in a header and use them. But there is no need to do so, Microsoft has done this for you. MFC.

If it would be just a collection of functions, there would be no problems with it. But it defines some freaky types, that are needed in the functions, it requires using huge pointless classes for everything etc.

Of course you will have to use classes and new types when you are developing such a huge library.

Win32 is clean and simple. Plus when everything is based on it, why use those things that are basically the same thing when I am satisfied with Win32 itself?

Who said you must use that? If you are comfortable with Win32, go on with it.

Max what you are doing is that you draw everything to the extremes here, you say that "ok pure mfc is inferior to winapi", while that may be true (wont argue because I dont have enough experience coding these kind of apps), but mfc mixed with winapi will beat pure winapi. You say winapi is clean and simple, I say its bloated and utterly overcomplicated (probably has to be since its generic), its all a matter of personal taste but keep this in mind, it is always better to know how to do a task in 2 ways than in 1 way.