A lot of GUI are dependant upon the compiler you are using. I prefer Borland's C++ Builder. It's as easy as Visual BASIC to drop and drag components into place but gives you a C++ standard compiler.
James P. Cottingham
----------------------------------------- To determine how long it will take to write and debug a program, take your best estimate, multiply that by two, add one, and convert to the next higher units.
If you want portability, try a toolkit such as wxWidgets(formerly wxWindows). It's a mature product, and free. If you prefer proprietary code, Qt is also nice, and portable across the major OS's (Mac, Linux/Unix, Windows).
the open version of Qt is available only for free GPL'd programs (and maybe a few other highly restrictive open licenses).
If you want to sell your product or keep the source to yourself you'll have to buy a license.
It's also very slow on most platforms...
Borland has good libraries shipping with C++ Builder (which now works on Windows, Linux and I think Mac OS/X) making it as portable as anything and more so than most.
We are using Qt for our developments, and we do not have problems with speed or efficiency. Anyway it is faster than Java/Swing. It's a lot easier to learn than MFC. The library is also well-designed, well-documented and reliable.
So I see people are struggling to decide which is best. MFC, Borland C++ or Qt.
Well, it depends on what one wants to do. If you wish to do simple apps (mostly cute interfaces) use Borland C++ Builder; it works like a charm. If you are an old fashionned guy, then use MFC, though I have no ideea why one would like to "reinvent the proverbial wheel". Most of the code one has to write is already made... probably "one" has too much time; anyway, Qt is the preferred way to do stuff. I haven't tryed it on Windows, although Opera Browser (which, from what I know, it's written in Qt) works and looks pretty cool.
In what concerns Linux (yes, I am a Linux fan) Qt _IS_THE_BEST_CHOICE. Works fast (too fast maybe ) is simple, is well docummented (I never googled the net for info) and is supported by most distros.
Cheers,
Mike
PS: Forgot about wxWidgets. Haven't used it. But the concept tells it all: does almost the same thing as Kylix or Qt, except it's totally free and (probably) adds some features. Sorry... but no. I belive the next step in this direction is to make a toolkit that makes apps look EXACTLY THE SAME on all major OSes. Qt almost does it... but not quite
globos: i believe jwenting meant "slow" in reference to compile time. Qt applications seem to take a while to compile (for me at least) but they run as well as most any other program.
As to Swing being slow, that's sadly a well established urban legend.
Swing USED to be slow, but the current implementations are quite fast.
Of course a poorly programmed Swing application will always be slow, but so will a poorly programmed application in any language/toolkit.
Mainly my experience with Qt has been only with poorly built applications but in my experience it's slower at runtime than for example OWL and MFC.
When using BC++, OWL is a logical choice. Easy to use (relatively) and good performance.
If using BCB, VCL or CLX become obvious (and good) choices.
I have not said Swing is slow, I have said Qt is faster than Swing
Maybe Qt is slower than MFC or OWL, that sounds normal, that's a little price to pay for portabilty of the source code. Qt provides better API than MFC, more high-level, so it may leads to slow down developped apps.
I have not said Swing is slow, I have said Qt is faster than Swing
Maybe Qt is slower than MFC or OWL, that sounds normal, that's a little price to pay for portabilty of the source code. Qt provides better API than MFC, more high-level, so it may leads to slow down developped apps.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.