[Webkit-unassigned] [Bug 27541] Web Inspector: Split InspectorController into InspectorController and InspectorBackend

[bugzilla-daemon at webkit.org]

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





--- Comment #3 from Pavel Feldman <pfeldman at chromium.org>  2009-07-22 14:04:11 PDT ---
(In reply to comment #2)
> Sounds good.  I haven't quite figured out where the C++ code calls into
> front-end JS (haven't really looked, actually); or maybe it really doesn't at
> all or not much.  But it would be nice to have this information as well.
> 

it is all going though the InspectorFrontend interface. See calls to m_frontend
in InspectorController.

> I have this dream of being able to take the current js/html/css/images out of
> front-end, and running them in a actual browser, plugging the back-end with
> something else.  
> 

This is working with some limitations in Chromium. There is an
InspectorController stub implementation written in JS code that handles most of
the calls and makes front-end self-contained web app. Exceptions are calls to
the host such as addSourceToFrame since they actually manipulate WebCore API.
Here is a link:
http://src.chromium.org/viewvc/chrome/trunk/src/webkit/glue/devtools/js/inspector_controller.js?revision=20751&view=markup

> In addition to, or as part of that dream, folks seem to be starting to ask
> about remote debugging, and having a clear contract between the UI and the
> backend would be very helpful.

Current plan is to serialize inspector controller frontend / backend
interaction, so this should be possible. However, when talking about remote
debugging, we should consider protocols such as
http://my.opera.com/dragonfly/blog/scope-protocol-specification or similar.

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