Here's a graph (or a chart if you're that way inclined) of the users of one of my add-ons over time. Firefox 14 - 16 are missing from it which is confusing, but that's not the unusual bit. Let's see if you can spot it:
Sorry if you've been writing to me about my add-ons or other work... these things have been on the back burner for me lately.
Oh, and I have a broken wrist and won't be writing any code for some time.
Recently I've decided to make better use of my GitHub account by putting some of my work out there for others to see and contribute to, if they feel the need. It's also been a chance to read through a lot of my old code and tidying it up (plenty of WTF was I thinking? moments).
So here you go, DarkTrojan on GitHub.
Bug 777882 was filed recently, so I've now been around for half of all the bugs on bugzilla.mozilla.org. My first bug was 388941 (not a spectacular success).
As I write this, the builders are compiling code without nsILocalFile for the first time. It's no longer used by any interface or C++ code - except for a few places where it's necessary to avoid everything blowing up. This should make working with files simpler and less confusing for new people, such as first-time add-on developers.
Yesterday I landed bug 718255, taking the guts out of nsIPrefBranch2 and putting them into nsIPrefBranch. That means a QueryInterface call is no longer required to add or remove pref observers. (The interface still exists, to prevent stuff breaking, but it is empty now.)
Hackers and reviewers, please take note. I don't want to be clearing out stray uses forever.
Hey Mozilla devs, are you sick of typing
TEST_PATH=... make -C objdir mochitest-browser-chrome only to remember halfway through that you're trying to run an XPC shell test, and have to type something completely different? Me too!
There's currently at least 7 makefile targets for running the common unit tests (mochitests, reftests and XPC shell tests). It's a pain remembering which one to use. So I've created a Python script which will do it for you, and you'll only need one command to run tests ever again:
"Where do I get this magic script?" you ask. It's here. It could be more efficient, it could be better documented, and it could be written by someone who actually knows what they're doing with Python. Who cares? It works.
Oh no, who started this again? Blair tagged me.
Nah, can't be bothered doing this. It's my blog so I'll not do it if I don't want to.