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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Feb 17 00:22:59 PST 2010


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


Pavel Feldman <pfeldman at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #48854|                            |review-
               Flag|                            |




--- Comment #1 from Pavel Feldman <pfeldman at chromium.org>  2010-02-17 00:22:59 PST ---
(From update of attachment 48854)
Jamey, there is already work in progress on this one. Let me provide you with
some context:

Chromium is already using a custom front-end that is backed with the
out-of-process implementation. The way it is achieved is that
setFrontendProxyObject is being called and it injects a special js object that
is sending information over the wire. So technically it is possible and there
is a working product using this approach. It was myself to serialize all the
inspector interaction, extract InspectorFrontend abstraction, re-work large
chunks of the front-end to allow only asynchronous operations between the two.
So we (chrome dev tools authors) have been continuously working on achieving
this goal for half a year or so. Some of our work is still in progress (such as
splitting InspectorClient into InspectorClient and InspectorFrontendClient)
since these parities are potentially operating in different processes (on
different devices).

Our present plan in fact is to allow remote debugging of the device using
existing front-end, it is ourselves developing Eclipse Chrome Debugger you are
talking about, we have some plans on merging the protocols there (it currently
only supports v8 raw debugging protocol). Sounds familiar?

Anyways, I would encourage you to start with a design doc in this bug and sync
up with pfeldman at chromium.org and yurys at chromium.org before you start sending
patches. We are both working on Chromium Dev Tools from St.Petersburg (similar
TZ as you?), so we should be able to sync up with no problem. If you can spend
some cycles on this, it would be great. We have a lot of work. I can see that
you are already familiar with the code, so your help would be greatly
appreciated!

-- 
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