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

[techsgin]

Hi Tom

 

Thank you very much for taking the time to response our message.

P.S *still relevant even if you do work for Qt.:-)

 

Regards

TechSgin

 

 

  _____  

From: qt-interest-bounces at trolltech.com
[mailto:qt-interest-bounces at trolltech.com] On Behalf Of Tom Panning
Sent: Wednesday, December 17, 2008 18:14 PM
To: qt-interest at trolltech.com
Subject: Re: [Qt-interest] (URGENT) Does QT3 Support module is
anintermediate step or a real solution the can go into aproduction release ?

 

The project has shipped and is shipping releases that use the Qt3Support
library relatively heavily. As we add new code we avoid using Qt3Support
classes and functionality, and if we do heavy modifications to existing
classes we attempt to remove Qt3 references where possible.

I don't work for Trolltech, but my understanding is that Qt3Support is
production-ready code for all of Qt 4. But when Trolltech decides it's time
for Qt 5, there won't be a Qt3Support. So, as the docs say, don't add new
code using Qt3Support, but it's better to use Qt 4 with Qt3Support than to
just stay with Qt 3.

Tom

On Mon, Dec 15, 2008 at 8:12 AM, techsgin <techsgin at gmail.com> wrote:

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

 

 

 

 


_______________________________________________
Qt-interest mailing list
Qt-interest at trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-interest

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20081217/7f232c96/attachment.html