30 Apr
2012
30 Apr
'12
3:53 p.m.
On Monday 30 April 2012 04:47:30 jamesg(a)dimensionality.com wrote:
At the risk of a repeated question (I've been
unable to keep up with this
thread):
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),
KWin does not optimize for the latest
hardware. It does so for a certain
degree as a compositor but you can just use KWin as a non-compositing window
manager like TWin :-)
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?
sorry I don't think I get
the question correctly.
Are you asking whether there is any code which code be moved from KWin to
TWin? If yes, no, I want to resolve the fork and not create a Frankenstein.
Cheers
Martin