Awesome. One problem I'm facing is that there's hardly any documentation for the APIs, so I have to spend hours trying to understand the Firebug source code or trying to find information on Google. I hope there's plans to thoroughly document the APIs on the wiki (like MDN) and create a couple of tutorials.
On Aug 9, 10:34 pm, Jan Honza Odvarko <[email protected]> wrote: > On Aug 9, 7:32 am, Rowno <[email protected]> wrote:> Hi, I've recently > started learning Firebug extension development to > > make a new extension. From what I understand is that since Firebug 1.8 > > there's now two methods to develop an extension which are the standard > > XUL method and the new AMD method. I've read in various places that in > > Firebug 1.8 the AMD isn't quite ready to move existing extensions to > > yet. What I'm wondering is that since I'm starting a new extension > > from scratch, would be better for me to use the AMD method and save > > refactoring later, or stick to the old XUL method? > > In order to properly design AMD style APIs we need feedback from > Firebug extension developers so, you are welcome to start using AMD > and report any problem you have with it! > > There is already on report related to AMD based > extensionshttp://code.google.com/p/fbug/issues/detail?id=4718 > > I have also created HelloAMD example that shows how to use AMD in > extensionshttp://code.google.com/p/fbug/source/browse/#svn%2Fexamples%2Ffirebug... > > You can use it as a skeleton and base your extension on it (only > replace <ext-id> tokens). There is a lot of comments and some links to > other resources. > > Please let me know if you see any problem. > > Honza -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
