I had been thinking about the Trinity/KWin relationship for quite some time and todays triaging showed me that this just does not make sense. I do understand that you want to provide a KDE 3.5 desktop experience. This is great and I am all for it. But KWin 4 is a clear continuation of KWin 3. It is not a rewrite like other parts of the desktop. It is the same application, with more features, less bugs and in general a better performance.
Hi Martin,
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?
- Nigel