Moving ThreadWeaver to kdelibs

[Thiago Macieira]

Mirko Boehm wrote:
>Hi,
>
>I was approached by different people to move ThreadWeaver to kdelibs.
> Namely by kmail, kdevelop developers and by Thiago (but I forgot what
> he wanted to use it for).

The networking classes in the KNetwork namespace -- actually, the 
name-resolver backend. I already have something quite similar to what you 
implemented in ThreadWeaver and I'd like to centralise it.

You know the story: less code duplication, smaller margin for error, etc.

>Could you give me clues where in the accepted library structure it would
> fit in?

libkdecore.

>And could someone help me to adapt it to the upcoming build system (it
> uses qmake only for now).

Uh...

>I would prefer to keep an individual library, as ThreadWeaver currently
> relies on QtCore only, which allows to use it in non-GUI applications.
> Please also refrain for now from adding dependancies to QtGui to the
> library itself, I think this should be put in some other KDE Gui
> library or another library by itself.

Currently libkdecore depends on QtGui, but that's only for the short term. 
The goal is to move everything depending on QtGui out of it so that it 
depends on QtCore only. Therefore, your class is suited for libkdecore.

In the new framework, ThreadWeaver would be a Component.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

2. Tó cennan his weorc gearu, ymbe se circolwyrde, wearð se cægbord and se 
leohtspeccabord, and þa mýs cómon lator. On þone dæg, he hine reste.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20050912/20497292/attachment.sig>