trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: December 2011

Re: [trinity-devel] Suggestion to drop [t|k]win from Trinity and replace it by KWin4

From: Julius Schwartzenberg <julius.schwartzenberg@...>
Date: Sun, 11 Dec 2011 12:17:29 +0100
Martin Gräßlin wrote:
> On Saturday 10 December 2011 12:56:07 Nigel Stewart wrote:
>> What you're proposing makes sense, on the face of it.  And I ask these
>> question not as a troll or flame - and not from the perspective of really
>> knowing what the KWin component is responsible for:
>>
>> Is the binary size and performance (desktop latency) going to be
>> comparable?
>>
>> Does it drag in other KDE 4 dependencies?
> Obviously it depends on kdelibs and kde-runtime like any KDE application. The 
> dependencies will of course be better once frameworks 5 are released.
> 
> Considering the impact on a running environment I would say that all depends 
> whether your users are using any KDE 4 applications or none. I would be 
> surprised if your users would use no KDE 4 applications. So I think it is 
> negligible.

Some system on which I run TDE are very memory constrained. They have
only 128MB maybe 256MB of RAM. On such systems I do not tend to have any
KDE 4 applications installed.

It's definitely true that window managers are very difficult to
maintain. I know that some tests in Wine's test suite were failing on
kwin in Trinity because of bugs that had only been fixed in kwin for KDE
4. I wonder how strong the newer kwin series depend on KDE 4 and whether
it could be made to compile against Trinity as well.

In any case good integration between KDE 4 and Trinity components so
they can be mixed already seems good at least for high end systems.

Julius