trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: April 2012

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

From: "Mag. Dr. Nikolaus Klepp" <office@...>
Date: Sun, 29 Apr 2012 17:22:03 +0200
> > it does.
> > not to all recent specs, but enough for my use cases.
> > I can read my files with OO/LO or even MSoffice w.o. problems.
>
> have fun the first time you get an dotx :-)

I do, and there's no office package that can handle docx the "correct" way 
despite M$-Office.

I don't get the point of this prolonged discussion: let's state somebody would 
really want to trade twin for something else, why should he use kwin? What's 
the benefit? As I see it, there's simply no point to prefer kwin to e.g. fvwm 
or openbox. 

By the way, I still have the infamouse problem of slugish qt4 experience.

Nik