Message: previous - next
Month: April 2012

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

From: jamesg@...
Date: Mon, 30 Apr 2012 04:47:30 -0700
At the risk of a repeated question (I've been unable to keep up with this

Are there any components of TWin and KWin4 that do not directly interact
with graphical libraries, compositing, and the like, that are still
interchangeable or close to interchangeable with each other and their root
ancestor of KWin3?

My understanding is that a fork is probably necessary given certian
mutually exclusive objectives (ie Qt3 and legacy support versus
optimization for the latest hardware), but is there a portion of code
shared between the two that is basically not part of that fork that we
might be able to separate out, possibly as a library?

James Gholston