Just read this, http://canuckistani.ca/how-i-quickly-write-add-ons
, and, I have to say, I'm really disappointed. I've written a number of Chrome extensions and have been wanting to try it on FF as well. A number
of things in this post concern me:
1) "you need to install the Add-on SDK"
Ok, so not a huge deal to need a SDK, but with Chrome I just need my favorite editor. When you want to deploy you have to do some packaging, but for your initial creation there is no SDK - just web standards.
2) "in Firefox, install Wladimir Palant's excellent Extension Auto-installer extension. This extension allows you to reload newer builds of your extension into Firefox without having to re-start."
Ouch - I read this as, "If I fix a typo in my extension, I have to restart FF." If right, and I may be wrong, then that is really bad. I mean, it sounds like they have a workaround, but you shouldn't need a workaround for this. In Chrome you keep the Extensions tab open and click Reload on your extension. That's it.
3) "The cfx tool does this already, but it creates a skeletal add-onwith example code and I almost never want that."
Ugh. PhoneGap/Cordova does the same thing. The example code is great
for your first time. But EVERY other time that crap just gets in the way. Cordova finally
added an option to let you copy in something else on project creation, and I get that you want to make it easy for new developers to your platform, but there really should be support for your experienced
developers as well, and it shouldn't be some add on. IMO, add a flag, -d (no demo) and skip adding the Hello World BS.