trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: April 2012

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

From: "David C. Rankin" <drankinatty@...>
Date: Fri, 20 Apr 2012 14:10:09 -0500
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/20/2012 01:00 PM, Martin Gräßlin wrote:
> this again has nothing to do with KWin. Luckily a window manager does not use 
> the column widget. Please keep that on topic. KWin has been running well on Qt 
> 4 for more than four years, please keep that in mind.
>> > 

Martin,

  I do apologize for the kwin/kde grouping. I did not recognize where the
boundary line was drawn between kwin and kde. As for the thrust of my original
response -- I agree with you, if we can avoid duplication of effort and prevent
creating inconsistencies in twin/kwin -- it makes sense. The only sticking point
there would arise if there was functionality that twin needed that kwin did not.
In that case, the only option would be to have separate patches to kwin to
provided needed twin functionality (if that is maintainable) or continue with
the fork.

  I have a practical question. If twin and kwin were to merge, how would that
impact the current GIT hosting of the code? Would the twin code be included in
the TDE GIT tree as a submodule our would the TDE git tree just receive updates
from kwin as needed?  Thoughts?

- -- 
David C. Rankin, J.D.,P.E.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+RtJEACgkQZMpuZ8CyrcgTzwCeO4JaSUIQNsgEH9LXxDBuaOv+
NPEAn25hIz8ReWGDwYb3AywtQGoH6/kt
=3pew
-----END PGP SIGNATURE-----