--===============1818897945==
Content-Type: multipart/signed;
  boundary="nextPart50293254.0GKFOZhh8e";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart50293254.0GKFOZhh8e
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Saturday 26 August 2006 18:47, Jerry Blanco wrote:

> So, the questions:
> a) Is it even possible to write a KDE application without using KDE
> classes? Is it advisable? (probably not, right?) Is it a good idea at all?

It's not possible to write a KDE application without using KDE classes, but=
=20
you can of course restrict yourself to Qt if you want. Then you don't have =
a=20
fullfledged KDE application, but at least a Qt application running reasonab=
ly=20
well under KDE (or any other desktop enviroment). That can make sense if yo=
u=20
want to support other platforms like OSX or Windows and don't want to wait=
=20
for KDE4 where these platforms are supposed to be supported. On the other=20
hand, it won't integrate so smoothly into the desktop like a KDE applicatio=
n=20
would.=20
If you want to keep it flexible, you can separate backend and frontend and=
=20
make the backend use only Qt (or even STL only). Then you can provide=20
different frontends if necessary.

> b) If you want to use a hybrid approach, how do you decide if you're using
> a KDE or QT class in a specific instance? For example, how do you decide
> between QApplication and KApplication or KPushButton and QPushButton? Are
> they 100% compatible, in general? Does it matter if I use the K or Q clas=
s?

In most (all?) cases, the KFoo class extends the QFoo class. Usually it add=
s=20
functionality needed in KDE or make it respect special KDE settings. So if=
=20
you decide to write a KDE application, don't do it half-assed and use the K=
DE=20
classes where available.
The KDE apidocs usually contain a little inheritance diagram where you can =
see=20
the relation between Qt and KDE applications.
They are compatible like class<-subclasses usually are: If you have a=20
KLineEdit extending QLineEdit, you can pass it everywhere where a QLineEdit=
=20
is expected. The other way round that of course doesn't work.

=46rank

--nextPart50293254.0GKFOZhh8e
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQBE8IWuFZrnbFOwfvQRAtIgAKCfUIbGIyt1b3omw7UoAax/S/AibgCgqeGG
x6sMAaRljUj8h9rJSOicy70=
=qmHA
-----END PGP SIGNATURE-----

--nextPart50293254.0GKFOZhh8e--

--===============1818897945==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1818897945==--