OpenOffice.org: Interactions Between Programs
Some people insist that OpenOffice.org should be called an office application instead of an office suite. The distinction that they are trying to make is that the programs in OpenOffice.org share a common code base, instead of being separate programs that are simply bundled together, the way that Microsoft Office's are.
This distinction means that the complete OpenOffice.org is much smaller than any version of MS Office (and that you don't save nearly the space you expect by installing only the components you actually use). It also means that many dialogs are identical in different programs, which makes them easier to learn. And, most important of all, it means that the separate programs can easily interact with one another.
Writer and Impress
One of the features of Writer that hardly anyone knows about are those that transform existing content. You can find them in the File -> Send sub-menu. From there, you can create a master document made of multiple files, copy the entire document to the clipboard, create an AutoAbstract and, send the current file either as an email, or as an attachment in Open Document, MS Word, or PDF format.
When you create an outline, either manually or by clicking Create AutoAbstract, you can create the outline of a slide show in Impress with either Outline to Presentation or AutoAbstract to Presentation. These choices, which produce similar results, are ideal when you want to write an article, and immediately produce a slide show based on the article. Fittingly enough, the new slide show opens in Outline view, but the Normal view is only a click of the tab away.
By selecting either of these menu items, you create a new slide show, with a new slide for every Heading 1 style in the Writer document. Any Heading 2 styles become top-level bullet points on the slide, and any other Headings become sub-bullet points. Probably, you'll want to confine yourself to five or six Heading 2 or lower paragraphs in the Writer Outline, so that they will fit on the slide.
These choices depend on your use of at least one Heading style, and are grayed out if none are in the current document -- making them one more example of how OpenOffice.org encourages the use of styles if you want to take full advantage of its features.
Calc, Draw, and Impress -- the other main OpenOffice.org programs -- lack Writer's options for transforming documents, although all have similar options for sending as email.
However, in all four of the main programs, you can embed another OpenOffice.org file by selecting Insert -> Object -> OLE Object. I am told that you are not using true OLE technology under GNU/Linux, which does not support it, but the results are much the same as though you were.
You can embed a file from one of the four main applications, or a chart. Your options are to create a new embedded file, or embed an existing one, either creating a separate copy of it, or keeping a link to the original
But why would you want to embed one file in another? The most obvious answer is convenience. When you embed a file, you do not need to reformat, the way you would if you copied and pasted. Although the result is not elegant if you embed, for example, a Calc spreadsheet in a Writer document, but for a private document, that may not matter. In compensation for the lack of elegance, you get the same set of controls that you would if the embedded document was opened in its proper program. Also, because so-called OLE objects are embedded, they are stored in the OpenOffice.org cache when the parent document is open, which means they open quickly.
However, the best reason for embedding is only revealed if you choose to maintain the link to the original. If you do, when the original document is edited, you can open the parent document and automatically update the embedded document. So long as you keep the link between the original and the embedded version of the file, you only need to update once.
Keeping the link to the original can be a tremendous time-saver, especially if you are going to be maintaining the parent document for some time, and parts of it will be continually changing. Instead of having to update two documents, you only need to update one and the other will follow. Nor do you have to worry so much about missing sections that need to be updated, because the updates are done for you.
The best way to embed documents, I find, is to place them in separate sections. That way, you can locate them more easily, and any differences in formatting become less important.
Giving yourself an edge
Most people, I suspect, use OpenOffice.org without ever taking advantage of such features. And, naturally, they are perfectly free to ignore them. But, like styles, taking advantage of OpenOffice.org's connectivity between programs requires less duplication of effort and less time than bulling your way through manually.
Take a moment to familiarize yourself with these tools -- especially if you regularly need to repurpose or update documents. You'll only need a few moments, and you'll be glad you made the effort.
Bruce Byfield (nanday)
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- SourceClear Open
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide