libqt-addon in kdelibs

[Thiago Macieira]

Simon Hausmann wrote:
>Talking about the API: What are you plans wrt that? Is libqt-addon
> with its Q* classes meant to be / stay public kdelibs API?

The idea is the same as for the old libkdeqt-addon we used to have in 
the elder days: stuff we make that we think should be in Qt, but TT 
hasn't added yet.

I'm talking to TT to have them included in Qt 4. The original idea was 
to have KDE 3.2 as its testbed and have it mature into its final form 
in KDE 3.3 before it got included in Qt 4.

In any event, I've programmed using Qt-only so that it can be included. 
Hence the Q names (and my need to change the Doxyfile, but that's not 
possible using the KDE build system).

BTW, the classes are namespaced, so they won't cause binary conflicts 
with the existing Qt. Just don't include both qserversocket.h files.

The API Doxygen reference is on our servers, even if not linked from a 
webpage (http://api.kde.org/cvs-api/libqt-addon/html/). Also note that 
QServerSocket didn't get listed there -- it requires a hack into qt.tag 
to work. The Doxygen reference on my home server is Ok.

-- 
  Thiago Macieira  -  Registered Linux user #65028
   thiago (AT) macieira (DOT) info
    ICQ UIN: 1967141   PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: signature
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20040215/6374330d/attachment.sig>