Qt4 support

[Jens Dagerbo]

On 10/21/05, Nicolas.Castagne at imag.fr <Nicolas.Castagne at imag.fr> wrote:

[snip]

> 2/ the effects of project option / C++ / Qt / use QT4 are not really
> clear... On my config, the qmake 3 and uic 3 were still used for
> compiling, even when selecting QT4 and entering the correct path to QT4...


It's far from obvious, I agree. I had to read the code to figure it out. As
far as I can tell, it ONLY affects the automated guessing of base class
declaration header file when using the Class Wizard to derive a Qt class.

class Foo : public QLabel
when set to Qt3 this will produce #include <qlabel.h> in the resulting
foo.hheader file
and when set to Qt4, #include <QLabel>

It has NOTHING to do with the build settings. This does make some sense when
you realize it's implemented in the cpp language plugin (independent of the
build system) and is in the "c++ specific" settings, not the build settings.

Some tooltips and a renaming of the "Qt" tab to "Class Wizard" would
probably help clear a bit of the confusion.


Btw, apart from this marginally useful feature, what other "Qt4
improvements" do we have in 3.3?

3/ It seems that QT3 designer is not compatible with QT3 uic.
> Consequently, the fact that .ui files in kdevelop open QT3 designer is a
> problem. If it is not possible to incorporate QT4 designer as a plug in to
> Kdevelop, it would be nice to use QT4 designer when using the
> OpenWith/QTDesigner in the contextual menu of .ui files.


The internal designer is, as you say, based on Qt3 designer and can as such
not handle Qt4 ui files. I doubt it's a trivial matter to have KDevelop
recognize the different file versions and only allow launching the internal
version if it is a Qt3 file.

I think it's better to configure KDevelop to launch designer externally.
Without testing it, I'd assume KDevelop still launches whatever external
handler of .ui files you have registered with .ui files. If you associate
the Qt4 designer with .ui files, it will be used for opening them. I have no
idea if the Qt4 designer is backwards complatible with Qt3 .ui files though.



[snip]

// jens
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20051021/fb911903/attachment.html>