LWN.net Logo

Looking forward to OpenOffice.org 2.0

January 5, 2005

This article was contributed by Joe 'Zonker' Brockmeier.

As the OpenOffice.org development team closes in on the 2.0 release, we thought we'd take a look at the suite and see how the 2.0 version is shaping up. Since OpenOffice.org 2.0 is still in development, it's to be expected that some features do not work or work poorly, and that its stability isn't at a level appropriate for a finished application. The 1.9.65 build of OpenOffice.org certainly lives up to that expectation, and should only be deployed for testing purposes.

We installed OpenOffice.org 1.9.65 from the snapshot builds page on a SUSE 9.2 system. Unlike previous versions of OpenOffice.org, version 1.9.x is being distributed in "native" installer format for various systems. The Linux build is available as an RPM rather than the old OpenOffice.org setup application.

One of the goals for the 2.0 release of OpenOffice.org is for the application to start faster than previous releases. At this point in development, the startup for OpenOffice 1.9.65 is not noticeably faster than 1.1.3, however.

Let's start with the word-processing application, Writer. The sad fact is that OpenOffice.org could be the best word processor ever invented -- but if it fails to import Microsoft Word documents well, it will have a tough time in the general market. This is also true of other OpenOffice.org applications, so we spent a good deal of time testing Office compatibility.

To test out the Word and other Microsoft document import features, this reporter searched for Microsoft Office documents on Google using the "filetype" search feature. Writer is still better at importing Microsoft Word documents than AbiWord, and 1.9.65 does a slightly better job of importing Microsoft Office files than 1.1.3. There still seem to be a few glitches. One Word document, for example, looked almost perfect, with the exception of a bulleted list presented outside the page borders.

The interface for Writer has changed very little, so users who are familiar with Writer already will be able to jump right in to the next version. There are a number of noteworthy new features in Writer aside from its Microsoft Word compatibility. This version of Writer allows an author to count words in a selection, in addition to counting words in the entire document. Nested table support has also improved in this version, which will also help with importing complex Microsoft Word documents. [OOo Impress screenshot]

The Impress interface has changed quite a bit, with floating toolbars for formatting and a tabbed interface to switch between views of the document. This reporter likes the new interface a little more, but the transitions between views are a bit jarring. The "slide sorter" view is particularly nice if one needs to re-arrange a presentation quickly.

Calc looks and feels the same as its predecessor. It has undergone a few improvements under the hood, however. In particular, Calc's limitation of 32,000 rows has been removed. Calc can now handle sheets with up to 65,536 rows, which is the same as Microsoft Excel. We tested this by importing a CSV document with 59,621 rows. Calc had no problem importing this document or saving it as a native OpenOffice.org file.

Calc is a bit better at importing Excel files with odd text formatting than Gnumeric, but Gnumeric does still seem to have the edge in supported functions. Calc fails several tests in Gnumeric's testing files which test for Excel compatibility.

One of the big additions to OpenOffice.org 2.0 is a database application like Microsoft Access. The OO.org Base application is, or should be, a nice addition to the OpenOffice.org suite when it's complete. Unfortunately, Base isn't very stable at the moment, and testing usually resulted in a complete crash in a short time. The Table Wizard is very user-friendly, but each time this reporter tried to create a database using the Wizard, OpenOffice.org would crash at the final step.

Unfortunately, the entire suite is only as stable as its least-stable component. When Base crashed, it brought down the entire suite in one fell swoop. This is a bit of a design flaw, as a user with Writer, Calc and Base open will have all applications crash simultaneously. This did give us a chance to work with the document recovery wizard. At startup, OpenOffice.org would try to recover all documents open at the time of the crash. OpenOffice.org's recovery feature was fairly dependable, but this reporter is looking forward to using it a little less often.

There are also a number of features that can be found throughout the OpenOffice.org suite rather than any specific application. The native file formats have changed to the OASIS Open Document Format for Office Applications. OpenOffice.org applications still support the older format, but new files are saved in the new format by default unless the user changes default file format preferences. Users have a great deal of flexibility in this area, including the ability to save in Microsoft Office formats if they prefer.

OpenOffice.org 2.0 also has a document conversion wizard that allows the user to convert older OpenOffice.org and Microsoft Office documents into the new OpenOffice.org document formats. Rather than forcing the user to convert documents one at a time, the wizard allows a user to convert all documents in a directory at once. This feature isn't quite error-free just yet.

We were also interested in OpenOffice.org 2.0's digital signatures feature. Apparently, OpenOffice.org will allow the user to sign or verify macros and documents in the new format. Unfortunately, this feature didn't seem to be working in the 1.9.65 build.

From a test of the 1.9.65 build, it's pretty clear that the OpenOffice.org project has a way to go before it's finished. However, this release does provide a pretty good overview of what to expect, and it does look like 2.0 will be a formidable suite when finished.

For LWN readers who wish to participate in testing, or just see what else is on the way, a feature guide to 2.0 is available. According to the roadmap, the OpenOffice.org project should be releasing a 2.0 beta some time this month, with a final release tentatively planned for March of this year.


(Log in to post comments)

Looking forward to OpenOffice.org 2.0

Posted Jan 6, 2005 5:06 UTC (Thu) by allesfresser (subscriber, #216) [Link]

Since I'm a Slackware user, the switch to RPM was a very unpleasant shock. I sure hope they don't do this for the release builds, since all I get out of OOo2 right now is "sorry, an internal error occurred...", etc.

(I realize I could just download the source and compile it, but I have better and more pressing things to do with several days of my time...)

Looking forward to OpenOffice.org 2.0

Posted Jan 6, 2005 13:10 UTC (Thu) by ringlord (subscriber, #6309) [Link]

I have the same problem. Why not let there be a tarball to download?

Looking forward to OpenOffice.org 2.0

Posted Jan 6, 2005 8:06 UTC (Thu) by ekj (subscriber, #1524) [Link]

The limitations on numbers of rows are really friggin embarassing. It's 2004 people, normal home-computers come with hundreds of megabytes of ram, a dataset with oh, say, a million records can no longer be considered "large" in any sense.

So, someone replaced an int with an unsigned int and gained a factor of 2 improvement. Wow ! If this was 1975 this would be a valuable improvement indeed.

There is absolutely no valid reason why a spreadsheet should have any limits on the numbers of rows, columns, sheets or anything else, other than the memory-limits imposed by the machine itself.

And no, the fact that Microsoft does it that way is not a good excuse.

Looking forward to OpenOffice.org 2.0

Posted Jan 6, 2005 9:04 UTC (Thu) by PhilHannent (guest, #1241) [Link]

If you did have a million records really you should be using a database application.

Having the limitation is good in my view as it forces people to use the right tool for the job.

Looking forward to OpenOffice.org 2.0

Posted Jan 6, 2005 23:05 UTC (Thu) by njhurst (guest, #6022) [Link]

No it doesn't, it means that they make silly hacks around the problem, like spliting the data over mulitple worksheets. I know this is true in at least one large financial institution.

Looking forward to OpenOffice.org 2.0

Posted Jan 6, 2005 12:12 UTC (Thu) by remijnj (guest, #5838) [Link]

I agree completely, i used to work for a company where some of the mathematicians (statistics mostly) would use Excel a lot for quick calculations. They often ran into the max 64K rows problem. The trick is to just use multiple sheets but it is indeed pathetic.

This was already a problem in 1998 when i worked there. It will be even more of a problem in 2005. What's next, a new MS-Office which does allow more then 64K rows which will then be "better than OpenOffice"?

Someone needs to fix this if the 64K limit exists in OpenOffice.

Looking forward to OpenOffice.org 2.0

Posted Jan 6, 2005 12:42 UTC (Thu) by pivot (guest, #588) [Link]

From the screenshots it looks as if they still don't have subpixel font rendering, only grayscale antialiasing?

Looking forward to OpenOffice.org 2.0

Posted Jan 6, 2005 22:22 UTC (Thu) by spitzak (guest, #4593) [Link]

You don't want that if you don't have an LCD display, or if you have one of those
LCD displays with RGB reversed, or are using it in portrait mode), as the
resulting color fringes will look terrible. For this reason if you want a screenshot
to look good when people view it, make it with subpixel rendering turned off.

The only other solution would be to save an image that is 9 times bigger (3x3) in
antialiased mode and add code to browsers to correctly dither this into colors to
match the subpixels on their LCD display. This is not going to happen soon.

export is important, too...

Posted Jan 12, 2005 3:18 UTC (Wed) by roelofs (guest, #2599) [Link]

Unlike "this reporter" (aside: that always sounds kind of stilted; how about "your reporter" for consistency with Jon's grumpy articles?), I've occasionally had the need to export MS formats, too. It would be nice to see some data on how (or if) that's improved, too.

For example, in Impress vs. PowerPoint, it's perhaps not surprising that partial transparency doesn't work right; that's a relatively new feature even in PowerPoint. (For the record, it doesn't work at all over RDP, nor via some of those web-based shared-meeting apps.) And font-rendering is always a little dicey, so one expects some sizing differences. But basic line-wrapping in text boxes is the sort of thing one simply expects to work, so I was rather dumbfounded that it didn't. (And it was broken in both directions, too: wrapped in OOo => not wrapped in PPT; wrapped in PPT => not wrapped in OOo.)

Since I encountered those problems in a couple of days' light usage (which accounts for nearly all of my usage over the last six months), I'd bet there are a lot more of them--particularly for Writer vs. Word. Any indication of export improvements in the release notes so far?

Greg

Copyright © 2005, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds