Personally I have to focus on making Firebug/Firefox jump ahead, but I suggest that a good place to start would be to get the latest Firebug Lite and work with it on Chromium, reporting any problems and offering suggestions. The Lite team is moving their code closer to Firebug/ Firefox and eventually we may restructure to maximize reuse. If Firefox goes multi-process we may be forced to change our design, and would likely move in a less-Firefox-centric direction. At the same time I will be working hard to make debugging on the other browsers look weak by comparison, so I hope there will always be cool things that only Firebug/Firefox can do.
jjb On May 20, 11:23 am, jordan <[email protected]> wrote: > I know that the basis of this project is for use in Firefox, however I > know many people would like to see this extension for Chrome, and now > that v 2.0.180.0 has extension support, it may be a good time to start > working. I'm more of a Web Design person than a programmer. I would be > happy to help out in anyway though. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
