What do you use with C++? Do you use simplified low-performance wrappers like MFC, Qt, ATL, GTK+ etc or pure WinAPI?
What do you use with C++? Do you use simplified low-performance wrappers like MFC, Qt, ATL, GTK+ etc or pure WinAPI?
MFC all the time. And only WinAPI when it makes sense.
After all, I have schedules and deadlines to obey to. Try and do that with WinAPI.
(Of course this only applies to my job as a Visual Basic software engineer. But MFC and the WinAPI are really not that different between VB and C++)
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
Win32. I'm on the verge of learning MFC but other stuff is taking priority right now, like remaining sane.
Seriously I know it's not *that* bad and seriously, I haven't found the time
Good class architecture is not like a Swiss Army Knife; it should be more like a well balanced throwing knife.
- Mike McShaffry
Of course it's not bad. The strangest thing about it is that most of people say it's easier, but to me it looks way more complicated than pure WinAPI.
Maybe because you didn't study it well enough yet
Trust me, it isn't more complicated. Why do you think they developed it?
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
I don't know why they develop it...
But Win32 API was clear from the start: simple variables, simple functions.
I can make Win32 API applications quickly, too. Usually I copy code pieces from my previous application.
I've heard someone saying, that Win32 API is too difficult... if that's the basic problem of Win32 then I have no problem using it.
No. It's not because it's difficult.
You have to ask yourself the question why companies worldwide favor MFC for their projects and not Windows API. And when you research it well enough (or have the experience yourself in the actual industry as a software developer/engineer/etc), you will realize that... tada! It's quicker to develop in MFC than it is in straight windows API.
And... that's all that matters. MFC may be ugly here and there, but it is a fairly more elegant approach to windows programming when compared to the windows API. Software development is about business decisions, schedules and deadlines. Failing to realize this and being pedantic around your choices is a sure step on your way to be sacked.
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
I will use MFC when I have deadlines and I can't finish the thing using Win32. But now, I don't work for any company, I just learn and test things (my productivity is about 2-3 simple programs a week ).
Wow, I wonder what Salem is using...
>> Wow, I wonder what Salem is using...
He probably made his own. I know I would if I had to write a warning against being asked for 1:1 help!!
Last edited by twomers; 09-09-2006 at 09:58 AM.
I use the SDL and my custom windowing library. :P
.NET is better than MFC.
Learn C++ (C++ Books, C Books, FAQ, Forum Search)
Code painter latest version on sourceforge DOWNLOAD NOW!
Download FSB Data Integrity Tester.
Siavosh K C
Some of us (quite a large number) write software which isn't PC bound, nor even has a GUI.
So questions like "which C++ GUI for win32" offer little meaning to us.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
I am surprised, Salem didn't change the title.Some of us (quite a large number) write software which isn't PC bound, nor even has a GUI.
So questions like "which C++ GUI for win32" offer little meaning to us.
Learn C++ (C++ Books, C Books, FAQ, Forum Search)
Code painter latest version on sourceforge DOWNLOAD NOW!
Download FSB Data Integrity Tester.
Siavosh K C
It depends almost entirely on the situation at hand. I prefer the Win32 API to the MFC, the API feels more natural to me. If I was writing something intricate like a GUI for a compiler with stuff like syntax highlighting, intellisense, etc, I'd definately consider using the MFC instead or just go right to .NET. If I was writing an application that would both be Open source and cross platform, I'd probably go right for Qt (this is coming straight from someone who hates GTK, mind you,) although the license for it bugs me.
operating systems: mac os 10.6, debian 5.0, windows 7
editor: back to emacs because it's more awesomer!!
version control: git
website: http://0xff.ath.cx/~as/