[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 #13 from Jamey Hicks <jamey.hicks at nokia.com>  2010-02-17 13:22:52 PST ---
(In reply to comment #11)
> (In reply to comment #8)
> > Created an attachment (id=48923)
 --> (https://bugs.webkit.org/attachment.cgi?id=48923) [details] [details]
> > Web Inspector architecture with patch 48854 applied
> > 
> > Shows subclassing of InspectorFrontend for the direct communication path into
> > the ScriptState of the Web Inspector UI Page.
> 
> I can see the subclassing, but that's not really what you want. All inspector
> frontend methods are dispatched into the "dispatch" script function calls with
> script value parameters. All that you need is to be able to use your
> ScriptFunctionCall that would serialize parameters. There already is a perfect
> tool for serializing ScriptValues that is JSON. So you don't really need any
> subclassing, just parametrized proxy object or pluggable ScriptFunctionCall
> version.

Just to make sure I understand what you are suggesting. You are saying that it
is OK to provide alternate implementations of the interface provided by the
script proxy object or by providing alternate implementations of
ScriptFunctionCall. 

The former implies that the communication channel to the UI needs to be
implemented in Javascript by a script proxy object that implements the same
interface as WebInspector from WebCore/inspector/front-end/inspector.js.

The latter (subclassing ScriptFunctionCall) seems like a bigger change to
WebCore but enables more choice of implementation language for the debugger
communication protocol. But I can envision how to make this work.

I'm a little curious why the designated externizable inspector API is one that
doesn't have any declaration apart from its implementation, rather than one of
the ones defined in a C++ header file or a .idl file.

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