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

List:       kde-devel
Subject:    Re: Porting Qt applications
From:       Gav Wood <gav () kde ! org>
Date:       2003-08-28 13:37:02
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 28 Aug 2003 2:12 pm, Bernd Brandstetter wrote:
> Hi,
>
> I have written a Qt-based application which also runs fine on KDE.
> However, I'm thinking about porting it to KDE, i.e. using the KDE instead
> of the Qt API where possible/necessary to improve its integration in the
> desktop.

good idea.

> My questions:
> - Is there some kind of porting guide or checklist describing what to take
> care of? (Like for instance does it make sense to replace a QPushButton by
> a KPushButton? What's the benefit from it?)

not too sure about push buttons, but generally kde widgets should be used over 
qt widgets, since they may provide more features and will integrate better 
with the environment (iirc kiconview uses the double-click preferences to 
generate the activate signal).

> - If the application doesn't use KDE-specific interfaces like KParts and
> dcop, is it worth the effort at all?

i would say yes, but i'm quite a purist and like the warm feeling that the 
application is truely a part of the kde experience. actual "physcial" 
benefits are stuff like better file requesters and passive popups in kde.

gav
- -- 
Gav Wood <gav@kde.org>

codito ergo non satis bibivi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)

iD8DBQE/TgWB7nE5x1pIEBQRAryRAKC3vVjU3tXaP8bgEGzGyVEWQ445LACfccW3
RQAT6rFDbl3FF2p5uy2S3rM=
=5LRO
-----END PGP SIGNATURE-----

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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