On Mon, Dec 2, 2013 at 10:05 AM, Jan Honza Odvarko <[email protected]> wrote: > On Monday, December 2, 2013 5:35:53 AM UTC+1, pd wrote: > >> My impression was that the DevTools people (of which there are seemingly >> many) were fully intending to develop the DevTools in an open manner in that >> Add-ons would be free to interact with them. > > That's correct. All API related to JSD2 (the new debugging engine) as well > as RDP (remote debugging protocol) are open and supposed to be used by > extensions like Firebug.
The impression that I've gotten is that browser makers are all proceeding full speed ahead on improving and extending the toolset available for development and debugging in the browser. In one sense, that's good: it gives things like Firebug a base to build on and extend. On the other, it appears that these developments are increasingly adding things people used to use Firebug to do, and in some cases browser tools are competing with Firebug. How much of Firebug's code is being made redundant because you can now do it in the browser itself? How much does Firebug need to change to call browser functions through an API instead of doing things itself? > Honza ______ Dennis https://plus.google.com/u/0/105128793974319004519 -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/CAF4AJDycg%3Do8neBEd%2B8ktBD6BEteRcgistrB%2BefF2jj5sDxrzA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
