Linux.com

Feature: Reviews

KOffice 2.0 beta hints at improved capabilities

By Bruce Byfield on October 09, 2008 (4:00:00 PM)

Share    Print    Comments   

KOffice has been trailing the office application leaders for a long time. Despite years of development, it has yet to match OpenOffice.org feature for feature, although its features are complete enough that they have attracted a loyal community. Judging from the first beta, KOffice 2.0 will still not rival OpenOffice.org or other free software rivals, but it should be a major step in that direction.

KOffice 2.0 is available as source code in two tar files, one of which contains only Karbon and Krita, the two graphic programs. Alternatively, you can find packages in the Debian experimental repository, or install a Kubuntu Intrepid Ibex beta release and download packages from Launchpad. Binaries are also available for Windows and Mac OS X.

Regardless of how you obtain the beta, at most it contains only KWord, KSpread, KPresenter, KPlato, Karbon, Krita, and KChart. The new versions of Kexi, Kivio, KFormula, Kugar, and the KOffice Workspace are not available yet, even after 10 alpha releases -- a reflection, no doubt, of the complexity of the project.

In this article, I'll look at the major applications: KWord, KSpread, and KPresenter. In Part 2, I'll move on to the other four.

The first thing to notice in KOffice 2.0 is that the move toward a common interface, which has been accelerating in the last few releases, is now largely complete. Where in older versions, few interface features were common to every application, the new beta has a unified look, a spare, efficient one that's closer to that of OpenOffice.org 3.0 than anything that has gone before.

The second is that the common interface has changed dramatically in the new release. Now, the right side of each editing window is dominated by Dockers -- not a brand of pants, but a series of palettes for such features as styles, shapes, and font effects. Each Docker can be collapsed to save space, or dragged to become free-floating on the desktop. Or, if you prefer, you can dock the palettes on the left, top, or bottom side of the window, or remove the entire docking area outside the editing window. If you prefer a different set of Dockers to the defaults, you can add or subtract Dockers via the Setting menu. Overall, the result is a highly customizable workspace, although some default Dockers do not seem especially appropriate to certain applications -- for instance, the Tool Options Docker probably should not be taking up space in KSpread.

Many of the default Dockers and tools seem oriented toward graphics. For example, KOffice now includes a Docker for various patterns, a freehand draw and a separate calligraphic tool, as well as the capacity to add patterns and gradients. In the beta, at least, the selection of drawing tools is not as well-rounded as those available in OpenOffice.org, but their introduction is still a major advance for KOffice.

Another common change is the introduction of scripts -- that is, macros or extensions, if you are used to the naming conventions of other office suites. Although they do not seem to enabled in the beta, you can view some of the items in the scripts from the Tools menu. Interestingly enough, they include OpenOffice.org Uno, that office suite's scripting and extension subsystem, which suggests that compatibility with OpenOffice.org extensions will be part of the final release. It may well be that scripts will be the feature that makes KOffice fully featured at last.

The KWord text processor

As a text processor, KWord is noted for its use of frames, which allow the creation of complex layouts quickly. In previous versions, frames were emphasized by icons for their creation on the left side of the editing window, as well as a tree view of the document's structure. In the version 2.0 beta, frame controls have been de-emphasized by confining them to a menu. Since layout that requires frames is more advanced usage than most people are likely to want, this change seems appropriate.

 

However, if you are a user of styles, you may find that the default Dockers make the sloppy habit of manual formatting too easy by making the tools you need always easily available. True, styles are included among the Dockers, but far more Dockers encourage manual formatting.

Additions to the latest version of KWord include such features as file encryption (available from File -> Documentation Information) and a variety of graphical bullets in style definitions that make OpenOffice.org's selection of bullets look tired and trite.

For the most part, the KWord beta offers little that is new for the average text document. In fact, it lacks many of the features of version 1.6.3 -- particularly support for tables -- although most of those, presumably, will be in the final version. However, more than any other application in KOffice, KWord benefits from the new drawing tools and Dockers, which strengthen its desktop publishing abilities, especially for projects that will be printed immediately and not heavily revised over their lifespans.

The KSpread spreadsheet

KOffice's spreadsheet has probably undergone the greatest number of additions of any of the office suite's applications. By my count, KSpread has added more than 170 new functions since version 1.6.3, an increase of nearly 50%. Many are intended to make KSpread more compatible with Microsoft Excel and OpenOffice.org Calc.

Almost as importantly, the latest version of KSpread gains some much needed sorting and filtering capacity, strengthening the ability to manipulate lists -- one of the most basic uses of spreadsheets. In addition, KSpread gains some new formula utilities, including Validity, a handy graphical tool for naming cell ranges, and a Function Optimizer that might be described as a form of Goal Seek. A few standard spreadsheet functions, such as pivot tables or datapilots and grouping and outline, are still absent, but KSpread is shaping up to be the KOffice application that comes closest to matching rival programs feature for feature.

The KPresenter slide show program

In the first beta, KPresenter 2.0 is still rough, with many of the items in the Insert, Format, and Slide Show menus of version 1.6.3 still absent. That makes it almost impossible to assess.

However, what can be said is that KPresenter has undergone some interface changes, with a note view replacing the note pane in the editing window, and the Text menu eliminated. It also has added support for custom animation, and a presenter view that gives anyone delivering a presentation a console on their own monitor, like the Sun Presenter Console extension for OpenOffice.org. These additions are welcome, so far as they go, but what else is scheduled for KPresenter -- in particular, the important question of whether the new version will support sound, and how -- is impossible to say with this release.

Conclusion

For those who would like to see more KOffice applications among the best of free software programs, the enhancement of KSpread is encouraging. But, unfortunately, the same cannot be said of KWord and KPresenter. Both these programs have lived on potential for so many years that I, for one, have just about despaired of them ever living up to their full promise.

True, KWord, KSpread, and KPresenter all show marked improvements in the version 2.0 beta, and the common interface fits well with the KDE 4.x desktop. The changes are generally promising, not least because they have been accomplished without any noticeable loss of speed compared to earlier versions.

All the same, the release has so many features missing and suffers from so much instability that it only just qualifies as a beta. For this reason, any conclusions must be tentative. For now, it appears that, except for KSpread, the major applications, have improved, but not advanced as far as many users might hope -- but that might change before the final release.

Bruce Byfield is a computer journalist who writes regularly for Linux.com.

Share    Print    Comments   

Comments

on KOffice 2.0 beta hints at improved capabilities

Note: Comments are owned by the poster. We are not responsible for their content.

Correction

Posted by: Anonymous [ip: 62.70.27.104] on October 09, 2008 06:20 PM
Hi, thanks for giving us your insights on KOffice :)

I just want to point out that there is a little mistake in the article; it says KOffice uses Uno for scripting but thats not the case. It uses a technology called kross instead.
Would be great if you could correct the article to remove that little mistake :)

Thomas Zander, KWord maintainer.

#

KOffice 2.0 beta hints at improved capabilities

Posted by: Anonymous [ip: 96.228.149.179] on October 09, 2008 07:22 PM
Has K Office become more compatible with MS Office file formats? I know in the past this was not one of its strong points. I wish that mention of this had been included before I waste time downloading and installing K Office. Thanks for the information that you did supply though.

#

KOffice 2.0 beta hints at improved capabilities

Posted by: Benjamin Huot on October 09, 2008 08:06 PM
Back to Koffice - I last used it at version 1.5 on Suse 10. I liked the streamlined interface an the palettes and the smaller footprint compared to OpenOffice.org, but in the past Kword would hang for a while after I started using it for a little while. I also need it to handle about 500 pages of text. Can it handle this size documents? I know LaTeX works well for this size which I use, but for conversions and such I often use OpenOffice.org to make a nice OpenDocument version of it via latex2rtf as the direct route from LaTeX to OpenOffice.org via htlatex choked on one of my texts as well as preserved less structure. Go figure.
[Modified by: Benjamin Huot on October 09, 2008 08:07 PM]

#

Re: KOffice 2.0 beta hints at improved capabilities

Posted by: Anonymous [ip: 91.107.124.38] on October 11, 2008 08:44 PM
I think that's spot on, Benjamin. The main thing that has always kept me off Koffice has been the lack of stability.

#

KOffice != OpenOffice.org

Posted by: Anonymous [ip: 124.106.192.77] on October 10, 2008 02:32 AM
Bruce,

I think you made quite a presumption up there, right at the very beginning. You presume that it aims to match OO. feature for feature in the first place. I think that's a bit unfair to the KOffice developers. KOffice was never meant to copy or even match OO.o. It is not its standard. In fact, even their implementations of ODF are not exactly similar (see comments in previous KOffice news in dot.kde.org). KOffice is an office suite in its own right, with its own goals and its own design. To measure its improvements based on how closely it matches OO.o is doing it a disservice.

P.S. Of course that doesn't invalidate the rest of your observations and assessments. :)

- Jucato

#

KOffice 2.0 beta hints at improved capabilities

Posted by: Anonymous [ip: 99.241.160.220] on October 10, 2008 03:09 PM
I would have welcomed comments on the compatibility between KOffice's implementation of ODF and OO.o's implementation. I am puzzled by reports that the two applications are not entirely compatible.

I sometimes need to print, even to edit, ODF away from my own workstation --- on hosts which have only OO.o and need confidence that the printed output is consistent between the two applications.

#

Re: KOffice 2.0 beta hints at improved capabilities

Posted by: Dummy00001 on October 11, 2008 01:04 PM
I had such problems in past, but can't comment on present state.

OO.o2 wasn't always 100% ODF compliant and for some things was dumping SXW into ODT. Pretty much no other (ODF compliant) suit could read it. I ran several OO.o's ODTs through ODF verification tool ( http://wiki.services.openoffice.org/wiki/ODFValidator ) and it produced some thousands of warnings for each file.

KOffice 1.x was crashing trying to read such files. I know for sure that 2.x doesn't crash (my bug report was closed), yet, until OO.o wouldn't improve its own ODF support (I heard OO.o3 claims to be compliant) and KOffice wouldn't crash on broken files, interoperability is all but remote target.

Also I had huge fonts problems. OO.o was trying to make document M$Wind0ze compliant by using weird fonts like Arial and Verdana (which were never present on my Linux). And obviously KOffice couldn't find them when trying to open the document. Result was less than pleasing rendering of what was before quite simple document.

I did also try opening KOffice 1.x ODF files in OO.o2, what was triggering different kind of bugs in OO.o: half of first page was rendered properly, but rest of document had fonts of size 4pt or something similar.

I think it is worth for somebody with writing skills to actually test KOffice 2.x and OO.o3 for two way interoperability.

#

Re: KOffice 2.0 beta hints at improved capabilities

Posted by: Anonymous [ip: 189.13.34.64] on November 03, 2008 02:51 PM
I like this

#

KOffice 2.0 beta hints at improved capabilities

Posted by: Anonymous [ip: 85.243.48.97] on October 10, 2008 04:28 PM
I take the opportunity to congratulate the developers, for a good suite of applications. KDE Office seems to be turning into a good suite. I have to try the beta.
And than you for the article, good overview!

But i also take the opportunity to note the naming scheme. This is not bashing, i'm being honest. The names are horrible. Unfortunately, i'm like the 100000th guy saying this, but also unfortunately, the names are still horrible. They always, and i mean always, suggest me Knockoff, and Kounterfeit. If i show it to some Doze users, they think the same. They're not, so why hint it?

Names matter for something imho.

Good luck with KDE Office, i may be using it in the future :)

#

Re: KOffice 2.0 beta hints at improved capabilities

Posted by: Anonymous [ip: 85.54.176.39] on October 15, 2008 01:51 PM
Seconded! :)

I'd even siggest that being FOSS community an international, supposedly non US empire based one, names should be in Latin (which is an important part of every major modern language not only in the western world) and not anymore in English, Swedish (Krita), Spanish (Gambas, Brasero) or any other national language.
If FOSS is all about freedom let's not keep supporting cultural colonization.

Cheers.

#

MS Office file format compatibility

Posted by: Anonymous [ip: 151.188.247.104] on October 10, 2008 08:45 PM
I like KOffice's features, no doubt. One of my favourites for years has been the PDF Edit feature, very handy at times. And I like a lot that KOffice uses ODF by default now.

However, on a daily basis, I use OpenOffice.org. The reason is that I'm in a Microsoft shop. I need really good MS Office .doc, .xls, and .ppt file format compatibility, which OO.o has in spades. Once KOffice improves in this way, I'll use KOffice more. I'd really like to, it's very memory efficient due to shared libs.

#

KOffice 2.0 beta hints at improved capabilities

Posted by: Anonymous [ip: 75.155.94.20] on October 11, 2008 10:06 AM
I think this review (and part 2) completely miss the point of KOffice's emphasis to integrate discrete document types within the same document, such as creating and fully editing (rather than cutting and pasting) a spreadsheet in the midst of a vector graphics drawing, or creating and fully editing a vector graphics drawing within a spreadsheet, which it clearly does better than any open source or proprietary solution, and thus blurs the lines between the applications as standalones.

It in effect adds the features of all other components to each single component, and for people who work with multiple "programs" for single projects (such as myself ;) ) this aspect of KOffice appeals without peer.

#

This story has been archived. Comments can no longer be posted.



 
Tableless layout Validate XHTML 1.0 Strict Validate CSS Powered by Xaraya