No sooner did I get my RPG notes put into nice comfortable TiddlyWikis than version 2.2 was released. Well, that’s alright. The upgrade didn’t work with the first, easiest (but weird) method they suggested, but the second method (which is the one I would’ve guessed) worked: start a new, blank TW. Import all your tiddlers.

I especially liked the accordion and inline sliders stuff… but I’m not using it yet.

Through aldaily.com, I got this link and followed it, because I greatly admire the work of W. H. Auden.

Once again, Aaron Straup Cope has written code so I don’t have to. Last time, I wanted to back up my bookmarks from del.icio.us, so I didn’t feel paranoid that they might go away and take my bookmarks with them. (This was before I switched to Rubric.) Because Net::Delicious existed, I was able to write Net::Delicious::Simple on top of it, taking only a few minutes instead of hours of toiling with XML.

There are apparently a lot of TiddlyWiki plugins or rewrites centered around “Getting Things Done” or other project management systems. That’s not what I did today.

I’ve finished converting all my OmniOutliner and LaTeX notes to TiddlyWiki, and along the way I’ve found a few things I didn’t like or that I thought were missing. Rather than just bitch, I though I’d fix these problems, and doing so has been a load of fun. Hacking on TiddlyWiki gives me the same kind of joy and awe that I felt when I first started programming in Ruby. In a lot of ways, I think TiddlyWiki is what Kwiki wants to be. Nearly everything builds atop a few simple structures, and everything is pluggable. Writing plugins is easy, editing templates is trivial, and only a very few lines of code are needed to add new features.

John Cappiello pointed me at this really pretty excellent vi-in-javascript thinger that lets you use an extremely vi-like interface to edit a textarea.

I run two RPG groups, and they take place in the same campaign world. I’ve got a lot of notes on it, and I’d like to make it easier for the notes to cross-reference one another. I didn’t want to use a server-based wiki, because I wanted to use Vim to edit things, and Mozex seemed like a big pain, at least on OS X.

I’ve been writing mini-articles about some of 5.10’s new features for ABE.pm, this past week. It’s been fun, and I’ve learned a few things that I didn’t know in the process. The feature that I knew the least before covering it, so far, has been assertions. Assertions let you have code that only runs if some set of assertions are enabled. It’s something like this:

First: