I’ve been much more organized since I finished my PhD. I wrote a small application to help me keep track of things that need doing, but… the granularity wasn’t right. That, and the theft of my Powerbook really made me realize that computer-based productivity solutions have limited utility.

When I heard that David Allan (author of “Getting Things Done: The Art of Stress-Free Productivity”) declared there would be no second edition of his book, I decided to buy it. (At least, I read somewhere that he declared there would be no second edition… but I can’t find the source, now. So that may be a complete lie.)

Either way, I’ve found two sites really useful in my “getting organized” kick that I’ve been on today:

  1. http://www.diyplanner.com/, a site full of do-it-yourself daily planner templates (of exceptionally good quality), and
  2. http://incompetech.com/beta/plainGraphPaper/, a site that lets me quickly and easily create graph paper.

It’s great awesome. I’m in the process of creating a daily planner that has the stuff in it that I want, and tailoring it to a fairly GTD-ish process that I’ll work at implementing over the next few months. Getting this ramped up before the move north (more on that later) means the move will be less traumatic in the end.

My preferred writing mode is LaTeX under Subversion. But what do you do if you’re collaborating with others, and not everyone is LaTeX-keen? What kind of options are there for collaborative writing?

I have a few requirements I’d really like to meet.

Requirements

  1. Plain text

    I would prefer that the document is stored in plain text—this is one of the only formats that have survived for the last two decades. I can still read plain text files from the 1970s, but I have a hard opening anything else on my Mac. Hell, I have a hard time with the Frame5 documents I created in 1996.

  2. Version control

    I must have version control over the document. There is no sense writing collaboratively if you can’t safely edit over each-other’s text. This way, you can get into a working mode where each author feels free to work on any part of the document. If one makes changes the other genuinely doesn’t like, this doesn’t matter so much, because you can roll back a rev and recover the text. Hence, automatic versioning is critical.

  3. Backups

    When I check things into my Subversion repository, I know that they are not only versioned, but backed up several times a week. I must have the same security in any collaborative writing program I use.

  4. Offline

    The solution must work when I’m offline. This rules out most web-based collaborative writing tools (eg. Google Documents).

There is, however, one critical requirement put forward by my colleagues:

  1. No control codes

    My colleagues don’t want to write directly in LaTeX. They have little desire to be typing in control codes to format their text. I, personally, like having a Turing-complete word processing system…

What does this rule out?

  1. Word is ruled out by my requirement #1. Current versions of Word cannot reliably open even old versions of Word documents. Therefore, no writing solution I use will be based on Word. (Or anything else with a closed document format).
  2. Google Documents does not work offline, meaning I can’t write a paper while on a long train journey in the UK. This defeats the purpose of having a 13″ laptop, if I can’t work on collaborative documents while away from the Interweb. A whole host of other on-line writing solutions are not viable as a result of this requirement as well (eg. Writeboard).

What does this leave available?

  1. OpenOffice is possible. It does use the Open Document Format, which is encouraging—XML will, as we all know, save us from oblivion someday. It does have change tracking, but not quite versioning (so it would have to be checked into a Subversion repository). OO provides no particular help with backups.
  2. LyX is a WYSIWYM (what-you-see-is-what-you-mean) LaTeX processor. You edit text, highlight stuff, and say “Title”, or “Section”. It makes it bold, or centers it, and so on. Actually, it’s really quite nice (for five minutes of usage, anyway). I found an interesting thread at the Ubuntu Forums where users were discussing LyX for collaborative writing in academia. This was encouraging.

If I had to pick a tool right now (which I said I would pick one over the weekend), I would pick LyX. This is because I can, if I need to, export to LaTeX and do any really hard tweaking (or supporting of journal-specpfic styles) that way, or (for most cases), I don’t need to. Also, looking at the features of LyX 1.4 (current stable is 1.4.3), the change tracking, notes, and some other features look like they’re just what are needed for multiple people working on a document. Put another way, the native format of LyX is plain text (check!), it can easily be checked into a version control repository (check!), is therefore easy to backup (check!), is a WYSIWYG/WYSIWYM word processor (check!), and it supports WYSIWYG change tracking (with different colors, and change bars, and the whole deal).

So, I’d suggest LyX for collaborative writing in the sciences, unless someone suggests otherwise. I will probably still prefer LaTeX and a plain text editor, but I may change my mind someday.

lyx-editing

Most of you don’t actually see Poul Henriksen on a regular basis don’t know that he has been claiming this release would come out “any day now” for, like, the last two weeks. But, today is today, and here it is!

Straight from the announce list:

Greenfoot 1.1 is available for download now.

http://www.greenfoot.org/

This version of Greenfoot adds various improvements, both the
performance and stability, as well as some new features.

The most noticeable of the new features is the support for sound. To
demonstrate the sound support (and exciting game programming in
general), we have also released a new scenario, named asteroids.

Both are available form the Greenfoot web site.

For those of you who are planning to attend the SIGCSE’07 conference
in March: We will be holding a Greenfoot workshop at the SIGCSE
conference. Come and join us!

The Greenfoot Team

Oooh! And I got to use the “releases” category, too!