What is the MFC future
-
I plan to develop a new application with Visual C++ but I am wondering which library to use for the GUI design. I.e. MFC, QT.. and so forth. MFC is a native MS library and sounds nice but rumors say that it has no future. What are your thoughts? Would you start a new application with MFC? Thanks for your answers.
-
I plan to develop a new application with Visual C++ but I am wondering which library to use for the GUI design. I.e. MFC, QT.. and so forth. MFC is a native MS library and sounds nice but rumors say that it has no future. What are your thoughts? Would you start a new application with MFC? Thanks for your answers.
I use VC 6.0 MFC, but I am a retired (cheap) hobbyist. I like the doc/ view “feature”. It was suppose to simplify the windows messaging, but it made it more complicated. May "professionals" will say that MFC lets you build quick base UI for your application, but IMHO it is a shaky foundation to build onto, adding anything requiring more that friendly, quick user interface application is a challenge using MFC. That is why, again in my opinion, you see mostly dialog based sample codes here. The key is in detailed planning – what do you want your app to accomplish. And as far as future of MFC – I see a continuing trend to abuse “object oriented” hiding of the actual process and “foundation” is just another name for “wrapper”. In short – do not use MFC if you want true control of your code. Cheers Vaclav
-
I use VC 6.0 MFC, but I am a retired (cheap) hobbyist. I like the doc/ view “feature”. It was suppose to simplify the windows messaging, but it made it more complicated. May "professionals" will say that MFC lets you build quick base UI for your application, but IMHO it is a shaky foundation to build onto, adding anything requiring more that friendly, quick user interface application is a challenge using MFC. That is why, again in my opinion, you see mostly dialog based sample codes here. The key is in detailed planning – what do you want your app to accomplish. And as far as future of MFC – I see a continuing trend to abuse “object oriented” hiding of the actual process and “foundation” is just another name for “wrapper”. In short – do not use MFC if you want true control of your code. Cheers Vaclav
Vaclav_Sal wrote:
“foundation” is just another name for “wrapper”
MWC = "Microsoft Wrapper Classes?" :laugh:
The difficult we do right away... ...the impossible takes slightly longer.
-
I plan to develop a new application with Visual C++ but I am wondering which library to use for the GUI design. I.e. MFC, QT.. and so forth. MFC is a native MS library and sounds nice but rumors say that it has no future. What are your thoughts? Would you start a new application with MFC? Thanks for your answers.
-
I plan to develop a new application with Visual C++ but I am wondering which library to use for the GUI design. I.e. MFC, QT.. and so forth. MFC is a native MS library and sounds nice but rumors say that it has no future. What are your thoughts? Would you start a new application with MFC? Thanks for your answers.
MFC is burdened with several decades of legacy, and full of bad designs and ugly interfaces. You won't notice a lot of it when designing a small GUI project, but for serious, long-lived work, it is most certainly not a good choice. However, your choice depends a lot on the application you plan to build: - If you want to build one for the MS App Store, you probably have to build it on the basis of WinRT, not MFC. - If you want one that runs on Win7, WPF is a better, more modern library than MFC. - If in the long (or short) run you don't want to restrict your application to just Windows, you need a platform-independend framework like QT.
-
yu-jian wrote:
GUI developmeng is no future
What? Complete and utter rubbish. The UI is now more important than it has ever been.
I was brought up to respect my elders. I don't respect many people nowadays.
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier -
MFC is burdened with several decades of legacy, and full of bad designs and ugly interfaces. You won't notice a lot of it when designing a small GUI project, but for serious, long-lived work, it is most certainly not a good choice. However, your choice depends a lot on the application you plan to build: - If you want to build one for the MS App Store, you probably have to build it on the basis of WinRT, not MFC. - If you want one that runs on Win7, WPF is a better, more modern library than MFC. - If in the long (or short) run you don't want to restrict your application to just Windows, you need a platform-independend framework like QT.
-
I plan to develop a new application with Visual C++ but I am wondering which library to use for the GUI design. I.e. MFC, QT.. and so forth. MFC is a native MS library and sounds nice but rumors say that it has no future. What are your thoughts? Would you start a new application with MFC? Thanks for your answers.
I would develop the user interface in C# and try to put the logic in VC++ if at all it is a mandate.
You talk about Being HUMAN. I have it in my name AnsHUMAN
-
I plan to develop a new application with Visual C++ but I am wondering which library to use for the GUI design. I.e. MFC, QT.. and so forth. MFC is a native MS library and sounds nice but rumors say that it has no future. What are your thoughts? Would you start a new application with MFC? Thanks for your answers.
What is your goal? For cross platform, Qt is probably the most dominant library. For just Windows, .NET is the most dominant, though the actual UI jumps around (forms, XAML, Silverlight, etc.) I personally love C++ and MFC and write small apps in both because I'm an expert in both (and will hopefully retire soon with that being my legacy of expertise.) However, if you are starting out, unless you are specifically interested in embedded systems, driver or kernel level code, C++ is a poor choice. Based on my recent interview experiences, Java probably has more demand than any language (Android is a big part of this) with C#/.NET web services being a close second. I have found increased interest in Qt, though I'm not convinced the demand will last much more than another decade, if that. (On the flip side, iPhone apps are written in Objective-C. How long will that last? Who knows?)
