Linked by Eugenia Loli on Sat 15th Dec 2007 06:17 UTC
Thread beginning with comment 291034
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links




Member since:
2007-12-15
KOffice definitely is not better than OO.o, but:
1. It is developed by a very small amount of developers. Taken that into account, it is amazing what it looks like (and with KOffice 2.0 around the corner - I guess it will be available at the end of Q1 2008, this will be even more obvious).
2. It has the great advantage of not carrying the legacy of old code. OO.o is a horror to comprehend. KOffice is quite easy to understand, so for new developers it is much less a hassle to become involved.
3. It leverages the desktop underneath, so it is tightly integrated to the desktop. The experience is incomparable.
Again, as I wrote in another post here, just imagine a fraction of fundings that goes into OO.o going into KOffice. Like, for example, into doc filter and another "corporate" stuff.