Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Software Books Media Book Reviews

OpenOffice.org Resource Kit 239

Eater writes "With a 1.1 release imminent, this review may be of interest to users of Linux on the desktop. OpenOffice.org is a group of small projects that collectively make up the open source community's premier office suite. Based on code from Sun's StarOffice and maintained by a worldwide community of developers, the OpenOffice.org project provides a full-featured office application suite. It includes a language independent API and open XML-based file formats." Read on for the rest of Eater's review.
OpenOffice.org Resource Kit
author Solveig Haugland, Floyd Jones
pages 1040
publisher Prentice-Hall PTR
rating 9
reviewer Eater
ISBN 0131407457
summary An essential introduction to OpenOffice.org.

With a stable 1.0 release and spectacular cross-platform functionality, it's finally time to seriously consider putting this software to work in your company. Whether you are completely new to OpenOffice.org or just moving from its predecessor StarOffice, you'll want to take a look at OpenOffice.org 1.0 Resource Kit from Prentice Hall PTR.

The "kit" consists of a well written tutorial book and a companion CD-ROM. The book's authors (Solveig Haughland and Floyd Jones) are salty veterans in the technical training field, and it shows in the quality of the text. The CD contains the OpenOffice.org release itself, as one might expect. It provides builds for every supported platform, to include the Mac OS X developer alpha version. At the time this review was written, two minor upgrades have been made available since my book's CD-ROM was pressed. These are, naturally, available for free via the OpenOffice.org web-site. In addition to the releases, the CD includes templates, macros, and examples from the developer community. The authors provide additional templates and resources at http://www.getopenoffice.org

The first five chapters of the book are devoted to basic issues such as installation, migrating existing data, printer issues, and global setup tips. Special guidance is given to users switching over from StarOffice, or even that Redmond company's office suite. Speaking of that company, OpenOffice.org is superb at converting Word, Excel, and PowerPoint files into its own open formats. The book shows how to use the handy "AutoPilot", which can perform batch conversions of your existing data for use with OpenOffice.org's equivalent applications. Originals are kept safely intact-- AutoPilot produces converted copies. This could make a large office transition much easier, if not completely seamless.

The next six chapters cover the creation of written documents in fantastic detail. The organization of this section is quite intuitive; you'll easily learn how to create a simple letter. When you're ready to write your memoirs, you won't need to buy another book--it's all there: complex formatting options, page layout functionality, object manipulation, linking cross-references, and indexing. And don't forget office goodies like mail merges, label printing, and business cards.

Chapters 13-17 focus entirely on web-page development. Serious web designers may find this section bordering on useless, but the casual user will be able to create a home page without learning a single tag of HTML.

The next several chapters deal with Calc (a spreadsheet program), Impress (for creating presentations), and Draw ("the best drawing program you've never used," say the authors). The layout of each section follows the comprehensive example from the earlier chapters detailing OpenOffice.org's word processor, Writer. Basic topics are organized neatly along with the more advanced ones, and neither seem to get in the way of the other. Both the novice and the expert will find very little lacking from this material.

Organizations who deal frequently with databases will not be disappointed with OpenOffice.org, either. The final three chapters of the book explain how to incorporate data from any flavor database you're likely to be using in your network. Throw in an appendix on macros, and you've got one very complete tutorial masquerading as an all-in-one reference. I'm very picky when it comes to my geek shelf space, and this one gets high marks in all the important areas: comprehensive, well organized, and with a great signal-to-noise ratio.

We have learned that superior open source software alone isn't always enough to supplant the existing closed source way of doing things. However, "document it, and they will come!" The OpenOffice.org 1.0 Resource Kit will go a long way toward fulfilling that prophecy.


Reader Marcus Green sent in a review of this book as well. Here are some of his thoughts:

In addition to the document management features the book covers the more "Page Layout" style features of StarOffice such as the ability to manage columns and to place vertical text running up the page. These are features I was not even aware existed in StarOffice before I read this book.

The StarOffice companion has over 1030 pages, but it is really bigger than it sounds because it is very dense. Although it has many screen shots, plenty of use is made of text based instructions. Instead of repeating instructions, the text will often point you to the page where a concept was first explained. This does break up the flow of instructions but it also means that the book contains more information than if they had repeated the text every time it was needed.

I found the section on the graphics module useful because I had not realised how StarOffice has some slightly non-standard ways of working with menus and selections. For example I spent quite a bit of time trying to get the 3d shapes menu to pop out and show all the possible shape options. It was only on a closer reading of the text of this book did I appreciate that you need to click and hold down the mouse for a few seconds before the menu pops out.

The tone of the book comes across as being created by people who like the program rather than a creation of a faceless corporation. Thus in the graphics section they have included the amusing Moose with moving fly graphic that is used for the logo of the JavaRanch website. Here is an example of the text style from the section on macros. "Macros can do things like open a file when you do a particular task, process data, or take your grandmothers' credit cards and buy $3000 worth of cat toys." It also features a section titled "Turning Off Annoying Features," which of course is about the autoformatting and word completion.


You can purchase the OpenOffice.org Resource Kit from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

This discussion has been archived. No new comments can be posted.

OpenOffice.org Resource Kit

Comments Filter:
  • Setup (Score:4, Interesting)

    by Anonymous Coward on Thursday July 17, 2003 @12:04PM (#6461904)
    I'd be happy with soem simple tips on scripting a setup so that "open file" points by default to a user's network drive and so that the display and toolbars are uniform within our firm. I do not relish setting up a dozen computers to make the settings match.

    Basically, scripts or config tools would be cool.
  • by Anonymous Coward on Thursday July 17, 2003 @12:06PM (#6461936)
    Back in the days, the Amiga had AREXX & OS/2 had REXX. These were for scripting ANY compatable application.

    Why don't we have these nowadays?!?!?!?

    Then we wouldn't need entire books like this, and could get better functionality from all our programs...
  • Re:What's sad... (Score:4, Interesting)

    by nobody69 ( 116149 ) on Thursday July 17, 2003 @12:10PM (#6461982)
    luugi -

    What problems have you had with opening MS Word docs? I've been using OO.o for a while, using myself as a test subject to see if we could replace all/some of our MS Office suites with something comparable. I haven't noticed any problems, but I'd like to hear what other people have issues with.
  • by aussersterne ( 212916 ) on Thursday July 17, 2003 @12:10PM (#6461990) Homepage
    While we're on the subject of StarOffice/OpenOffice, I'm going to post a question about it here because Slashdotters are more likely to be able to anwer than those kids over at the OO forums.

    OpenOffice is able to inherit and use the toolkit/widget colors that I select in Linux/KDE. i.e. if my widgets are all brown in other apps, they are also brown in OpenOffice. However, when I am using WindowMaker or another simple managed environment rather than KDE, OpenOffice comes up in Windows NT gray and I can't seem to change that.

    I've done an "xrdb -all -edit myrsrcs.txt" from within KDE to grab all the krdb stuff and then an "xrdb myrsrcs.txt" from within WindowMaker, but that didn't help. All of my GTK/GTK2 apps look the way I want them to at this point because my .gtkrc and .gtkrc-2.0 files and relateds are all configured correctly for my color preferences... but OO doesn't seem to see these either (I haven't checked to see if OO is a GTK app at all).

    I even tried "kfmclient file:/opt/OpenOffice.org/progrms/swriter" to see if I could get the KDE colors into OO that way without actually having to be logged in to KDE, but it didn't help.

    Does anyone know how to change the widget colors in OpenOffice without having to simply log into KDE or GNOME?

    P.S. final hint: using the Tools menu is not the right answer, it contains color options for a great many things, but the menu and toolbar widgets are not among them.
  • Upgrade (Score:3, Interesting)

    by HogGeek ( 456673 ) on Thursday July 17, 2003 @12:12PM (#6462006)
    Do they mention a manner in which to upgrade an installation vs. re-install?
  • Re:What's sad... (Score:5, Interesting)

    by jason0000042 ( 656126 ) on Thursday July 17, 2003 @12:16PM (#6462052) Homepage
    is that it simply doesn't import MS Word documents properly. MS Word is the still the norm wether you like it or not.

    So we have two choices to what we can do.

    1. Give up.
    2. Support OOo whenever possible. By contributing, donating, or just using it when ever it makes sense for the project.

    I'm not much of a defeatist, so I'm going with option 2.

    Besides, it imports simple word docs fine. And really, Word is a word processor, not a page layout program. If you really want to do some fancy stuff neither word nor OOo are good. Go get pagemaker or quark.

  • by Swayne Shabazz ( 678612 ) on Thursday July 17, 2003 @12:18PM (#6462084)
    The more I use it (on both Linux and Windows) the more bugs and crashes I see. Granted, the more you use any particular application the more bugs you'll see - but OpenOffice Writer is the only application that I use that always seems to suprise me with an amazing crash or wild bug every single time I use it. Take for instance what happened about 5 minutes ago - when printing a document the window resized itself wildly, crashed, and the system locked up.

    It needs some real work.

  • by Zestius ( 526143 ) on Thursday July 17, 2003 @12:25PM (#6462165) Homepage
    I don't know, but on the Mac you have AppleScript, which works great for scripting any Mac application. You can even create your own standalone applications using AppleScript and AppleScript Studio (free with Apple's dev tools).

    So maybe it's time to change platforms? ;) Especially now that OpenOffice is coming to MacOS X. It will undoubtedly support AppleScript as well (heck, it probably does already).

  • We use this book (Score:5, Interesting)

    by rindeee ( 530084 ) on Thursday July 17, 2003 @12:32PM (#6462251)
    for our OpenOffice.org training classes and it is quite good. The customers/students have really given posotive feedback about it not only as a classroom textbook, but also as a reference for ongoing use. For what it's worth.

    ER
  • by r_j_prahad ( 309298 ) <r_j_prahad@@@hotmail...com> on Thursday July 17, 2003 @12:52PM (#6462508)
    ...we use OpenOffice to repair hopelessly munged-up Microsoft Word documents - which happens more often than anybody is willing to admit. I used to fix all the formatting fubars with WordPerfect but the two products have diverged so much in the last two years that we've discontinued using WordPerfect for anything. Anyway, everytime I get a user who asks me why she can't get her headers and columns to do such-and-such I snarf a copy off his/her server, import it into OO, undo the hideousness (sp?) and export it back out. And it generally stays fixed, even after subsequent exposures to MS Word, plus it's a lot smaller.

    Thanks to Microsoft, OpenOffice looks pretty damned good.
  • Re:Some solutions. (Score:2, Interesting)

    by pmsr ( 560617 ) on Thursday July 17, 2003 @01:23PM (#6462851)
    Yes, to tell you the truth I have tried it now for the first time, and it does work. I tend to prefer to open the document directly, though.

    /Pedro

  • by H310iSe ( 249662 ) on Thursday July 17, 2003 @05:34PM (#6465652)
    God I wish I didn't have to choose between replying and moderating...

    Anyway, the parent is only part of the truth. I can say from extensive experience with Word in a legal environment that yes, in fact Word documents do blow up when opened in Word. Number formatting is a big problem, but really any time you have a document stretching over 100 pages or so you're asking for all sorts of weird problems. Not every one, but maybe 1 in a couple hundred or so. Take a library with several million documents and you realize that's a @#*)! load of *&*)@!# up documents.

    MS intentionally obfuscated and otherwise complicated their binary document format (need I explain why?) and they have suffered almost as much as those trying to interoperate with it. Of course, since the world is locked in to Word it doesn't matter that their anti-competitive-driven technology decisions led to a fucked up product.

    I've tried to sort out deep-seeded Word document problems with high-level (like, the ones you pay millions in support contracts to get to call) MS folks and even they couldn't sort out the document on a binary level. Ghost in the machine is about as far as they could say whenever I called with a completely impossible-but-it's-happening problem. Save document as plain text and reformat is the mantra for anyone working with large Word documents for a living.

    For a small sample of Word-related issues see
    annoyances dot org [annoyances.org]
    Woody's Office Watch (amazing resource but you have to search through a lot of junk to find it).

    And, just as a foot note, VBA is the most buggy, slow, impossible to use programming language I've ever had the horror to use. I'm not just throwing the Buggy word around either, it's unpredictable, awkward, ass-backwards and slow slow slow.

    Me, I do web development now and use Edit Plus for all my document needs. I'm much, much, much happier now :)

Anyone can make an omelet with eggs. The trick is to make one with none.

Working...