I might as well try and hype up what's coming, even though it's not quite there yet.

The biggest addition is alarms. The last version laid the ground work, this version includes the actual implemention. Sort of.

There's still quite a lot of work I need to do to decide exactly how the alarms are going to work. Right now they successfully get created and persisted across browser sessions.

I'm still working on the UI for creating them and managing them once they've been created.

I'm also going to look into adding a Balista calendar or (more likely) a "next x matches" schedule.

Compiling Mozilla under Windows requires a C++ compiler. Previously the only way to compile Mozilla under Windows without having to pay big bucks for the Visual C++ environment was to use the free Cygwin utilities, but those didn't include all the features that Microsoft's compiler did and didn't offer all the features that Mozilla has to offer under Windows.

Microsoft has since released the build environment (but not the GUI tools) to allow developers to write software under Windows without paying large amounts of money for Visual Studio. However, the process for doing this is fairly poorly explained. (And for good reason, it's long, annoying, and impossible unless you do some extra credit which is dubiously legal.)

OK, this is one of those "to be edited later" posts, but it's a start at writing a real quick tutorial on how to write a Firefox extension.

Settings Up Firefox

Before writing any code, we need to set up Firefox to make debugging an extension more possible. I mean, we could conceivably skip these steps, but then debugging anything would be a giant pain.

Anyway, first things first. Copy your Firefox shortcut or launcher or whatever you use for your system. Edit it and add "-console" to the command that starts it. So Windows users will wind up with something like: