EZ as a Word Processor
Some insets have special meaning for the formatting of the text document. They generally have their own menus. If you select the “Insert Pagebreak” menu item, a thin horizontal line appears on the screen. This causes a new page to begin when the document is printed or previewed.
Footnotes can be added to your document with the “Insert Footnote” menu item. The footnote will appear as a small square with a star in it. Footnotes can be open or closed by simply clicking in the box. They are displayed in-line as shown in Figure 3, but print at the bottom of the page, as you would normally expect.
A page header or footer can be specified for your document by inserting the Header/Footer inset on the Media menu card. As shown in Figure 3, you can specify various fields. There are special $-keywords you can use for variable data. Select the AUIS Help menu and then select Show Help On... When prompted, enter headers to get more detail on headers. Alternatively, you may enter auishelp headers in an xterm window.
The list of styles that come with ez is usually sufficient for simple documents. However, you may need better control of tab stops, paragraph indenting or outdenting, or double spaced lines. Perhaps you want your own combination style that sets the margins, font, point size all from a single menu item. All this and more can be done by selecting the “Edit Styles” menu option. This brings up a second window which is divided into several panels, as shown in Figure 4.
The style editor window has its own menus. The top part of the window, above the double line, is used to select a style to edit. The left-hand panel is a list of all the menu cards that have style options. If you select a menu card name, it is highlighted and its list of styles appears in the right-hand panel. Once you select a menu card and style name, the rest of the panel becomes active. It displays the attributes that apply to the selected style.
To change the attributes of a style, highlight the different options in the attribute panels. The document will not change until the document is redrawn. You can select “Update Document” to force the redraw.
Choose the menu item “Add Style” to create your own style. When you do this you are prompted in the message area at the bottom of the screen for a menu name. You should enter a pair of names like “Region,MyWay”. This will add a menu item “MyWay” to the “Region” menu. You should then select the attributes you want for this new MyWay style.
When you edit or add styles with the style editor, the changes only affect the document you are currently editing. They are saved in the data and will exist when you edit the document later. If you copy text containing the new style and paste it in a new document, the style will be transferred to the new document, but the attributes of that style will not be transferred. This is because the attributes of the style are saved at the top of the file in an area you cannot see. So when you copy the selected area, you only get the name of the style, but not the definition of the style (which you cannot see). You will need to either add a new MyWay style to the second document or learn about templates.
A template is a set of ready-made formatting information or instructions that you can apply to a text document. Templates describe two types of information:
Style specifications, which determine what formatting styles (such as boldface and centering) can be applied to a document, and exactly how they change the appearance of the text to which you apply them. Thus templates lend a standard appearance to documents by making a style always look the same.
Set text, which is text that you want to include over and over in many documents. A template saves you time in this case because you only have to type that text once. ez gives you an extensive set of templates. Most of these include style specifications only, but some also include set text (e.g., the template used for creating memos). Creating a template is described in detail in the on-line help (enter the command auishelp templates in an xterm window).
The entire AUIS system is designed to print using PostScript. This was a decision made many years ago and is still in transition. In this version AUIS objects all generate troff output—along with copious amounts of embedded PostScript. The troff is then processed to generate the necessary PostScript. In the auis63L0-wp distribution the default print command will invoke a shell, /usr/andrew/etc/atkprint. The default preview command calls the shell /usr/andrew/etc/ atkpreview. Each of these shells will invoke the groff formatter to generate the PostScript output. In atkpreview the groff output is piped into ghostview.
If you do not have a PostScript printer, you can modify atkprint to pipe the PostScript output through ghostscript to generate the correct stream for your printer. Andreas Klemm email@example.com has written a filter, apsfilter (available from ftp. germany.eu.net in /pub/comp/i386/Linux/Local. EUnet/People/akl/apsfilter*), which works with your /etc/printcap entry and will automatically convert PostScript into the correct DeskJet stream. I have a DeskJet 500 printer which works very well in this mode.
There are other ways to control printing/previewing by AUIS. These will be discussed in a future article about tailoring your AUIS applications.
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
- Google's SwiftShader Released
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Interview with Patrick Volkerding
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
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