trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: April 2012

Re: [trinity-devel] Re: Resolving the TWin/KWin Fork Issue

From: Julius Schwartzenberg <julius.schwartzenberg@...>
Date: Mon, 30 Apr 2012 18:31:12 +0200
Martin Gräßlin wrote:
> On Monday 30 April 2012 00:24:11 Julius Schwartzenberg wrote:
>> Other than activities (which doesn't seem like a large difference to me
>> for a fully separate build) are there other things I could disable? I
>> guess the webpage you linked to doesn't let all the new options from the
>> GIT version yet? Maybe there is also a list in the source tree?
> The web page lists everything currently supported to be disabled in the git 
> tree. But soon there will come more things, like how to define a different 
> name and after feature freeze I will create a branch for standalone building 
> which will add a few more build options.

Great, then I think it will be good to continue based on this branch at
this point. Having a different executable name is indeed something that
is also missing now and crucial to get a separate kwin4 for Trinity.

I guess kwin4 will not fully replace twin short term, but any work
towards making it easily available to Trinity users should enable
replacing it in the long term at least.

One thing that is not fully clear yet however. Kwin4 is not able to
integrate anymore with a Qt3 and kdelibs-v3 (Trinity) based environment
as far as I am aware. Basically the sources have been migrated to the
newer libraries, which is the reason for the current fork.
In another message in this thread however, there was a mention that
kwin4 still has references to kicker in its source. What about other
facilities like DCOP?
Basically my question would be, which advantages would kwin4 have at
this point over other window managers like Metacity or Sawfish regarding
integration with the rest of Trinity? The toolkit difference seems to be
equal to me and I would expect the integration problems to be the same
as well.

The current advantage I do see for kwin4 over the others is that its
behavior is the closest to twin, because it's the same code but evolved.
Another is that the themes are the same. I guess there are more
advantages though? It would be interesting to have a good overview of this.

Thanks,
Julius