I was reading some web page talking about MFC and Windows API saying that MFC isn't the way to go. It is restricting and you can't do as many things with it. I was wondering your opinion on views on MFC and Windows API. Thanks for you help. Really appreciated.
There are loads of previous threads on this....nevermind....
WinAPI is the natural starter........you learn more cuz your forced to do more.....there arent many shortcuts......
MFC is better for fast turnaround and offers a level of abstraction from the WinAPI......You can pump out a MDI or Database app pretty quickly without the laborious coding needed each time......The downside is that you can get unstuck if you dont have experience of the WinAPI
Start with WinAPI (Get Petzold) then if you wish to go on, start MFC
Okay summed up:
API:
-has a broader scope and flexibility
-"no short-cuts"
MFC:
-faster coding
-shorter range and much less flexible than the API
Feel free to add to this list.
--Garfield
1978 Silver Anniversary Corvette
MFC:
-faster coding
-shorter range and much less flexible than the API
-slower
>> -slower <<
Yes! Big. Very BIG!!! Program for optimization.
--Garfield
1978 Silver Anniversary Corvette
Well I just got my Learning Visual Studio 6.0 in 21 days books and it works with MFC I noticed. I am also getting a MFC book in the mail pretty soon so sounds like I am starting with MFC. Do you think I will be able to switch over to Windows API after doing MFC will I unlock some of the things I couldn't do with MFC? Well thanks for all your answers.
Ryan
>> Do you think I will be able to switch over to Windows API after doing MFC <<
It would be harder than going from API to MFC. But, it's possible.
1978 Silver Anniversary Corvette
yeah but API is already harder from what I hear so yeah it will be harder to go from MFC to API also if a program uses MFC42.dll does that mean it was built with mfc cause I noticed ICQ uses it.
Ryan
