Using Freemind as a Writing Planner
Freemind, the open source Java based mind mapping application, makes a great writing planning tool. A final release of version 0.9 has been a long time coming, but the current release candidates are very usable and stable, and I would recommend making the extra effort to install one of these rather than an 0.8 “stable” release. Fortunately, the 0.9 RCs have made it into the standard Ubuntu 10.04 repository.
Thankfully, Freemind is a keyboard friendly application. The first thing I do when I'm using Freemind to plan out an article is to rename the first node by hitting F2. You can add new nodes by hitting the insert key and then typing in a title for the node.
At the beginning of the process, I prefer an approach of dumping ideas into the mind map rather than worrying about where it belongs in the overall structure. Often, I read up on the subject while alt-tabbing back to Freemind to make notes.
Before long, you'll want to save the file, and this reveals a weakness of Freemind. Owing to the program's Java roots, the file requester is a bit cumbersome and lacks directory hot links. Typically, however, it's an awkwardness that you'll only have to deal with once per project. However, the Java nature of the program means that the user interface couldn't really be described as lightning fast. By the same token, initial application launch time is on the slow side. Neither of these problems make much difference for typical desktop usage but Freemind wouldn't be my first choice in a resource constrained environment.
Once I've got a few ideas onto the page, in the form of branches that are linked to the initial node, I start to think about structure. I've seen mind maps that go off in all directions, but my view is that a document such as the main body of a magazine article is ultimately linear, and for this reason, I like to end up with a mind map that is as vertical as possible. It's like a game of patience, and I tend to spot outlying ideas that can be added to the main stack of ideas, along with branches that can be combined. If an idea won't fit into this scheme it often means that it doesn't have a place in the article, or it would work better as the basis of a side bar.
You can move a branch to a different place in the structure by holding down the control key and using the cursor keys. Given the graphical approach of mind maps, the mouse is well suited to moving branches around using drag and drop, but keyboard control is sometimes preferable for speedy rearrangements.
Text notes that can be attached to a branch are a welcome addition of 0.9. Personally, I use this feature quite a lot, so I expand the notes window to fill the bottom half of the main window.
The export features gives you everything that you're likely to need, supporting various text based and graphical export formats by default. Although, inter-operation with other, similar tools is limited. SVG export is enabled with the addition of a separate package.
The application itself features plenty of extra features such as the inclusion of hyperlinks and images, but as you might imagine, in this role, I tend to only use the basic features. Being Java, it's available for most of the major platforms, often an important consideration when evaluating a creative application.
What about the rest of you, what writing planning tools do you use?
UK based freelance writer Michael Reed writes about technology, retro computing, geek culture and gender politics.
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
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- 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
- Rogue Wave Software's Zend Server
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