[Webkit-unassigned] [Bug 35016] Enable alternate front-ends for Web Inspector

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Feb 17 10:58:47 PST 2010


https://bugs.webkit.org/show_bug.cgi?id=35016





--- Comment #5 from Jamey Hicks <jamey.hicks at nokia.com>  2010-02-17 10:58:46 PST ---
Created an attachment (id=48913)
 --> (https://bugs.webkit.org/attachment.cgi?id=48913)
Qt debug agent partially implementing ChromeDevTools and V8 debug protocol

For reference: This is a patch to Qt that implements remote Web Inspector
usage, supporting all Web Inspector functionality. It is a quick prototype and
not stable.

It includes an HTTP server in QWebInspector that can be enabled for remote
debug. It serves 4 information channels through the HTTP server:
1) Built-in resource files -- the HTML, Javascript, images, and style sheets
composing the Web Inspector UI (original encoding)
2) Asynchronous RPC to InspectorBackend via HTTP POST (encoded as JSON)
3) Polling for events to the frontend via HTTP POST (encoded as JSON)
4) Dynamic resources via HTTP POST (to fetch these resources from the same
context as the browser, in original encoding)

The Inspector front-end javascript is modified to use asynchronous style when
communicating with the back-end.

In my current design, the remote debug agent would not require instantiating
the Page for the Web Inspector UI nor would it require QWebInspector.

In terms of implementation, it was very quick because it does not change the
messages or encodings between the backend and UI, though use of XMLHttpRequest
caused a change to an asynchronous style of communication.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list