Commentary

Serdar Yegulalp
 

OpenOffice.org 3 Edges Towards Release

OpenOffice.org's first release candidate for version 3.0 hit the tubes yesterday. It's an evolutionary, rather than revolutionary, edition of the open source office suite. It isn't to OO.o 2 what, say, Office 2007 was to Office 2003 -- but it's solid, and most importantly, noticeably faster.

OpenOffice.org's first release candidate for version 3.0 hit the tubes yesterday. It's an evolutionary, rather than revolutionary, edition of the open source office suite. It isn't to OO.o 2 what, say, Office 2007 was to Office 2003 -- but it's solid, and most importantly, noticeably faster.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

If there was one complaint I heard about OO.o more than any other, it was "It's too slow!" Slow to get started, mainly, but actually not all that slow when doing other things (at least not in my experience). On Windows, RC1 of version 3 opens all of its apps pretty snappily even without the Quickstarter running in the system tray. A well-engineered program shouldn't need a crutch like the Quickstarter in the first place, so I disabled it to see how well things worked without it.

Another major addition is native (if not feature-complete) support for Microsoft Office macros, something enormously useful to people trying to make a jailbreak from the Office but find they can't due to the need to support legacy macros. Financial houses and law firms seem to be two types of folks most heavily dependent on Office VB macros -- so maybe some success stories from their side of the fence will compel those with far less ambitious needs to make the jump, too.

One of the big selling -- er, using points -- for me has been OO.o's native .PDF support. Version 3 adds in the ability to import and edit .PDFs via a plugin, and a much more detailed and powerful .PDF export dialog. (Nominally I use a print driver to do .PDF export, but anything that exports natively within an app gets precedence.)

Version 3 also reads Office 2007's OOXML documents pretty transparently -- none of the Word docs I opened with it gave me problems -- but on the whole I'd rather convert to and use the standard OASIS document format to avoid any cross-compatibility issues. On that note, since OO.o 3 uses the most recent version of the OASIS document format (1.2), don't save anything as 1.2 if you intend to also open it in older versions of OO.o. You can force saving documents in the older version of the format through the Tools | Options | Load/Save | General menu.

I still see myself running Word 2007 for now; that part hasn't changed. But I see much more of a reason to use OO.o as a replacement for many other MS Office programs -- mainly Excel and PowerPoint, which I ditched almost two years ago and haven't missed once since. Each subsequent edition of OO.o has given me that much more of a reason to lean in that direction, and I'm hoping by version 4 Word will be gone entirely.

Next mission: replace Outlook if possible -- not just email but calendaring, to-do lists, all of it. For that I'm looking at Thunderbird 3, still in early alpha but which will be getting a lot more attention from me when the non-email components start getting rolled in. Tiny steps ...


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links