Thanks again for another handy mini release. I noticed the nice new search box treatment before I even realized I'd been upgraded :)
Regarding the progress of towards adopting the new debugger, can you say more about the platform APIs issues you mentioned?
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.
On Monday, December 2, 2013 5:35:53 AM UTC+1, pd wrote:Thanks again for another handy mini release. I noticed the nice new search box treatment before I even realized I'd been upgraded :)
Regarding the progress of towards adopting the new debugger, can you say more about the platform APIs issues you mentioned?
Bug 637572 - [jsdbg2] Implement Debugger.Source, providing script source code and detailed origin information
The last missing piece in our JSD2 branch (the branch where the entire JSD2 adoption process happens) is related to debugging dynamically evaluated scripts (new Function(), eval, event scripts). I believe that the bug above it the only one blocking us (or at least I don't know about anything else at the moment).
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.
Honza
On Tuesday, December 3, 2013 2:05:49 AM UTC+11, Jan Honza Odvarko wrote:
On Monday, December 2, 2013 5:35:53 AM UTC+1, pd wrote:Thanks again for another handy mini release. I noticed the nice new search box treatment before I even realized I'd been upgraded :)
Regarding the progress of towards adopting the new debugger, can you say more about the platform APIs issues you mentioned?
Bug 637572 - [jsdbg2] Implement Debugger.Source, providing script source code and detailed origin information
The last missing piece in our JSD2 branch (the branch where the entire JSD2 adoption process happens) is related to debugging dynamically evaluated scripts (new Function(), eval, event scripts). I believe that the bug above it the only one blocking us (or at least I don't know about anything else at the moment).
Sounds like the new debugger is much closer than previous suggestions re how long it would take to integrate, suggested. Is that the case?
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.
Honza
Ok, good to know the "we are yet [again] blocked by missing platform APIs" are not blocking adoption of the new debugger. Which APIs are you referring to?
On Mon, Dec 2, 2013 at 10:05 AM, Jan Honza Odvarko <odv...@gmail.com> 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?