Thomas Zander
KDE
KOffice
Posted by Thomas Zander
 in KDE, KOffice
 on Friday, August 28, 2009 @ 17:18

Its been some months since we released KOffice2.0.0, the first official release for the new platform KOffice2.
For common and certainly for advanced office users we made clear that 2.0 is missing features for them. What then, you may ask, is 2.1 going to change for them?
Well, here is what we are working on and what has been integrated into what will become the 2.1 release in a month or two.

Tables
Releasing a word processor without tables was pretty daring, and for 2.1 we did a lot of work to correct this. As part of the GSoC project we got Elvis Stansvik working on this for the whole summer. As this is part of KWord, I was the mentor and near the end we also got help from Casper Boemann. The end result is that KWord can show a huge set of tables based documents correctly. Its important to point out that this is ongoing work; creating new table cells or modifying the shape and look of a table is currently not possible.

Change Tracking
While editing a text document you can always undo your changes and get back to the way your document looked before. But what if you want to show the actual changes made right inside the current document? Or even better, being able to see what your colleague changed in the document over the weekend. This is what change tracking offers and this has been integrated just last week and it looks like we’ll have most of the expected features available in 2.1 thanks to the work of Pierre Stirnweiss. The most exciting part is that this lays the foundations for projects like collaborative editing.

Improved image handling
This has been detailed in another post already, so I’ll keep it short. For 2.1 the images handling has been made faster and we now are much smarter with memory usage so its possible to have image-heavy documents showing just fine even on memory constrained systems and devices.

Continued improvement in OpenDocument Format (ODF) support
ODF is still a huge specification and during the 2.1 time-frame there have been various teams working on testing and improving KOffice to become both better at writing correct and full ODF as well as reading other applications ODF documents. As ODF is a way to inter-operate between different application suites so its obvious that the way to get better ODF support is to collaborate on this front with others.
KOffice has been working at the front-lines with the industry big names for some time now. A recent example is the plugfest in The Netherlands last summer and the upcoming plugfest in Italy where KOffice is well represented.
An exciting initiative is the officeshots which renders an ODF document in all available office applications and shows the output. KOffice has been working with the OpenDoc Society to provide hardware and software support and make sure KOffice interoperability can be verified by everyone.

KFormula major improvements.
The formula editing component in KOffice has seen many upgrades since the 2.0 release. This means that all KOffice applications can now display and directly edit formulas. The GSoC project by Jeremias Epperlein has seen improvements specifically in rendering the formulas much more pleasing to the eye and the editing of a formula is well integrated into KOffice and quite easy to use.

Windows
At the tagging of the beta1 all of KOffice compiled without problems on visual studio 2008 which significantly lowers the barrier to developer and end user adoption of KOffice. We are still looking for enthusiastic packagers and naturally developers on this platform to help improve the experience for end users.

MSOffice support
Still quite important for many is the ability to open MSOffice documents correctly and the major painpoints are one by one being addressed. Major things like importing text correctly, importing tables and importing images in presentations have been added for 2.1.

9 Responses to “What is happening for KOffice2.1”

» Posted by Salva
 on Friday, August 28, 2009 @ 18:28

Hi!

it seems it’s a really good job, congratulations! However, I find one thing missing in this list, and it’s whether Koffice is able to manage references (Bibtex, Mendeley, Zotero…)

Thanks

» Reply from Thomas Zander
 on Friday, August 28, 2009 @ 18:50
Thomas Zander

@Salva. The reason its missing in this list is because this list talks about what is happening for 2.1 :) If you want to know when references are going to be implemented; I’m not sure… It will happen when someone puts the effort in.
KOffice is very easy to extend, and its open source. So anyone that wants to put either the time or the money there to make it happen is able to.

» Posted by The User
 on Saturday, August 29, 2009 @ 00:00

@Salva
Plugin-creation is not too complicate, but you have to do some things:
-The real invocations of Bibtex or whatever
-Load/Save this information in the file
-Save this information in a format compatible to OOorg (save the results)
-Create a Tool to edit it
-Create some factory-classes
I think all those factory-classes take a bit too much time, but it’s okay.

» Posted by Salva
 on Saturday, August 29, 2009 @ 00:56

Hi!

I don’t know so much about how to programme kde applications (in my work I have some C++ codes but without graphical interfaces), but I love kde and I would like to use koffice at work, but somehow I would need a way to include references.
Could it be possible just to reuse code from OOorg? Maybe this would make it easier.

Thanks for your fast reply!

» Posted by Bugsbane
 on Saturday, August 29, 2009 @ 05:09

Brilliant - especially the Windows / Office support and image handling stuff. Congratulations to everyone involved.

I’d also like to point out that Karbon added what is most likely the second most used tool in all of vector graphics editing (after the line draw tool). The ability to edit any curve by dragging at any point on the curve with the curve edit tool is, for many artists this is the defining point between a vector editor that isn’t truly usable to one that’s ready for work. Many, many thanks Jan for adding this so swiftly.

I’ve never been as excited about Koffice as I am today, and the future’s looking better than ever.

Go team Koffice! \o/

» Posted by Dimble
 on Saturday, August 29, 2009 @ 09:21

delighted to hear about MSOffice support, it is important.

» Posted by werner
 on Saturday, August 29, 2009 @ 20:21

Eine Funktion die viele Leute suchen fehlt in allen Büro-Programmen, und könnte mal in KOffice eingebaut werden:

Von einem (langem) Dokument automatisch eine Index-Tabelle aller vorkommenden Worte erstellen.

Bsp.: Datei:
1 fifi
2 fofo
3 fifi

Die Tabelle wird dann:
fifi: 1,3
fofo: 2

Bei den bestehenden Funktionen muss man jedes einzutragene Wort als solches markieren. Das ist bei langen Texten (zBsp Büchern) kaum noch möglich. In vielen Anwendungsbereichen braucht man aber eine Funktion um solch einen Index der vorkommenden Worte zu erstellen.

Also: eine Menüfunktion die das macht. Maximal zu konfigurieren: Trennzeichen (default: ), und min. Anzahl der Buchstaben fuer ein Wort (default: 2)

W.Landgraf
SYS

» Posted by Haakon Meland Eriksen
 on Saturday, August 29, 2009 @ 20:39

About change tracking: We already have git, GNU Arch, Subversion, Concurrent Versions System available to us, please consider being the first free (as in freedom) software office suite to auto-detect the revision control system installed and offer to use it upon saving documents.

Yours sincerely,
Haakon Meland Eriksen

» Posted by Pavel Fric
 on Sunday, August 30, 2009 @ 10:30

Hi,
I worked on translation of KOffice into czech: missing - untranslated strings, revision for my own custom version of look of interface (almost all the modules except Kexi and KPlato). The main thing, why I see some problem with usability, is in the formating of simple text: the interpretation of fonts, look and feel of text, doesn´t seem to be the same like in other softwares (MS Office, OpenOffice, Abiword). This is the main thing for me to be able to use KWord - perfection of look of text. Could you explain to me, where is the problem, or isn´t it problem? :-)



© 2008 Nokia Corporation and/or its subsidiaries. Nokia, Qt and their respective logos are trademarks of Nokia Corporation in Finland and/or other countries worldwide.
All other trademarks are property of their respective owners.