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

List:       kde-devel
Subject:    Re: Ark: Is there a need for ThreadWeaver at all?
From:       "Mathias Brito" <mathiasbrito () gmail ! com>
Date:       2008-08-02 6:19:29
Message-ID: a78b1c920808012319m62488deag2f7eaf8b5a0b58ee () mail ! gmail ! com
[Download RAW message or body]

:P woolll god my english is very bad :D but i'm learning a lot! :D
keep on the nice thread... :D cheers, hugs, and all that nice things
to all...

Mathias Brito (from brazil) :-P

2008/8/2 Harald Hvaal <haraldhv@stud.ntnu.no>:
> Aaron J. Seigo wrote:
>> is the KJob threaded? KJob doesn't do threading on its own, that's up to the
>> application... and probably why ark is written as it is. by getting rid of the
>> ThreadWeaver code, i'll bet you end up with the UI blocked by the
>> decompression process.
>>
> You're quite right there, I had a good look at the KJob and the code and
> it looks like that was indeed the reason. Not much to do about it then,
> although it's a little ugly how much code is actually needed to have
> threaded KJobs. Is there really no KThreadedJob or such available
> somewhere? Would make the code a lot easier to maintain.
>
> Harald
>
>>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
>
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]