qt versus vb6

[litlewiki]

iam planning to do develop an application using either vb6 or qt...havent decided on which to do really..
could anybody throw some light on

1) which is preferable on the whole
2) in realtion to databases..

looking more abt the pros n cons abt using qt or vb6 really...

opinions puhlzzz

[penagate]

What is qt?

[litlewiki]

trolltech.com/qt

[penagate]

Looks interesting, I'll investigate. Thanks.

Obviously, I can throw no light on the situation however

[iPrank]

I programmed in QT on Linux long time ago, just for testing.
IMO, it is just an advanced C++ form designer. But then again, I was using the free version. (QT Designer on KDE)

If you want to use QT just for platform 'independence', then you may also want to try , .NET on Mono or RealBasic.

[Kasracer]

Remember, Qt isn't 100% native on Windows. It emulates some of the graphics.

It really depends on what you want to do. If you want to develop a high performance application that's cross-platform, then go with qt or wxWidgets (I'd highly recommend over qt as it provides 100% native GUIs on any OS) and C++. If you want something that's easy to use and is windows only, go with VB6.

[iPrank]

IMO, until now, Java is the best choice for 'serious' cross-platform programming.

[Kasracer]

IMO, until now, Java is the best choice for 'serious' cross-platform programming.

What? Java!?

Java is a slow and horrible language that has no standards behind it.

With C++'s wxWidgets, you can create applications with rich GUIs with networking features and other usually platform dependant features, quickly. All all you have to do to make it run on any platform is to compile it for that platform.

Yeah yeah I know you don't have to keep recompiling Java for each platform. But you have to have the Java Runtime Environment to do this. You could easily install Mono on OS X and Linux and your executables compiled in Windows that targets the .Net framework will work just by double clicking on them in OS X or Linux. .Net has now reached Java's capabilities in easy of use on other platforms (thanks to open-source, of course) and it's better than Java and provides native GUIs compared to Java's horrible UI.

Java's language also lacks very key things in programming languages like Destructors, templates (.Net has generics, though they are very limited compared to C++'s templates), default arguements, and even operator overloading (.Net doesn't have this as well, which is disappointing).

You still have more choices than wxWidgets and .Net for cross-platform programming as well. There is qt and GTK2. Heck, you could even roll your own GUI Wrapper. It's very simple. I made a simple one in C++ years ago so I could create 1 set of code and it would compile fine on Linux and Windows and create a Window.

[NoteMe]

Remember, Qt isn't 100% native on Windows. It emulates some of the graphics.

Errrrrrrrrrrrrrrrrrrrrrrrrr


QT is not native under any platform. You have 3 different types of platfor independent graphics libraries.

QT is a GUI emulation toolkit. A so called GUI emulation toolkit don't use any native-toolkit calls at all. Instead they use the drawing or primitives of the respective platform. Each widget is drawn inside the emulating toolkit.


Then again you have an other form of the libraries. They are API Emulators. They emulate the API of one system on all other systems. These toolkits include products such as MainWin, witch provide the Win32 API on Unix systems. So you need a API emulator on other platforms to make it run. This way you can get a MFC layer on top of a Win32 layer, on top of a Motif layer on top of a Xt layer, on top of a Xlib layer.......you know what I mean...not a great idea...


And then again, you have the 3rd opertunity. wxWindows is using this one. It is API layered. This means that they provide their own API on top of the native API. The wxWindows methods map to Win32 API calls on Windows and to either motif or Xt API calls to Unix.



Then again, you have also QT# which is QT ported for use with .NET, so you don't have to use Windows.Forms. In my opinion QT is better then Windows.Forms specialy when it comes to event handling, where the way slots and signals are handled is just perfect for any application that becomes over a certain size.


Then again. Doing the whole thing in VB is probably much easier..


-ØØ -

[litlewiki]

thanks everyone for the quick response.i was actually planning to devlop an applic. ,something like a day planner.whicj is cross platform compatible and i will defintely go for qt.

[NoteMe]

Ohhh....and just to add to that...QT is Norwegian... Woohooo...Go Norway...