Couple of months ago I started a little “via Twitter” only campaign and now I think it’s the time to give it more visibility, because the deadline is in 20 days.
The main idea is: for every tweet [tooltip title=”Yes I Will” gravity=”e”][mark color=”yellow”]I will run 1[/mark][/tooltip] meter on Prague Marathon on September 8th 2012 (yes in 20 days) and will donate some money to an open source project.
[box color=”orange” icon=”flag”]
Join the campaign now – it’s FUN. Fell more than free to share it with your friends.
One of the coolest way to bring the knowledge to the masses is to …write an article for a magazine. I know it’s kinda old fashion, but there are a lot of people that are reading actually magazines.
I will write 2 articles in next several days about JetPack and AddOns in general for JSMag and .Net Magazine (Bulgarian edition) and I hope I will get more people trying to write an AddOn or just diving into this new technology.
I will be stick on:
0. What is an Addon and why we should create more of them.
1. JetPack Architecture and structure.
2. JetPack API (panel, widget and more).
3. How to write an external reusable library.
4. How to remix the code and add your JS to an AddOn;
5. How to use SDK to develop, pack and test your AddOn.
So I wanted to create a simple JetPack debugger that will write me some data and will dump me some objects on my …Firefox error console.
Here is the code. This simple tutorial shows :
0. How to use some of Firefox Services via Services.jsm
1. How to work with nsIConsoleService
Why I need that? Well I want to debug some of my extensions without using console/notifications or Firebug. This can be usable for getting better support for users. You can always put some debug lines on your code that will be visible for your addon user.
Anyway this is an example library and it’s not for production use :)