[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: KDE & QT4
From:       David Boosalis <david () commandscape ! com>
Date:       2005-11-15 18:44:44
Message-ID: 200511151145.17029.david () commandscape ! com
[Download RAW message or body]

I would use QT3, but as you code try to minimize how QT3-QT4 differences.  For 
instance  in QWidget

QT3 QWidget(QWidget *parent, const char * name = 0, WFlags f = 0 ) ;
QT4 QWidget(QWidget *parent,WFlags f = 0 ) ;

So for every widget you create which inherrits from QWidget directly or 
indirectly(All QT widgets) Do not have the name field.

Also if you use database calls, do not use and QCursor, as I am pretty sure 
they went away in QT4.
 
Stay away for QCanvas

Pray that QT4.1 makes QT4 usable.


On Tuesday 15 November 2005 07:27, Andreas Pakulat wrote:
> On 15.11.05 15:57:48, Bram Biesbrouck wrote:
> > I'm currently developing a new KDE application and I wonder if any of you
> > guys could spill out your opinion on the best approach to do it. Should I
> > stick with QT3 and then move to QT4 when KDE does?
>
> I guess you also mean here that you use KDE3.
>
> > Or should I develop entirely in QT4 and then tweak the necessary
> > widgets when KDE moves to QT4? Or maybe, I should work on the latest
> > SVN that is already ported to QT4?
>
> First: As far as I know kdelibs in SVN is changing very heavily ATM
> AFAIK, so I don't think that you can build a new app on top of it at the
> moment.
>
> Second: If you need any KDE widgets this of course means to stick to
> KDE3+Qt3, if not it's your choice. If you're familiar with Qt3 it might
> be easier to start with that...
>
> Also note that Qt4.0.1 is still somewhat buggy and slow with painting,
> Qt4.1 should be an improvement here, but it's not out yet. Qt3 is much
> more stable and paints much faster.
>
> Andreas

-- 
David Boosalis
Commandscape, Inc.
101 Redwood Shores Parkway
650-598-1300 x 160
david@commandscape.com
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]