Firebug extension generally: http://www.softwareishard.com/blog/firebug-tutorial/extending-firebug-hello-world-part-i/
The component in Firebug that implements the feature: http://code.google.com/p/fbug/source/browse/branches/firebug1.5/content/firebug/firebug.js#3359 You also need to hook the callback in your module's initializeUI TabWatcher.addListener(Firebug.URLSelector); // listen for shouldCreateContext uiListeners.push(Firebug.URLSelector); // listen for showUI jjb On Jun 23, 7:55 am, Bill Barry <[email protected]> wrote: > Is there any documentation on this extension mechanism? > > I would be happy to try my hand at writing one (if possible to do the > scenario in the other post, if not then I guess domain whitelisting > would be good enough). > > johnjbarton wrote: > > Work on Firebug 1.4 is complete. Your scenario description is a good > > one, I wish we had it back when we were working on this feature. I'd > > love for Firebug to be perfect for everyone, but in every change there > > will be some winners and losers I guess. > > > The activation model in 1.4 was designed to allow extensions to > > provide special activation solutions. If anyone wants to create one > > for this use case we'd be happy to give advice. (Just to set > > expectations, I have no plans to do any more work on activation > > myself). > > > jjb --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
