27 Apr
2012
27 Apr
'12
6:26 p.m.
On 04/27/2012 12:13 PM, Calvin Morrison wrote:
I mean if we started using kwin, we would definitely
have influence upon it
because we would be the users. Reporting bugs requesting features. I am not sure
what else you mean by "influence". KWin4 does everything TWin does.
Let's keep it friendly and to the point.
Calvin
Both Andy's and Calvin's points are well taken,
The 'influence' issue is actually a 'kwin responsiveness' issue. If
there are
specific needs or bugs associated with TDE users of kwin, then regardless of how
many patches or bug reports are filed, if they are ignored and not implemented
in kwin4, then Andy is correct -- there is no influence. At this point, that is
a pure hypothetical. I personally don't see it being a problem with kwin as it
was with KDE4. That was the straw that finally broke the camel's back for me
with kde4 (as a global collection of apps). I authored over 200+ bug reports to
help kde4 become usable in the 4.0.4 - 4.3.X time frame and 4 years later most
are still unresolved or closed WON'T FIX.
That is both an influence and responsiveness issue. The desktop simply failed
to meet the needs of the user in my case and it was abandoned. With twin, we
have an excellent WM that is very responsive to this projects needs. If kwin can
do the same, there is no reason not to see what it can provide. Equally true is
that there is no need to abandon twin to do this. If somebody has the know how
to build an install around kwin and test, then we can get an idea of where the
shortcomings regarding TDE needs are and what can be done to address them. Until
then, it is always good to think through the what if's of any situation, but as
for whether and how well kwin can be used as a replacement for twin to allow a
merge -- until it's done, it's all just speculation...
--
David C. Rankin, J.D.,P.E.