Linked by Thom Holwerda on Sat 23rd Dec 2006 00:48 UTC, submitted by dumbkiwi
KDE This is a response to the article yesterday on the progress of GNOME and KDE. Aaron Seigo, a lead KDE developer, sets out the current state of progress with KDE 4, pointing out that KDE 4 is on track for a release in mid 2007. "Thom points to a quote from me that our goal is to have a 4.0 ready sometime in the first half of next year. That gives us until sometime in June and I'm still thinking we can make it."
E-mail Print r 37   87 Comment(s)
Thread beginning with comment 195623
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Looking forward to KDE4
by elsewhere on Sat 23rd Dec 2006 08:04 UTC in reply to "RE[4]: Looking forward to KDE4"
elsewhere
Member since:
2005-07-13

"KOffice really doesn't measure up to OO.Org at this point. "

Sure it does. The majority of users will never need 90% of the features in OOo and thus KOffice will do all they need.
The only thing OOo have over KOffice is, imho, that OOo handles MS Office formats better.


Unfortunately handling MS Office formats is probably what 90% of the users need. I know I do.

I like KOffice. It's small, light, fast, integrates well into KDE, and does some cool stuff that OOo or MS Office do not (ie. editing PDFs).

But until I can interoperate with powerpoint and excel files, I simply can't use it for my day-to-day no matter how much I'd like too. And I do want to, because it's a pretty wicked package for what it does.

Hell, I'd be happy if I could interchange files with OOo2 using OpenDoc, but I can't even do that reliably.

KOffice is great as a standalone office suite, but we don't live in a standalone world. It sucks being tied to the MS-Office format, but that's a sad reality, at least in the corporate world. I have high hopes that KOffice 2.0 will improve in this area.

Reply Parent Score: 5

RE[6]: Looking forward to KDE4
by MechR on Sat 23rd Dec 2006 09:14 in reply to "RE[5]: Looking forward to KDE4"
MechR Member since:
2006-01-11

Depending on just how open Microsoft's new Office Open XML formats really are, compatibility with Office should be less difficult in the future.

Reply Parent Score: 2

boudewijn Member since:
2006-03-05

The MS OpenXML format is open -- but it is full of problems. Like codifying twenty-year old Excel bugs (did you know Excel still uses the Julian calendar, as obsoleted by Pope Gregory?), things like the -- copyrighted! -- border graphics for Word (all two hundred of them). People inside Microsoft and Adobe have computed that it will take about 50 man years to implement support for the OpenXML wordprocessor subformat _alone_. Basically, from lock-in through secrecy we've gone to lock-in through overload.

Simply put: writing import/export filters for MS Office file formats is not something that's doable for volunteer hackers. The formats are designed to make that hard. If we had a bag of money we'd probably use it to out-source the development of GPL, library based filters, but we haven't got a bag of money.

For KOffice 2.0, better MS file format is not a goal. If you get an MS Word document that KWord's quite adequate import filter (it's better than the one Pages has...) cannot handle, convert it to ODF with OpenOffice, then work in KWord. We believe that KWord will be so much more fun and pleasant to use, that that'll be acceptable to many people.

We cannot be all things to all people, and we prefer to do one thing good: make a suite of application that are fun to use, that help people create, put their thoughts on paper and organize their business. There are many cases (and many current users) who do exactly that. We are glad that there's OpenOffice for when better MS file format compatibility is needed.

(That said, one of the main problems with the old MS Word importer isn't actually with the importer, which can handle anything but a particular kind of graphics, but the KWord table and layout code. Now that code is going to be completely rewritten and the result may well be that the importer suddenly starts working a lot better.)

Boudewijn Rempt, Krita maintainer

Reply Parent Score: 5