Creating a Lulu Book Cover with Pixel
Last month, I dove into LyX, a graphical LaTeX typesetting program for Linux. Because LyX produces commercial quality documents, it's an ideal match for the Lulu.com self-publishing Web site.
I'm reasonably certain most authors send material that comes from a standard word-processing program, such as Microsoft Word. Look back at the article in the December 2006 issue of LJ where I show you some output between a word processor and LyX to see what a difference it makes for your final product.
This time, I finish our book publishing tutorial. Publishing to Lulu.com is a two-step process. First, you need to upload your finished text files to Lulu. Then, you need to design a cover for the final product.
After Lulu accepts your text file, it asks you to format or upload a cover for the book. You have two choices: use one of Lulu's predesigned cover backgrounds, or upload a custom book cover that you created.
The sample book covers Lulu provides vary and may suit your publication just fine. If you decide to use one of those, the on-line system will help you add text to the image. Lulu's on-line program will place the author, ISBN and copyright notice for you as well. However, creating a book cover yourself is a great opportunity to examine Pixel.
In my estimation, Pixel is not a direct competitor of The GIMP. Pixel is a commercially produced application that runs on many operating systems. The Pixel Web site (www.kanzelsberger.com/pixel) notes at least six different operating systems, including Linux, Windows and Mac OS X.
By its own description, Pixel seems suited for advanced graphic artists. In fact, the first non-beta version of Pixel should include Photoshop plugins and .psd import and export. See www.kanzelsberger.com/pixel/?page_id=60 for more details and a list of features for the next release.
Pixel is not free. It is available as a demonstration software package, and users can buy a license for $32 US. This fee includes unlimited support and all updates until the next major release.
The demonstration copy does have a significant drawback. Any image created with Pixel contains a Pixel watermark. There is also a small “nag” screen reminding you to buy the product to get full use of the software. So, you can't use any graphics produced with the demo version.
I don't find this objectionable. Pixel's author intends to steer the software to compete with the leaders in the graphics industry. Although the expected version 1 price is around $100 US, it's still less than the competition. I like competition; it helps keep prices down.
Because Pixel is not open source or free, it's not likely you will find it in a major distribution's repository. So, download a demo copy from www.kanzelsberger.com/pixel/?page_id=4. Installation is straightforward. Download the Linux .tar file, unpack it and click on the file to start program installation. Follow the instructions on-screen to finish the setup.
Once complete, start Pixel from the command line or your system menu, and the home screen appears (Figure 1). At first impression, Pixel looks similar to other top-line commercial software. It's also different from The GIMP, because it covers your entire screen. In addition, many tools are in full view by default (Figure 2).
The screen layout is clean. Some of the icons are a bit troublesome to identify due to their size. But, trying to find hundreds of unique pictures for tools must be challenging for any programmer.
Now you're ready to begin. Because Pixel is still in beta release, documentation is scarce. In March 2006, the Pixel support forum explained that no documentation is ready as the focus is on product development. There is a help system available by pressing F1 (Figure 3), but currently no embedded tutorial exists. Even without much documentation, Pixel's layout is somewhat intuitive. If you know Adobe Photoshop, you're in luck—it's nearly the same.
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- The Secret Password Is...
- RSS Feeds
- New Products
4 hours 7 min ago
- Keeping track of IP address
5 hours 58 min ago
- Roll your own dynamic dns
11 hours 11 min ago
- Please correct the URL for Salt Stack's web site
14 hours 23 min ago
- Android is Linux -- why no better inter-operation
16 hours 38 min ago
- Connecting Android device to desktop Linux via USB
17 hours 7 min ago
- Find new cell phone and tablet pc
18 hours 5 min ago
19 hours 34 min ago
- Automatically updating Guest Additions
20 hours 42 min ago
- I like your topic on android
21 hours 29 min ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?