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

[bugzilla-daemon at webkit.org]

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





--- Comment #4 from Pavel Feldman <pfeldman at chromium.org>  2010-02-17 06:20:49 PST ---
(In reply to comment #3)
> I'll add a design document. We discussed implementing the debug agent /
> protocol adapter in Javascript, but it seemed cleaner to stick to a native
> implementation.
>

It does not seem cleaner to me and here is why. We'd like to define a protocol
for the interaction between the backend and the front-end. This protocol is
likely to use JSON for the message content. Today WebCore contains both backend
and the front-end pieces and defines the interchange "API". We'd like to leave
specifics to the WebCore and make inspector clients/hosts serve
backend-frontend transport needs only without cracking the messages.

Today, InspectorFrontend is a guy sitting on the backend side that is
serializing messages for the front-end into the standard protocol format. It
does not make much sense to make it pluggable since its responsibility is very
narrow. What you need is to take these JSON messages and send them over the
pipe. That's basically a reason for r-.

> I am in favor of cleaning up Web Inspector's backend interface so that it would
> be easier to support different debuggers, including:
> 1) Web Inspector in-process
> 2) Web Inspector remote (e.g., via HTTP)

(1) and (2) is our goal as well as mentioned in my previous message.

> 3) Chrome Dev Tools protocol (with V8 debug)

This one is not clear to me. We are currently changing v8 debugger and profiler
so that it conformed same apis as in (1) and (2). See ScriptProfiler /
ScriptDebugger classes that are being added in bindings.

> 4) Aptana via Chrome Dev Tools protocol

We are thinking of switching from Chrome Dev Tools protocol to the same
protocol as in (1), (2) and (3) in Eclipse SDK when protocol is mature enough.

> 5) Dreamweaver
> 

Please explain what exactly you are suggesting here.

> I have a prototype of Web Inspector remoted via HTTP using Qt/Webkit 4.6. I
> would be happy to post that patch.
>

That's great!

> I have the beginnings of Chrome Dev Tools protocol with the V8 debugger
> protocol. You can attach the debugger, set and clear breakpoints, and I am
> working on the backtrace command. It is a work in progress, but I would be
> happy to attach that patch as well.

It is not clear why you need this one. Could you please describe the scenario?

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