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

Martin Gräßlin wrote: 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