Creating Applications with Mozilla by David Boswell, Brian King, Ian Oeschger, Pete Collins and Eric Murphy
Next to Linux, Mozilla is probably the most well-known and widely discussed open-source project. O'Reilly's Creating Applications with Mozilla appeared hot on the tail of the official Mozilla 1.0 release. It is notable for a number of reasons: 1) the entire text is available on-line (books.mozdev.org/chapters), as the book was written under the Open Publication License, and 2) it explains why the 1.0 release of Mozilla took so long to make an appearance.
This book shows that Mozilla is much more than a browser. In addition to offering capable e-mail, newsgroup and Web page composer applications, Mozilla contains a sophisticated Web client development environment. A series of technologies allows programmers to interact with and control Mozilla, and at slightly more than 450 tightly packed pages, Creating Applications with Mozilla is the definitive reference to these technologies.
I would have welcomed more extensive use of screenshots, especially in the chapters that describe creating and customizing Mozilla GUIs. The authors rely on textual descriptions such as, “the icons appear to the left and right of the bar, while the flexed text panel takes up the remaining space.” Pictures would have been better.
There's also some confusing language, especially in the earlier chapters. A particularly bad example of this is a sentence taken from the discussion of Box Attributes on page 63: “But there are also CSS versions of these properties that use the prefix box-pack becomes box-pack when it's defined in CSS, for example.” This sort of thing should have been cleaned up during copy editing. However, the entire text (plus errata) is available on-line to allow potential purchasers to try out the book before buying it.
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