[Qt-interest] (URGENT) Does QT3 Support module is an intermediate step or a real solution the can go into a production release ?

[Malyushytsky, Alex]

QT3Support module is officially supported.
And if it produces results which satisfy you and your customers, you don't have to replace already working code.
It could not satisfy me in my main project, since I've had just a few dialogs where I could use QT3Support classes to simplify porting to Qt4 and most of the widgets were so customized that wre-riting them in Qt4 required about the same efforts as making ported using Qt3Support code work.
At the same time we left QT3Support module in the opengl based library developed by my co-worker and  used in my main project.
I don't think it would make any sence to spend extra tiime to remove QT3Support module from that project.

Alex


________________________________
From: qt-interest-bounces at trolltech.com [mailto:qt-interest-bounces at trolltech.com] On Behalf Of techsgin
Sent: Monday, December 15, 2008 5:12 AM
To: qt-interest at trolltech.com
Subject: [Qt-interest] (URGENT) Does QT3 Support module is an intermediate step or a real solution the can go into a production release ?

Hi All, And many thanks in advance :)

Does QT3 Support module is an intermediate step or a real solution that can go into a production release?
*In other words is it a gimmick and we must complete the port to a pure QT4 solution to go live?

>From looking at QT source code, it looks like that the "Q3Support" layer is a complete rewriting of the old interface.
For example Q3MainWindow inherits from QWIdget and not from the old class or from the QT4 QMainWindow.
This usually means overhead, stability issues, performance issues and lots of headaches.

We really got scared after reading this quote " ... This class is part of the Qt 3 support library. It is provided to keep old source code working. We strongly advise against using it in new code ... ",. :(

We will appreciate anyone's experience is such a dilemma.

*Please note that we have read every "Qt Assistant" possible document in regard, and evaluated the relevant paths.
What are trying to do is to roughly estimate a schedule for feature a release.

Some extra information about the project:
* Huge and includes many sub projects.
* The project heavily depends on inheritance of QT objects. (All of them not just QWidget, this is an infrastructure layer we made)
* The project extensively relays on the following:
MainWindow,
Docking,
Canvas,
Custom Drawing,
Custom Widgets,
Custom Plugins,
List Views,
Actions,
Menu,
Toolbars.


Many Thanks
TechSgin






---------------------------------------------------------------------------------------------------
Weidlinger Associates, Inc. made the following annotations.

"This message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any disclosure, copying, use, or distribution of the information included in this message and any attachments is prohibited. If you have received this communication in error, please notify us by reply e-mail and immediately and permanently delete this message and any attachments. Thank you."

"Please consider our environment before printing this email."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20081215/e3d22696/attachment.html