Sent to you by Sparkie via Google Reader:
Google Chrome has had a V8 debugger for some time, and they just released a Chrome Dev Tools Protocol that builds on that:
The V8 Debugger protocol covers only JavaScript debugging operations, and only within a single V8 virtual machine (VM). In reality, there can be one or more separate V8 VMs inside a Google Chrome instance, residing in different renderer processes. Also, retrieving URLs loaded in the browser tabs, inspecting or modifying the DOM tree are not covered by JavaScript operations.
Because of these restrictions, the ChromeDevTools protocol has been created to enable the exchange of additional information between a remote debugger and the browser instance being debugged. The ChromeDevTools protocol can be used as a transport for other debugging-related protocols, including the existing V8 Debugger Protocol. The proposed protocol can be used as a transport for other debugging-related protocols, including the existing V8 Debugger Protocol.
One tool that builds on this is an Eclipse based debugger.
There are other efforts on the remote debugger front too that we have been watching. For one, we have Opera Scope, the Opera Dragonfly debug and inspection architecture. The Firebug working group has a Web Debug Protocol, and then there is the good old DBGP protocol originally from ActiveState.
Feels like a good time to get together so tools could speak cross browser.
Things you can do from here:
- Subscribe to Ajaxian » Front Page using Google Reader
- Get started using Google Reader to easily keep up with all your favorite sites
No comments:
Post a Comment