[Webkit-unassigned] [Bug 35340] [Qt] Enable alternate HTML/JavaScript front-ends for Web Inspector

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Mar 8 01:52:38 PST 2010


--- Comment #16 from Simon Hausmann <hausmann at webkit.org>  2010-03-08 01:52:38 PST ---
(In reply to comment #14)
> Simon,
> We are enabling remote usage of all the inspector functionality. I'm working on
> two such remote cases:
> 1) Using Web Inspector UI remoted over HTTP to enable on-device debug and
> profiling.
> 2) Implementing ChromeDevTools protocol for Eclipse or Aptana debug and
> profiling on-device
> The previous version of the patch extended the QWebInspector API but a
> discussion with laszlo and kenne on #qtwebkit led to this QWebSettings API. I
> have no particular preference between the two.

Ah, so when you bring up the inspector with a remote URL, do you actually use
any functionaliy of the inspector backend?

Do I understand correctly that the _use case_ behind this is that you have
WebKit running on a mobile platform, with the embedded web server enabled. Then
on your _desktop_ machine you take a QWebInspector, set the remote inspector
url to the address of the mobile device and fire up the inspector?

In that case, how much of QWebInspector is actually used? Or could you also
just point a QWebView to the remote url and it would work just as well?

Please elaborate and explain :), then it's easier for us to understand the API.

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