Summary: | Web Inspector: Remote debugging meta-bug | ||
---|---|---|---|
Product: | WebKit | Reporter: | Pavel Feldman <pfeldman> |
Component: | Web Inspector (Deprecated) | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED INVALID | ||
Severity: | Normal | CC: | bweinstein, eostroukhov, joepeck, keishi, loislo, pfeldman, pmuellr, rik, sroussey, yurys |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | All | ||
OS: | All |
Description
Pavel Feldman
2010-08-09 11:12:17 PDT
> - We change the JSON message format a bit, leaving existing semantics of messages > in place. Following draft should give a good idea on the message format: > https://docs.google.com/document/edit?id=1d_N-OIb3UztuC-_g0piXsIIdp89HnMcDk-uSQ8uamW4&hl=en&authkey=CIf48O4J Very useful, thanks for putting this together. > - Approach described above might be sufficient for some domains (cookies, appcache). But there are more > complex domains such as 'dom' that maintain heavy state. For these, I'd suggest implementing an 'SDK' that > would maintain model consistency and encapsulate backend interaction. In dom case, DOMAgent is pretty > much covering it, but needs to brushed up a bit. It no longer needs to mimic DOM interface, enulate DOMWindow > and such. > > - Over time, we could deliver these SDKs to the remote debugging clients and hence allow alternate front-ends. > As a result, we will need to maintain JavaScript SDK conformance instead of the protocol conformance. Just as > we do with Eclipse Debugger for Chrome. I think that is a good idea. Its much easier to maintain a few method names and their parameters, then maintain an "old" and "new" protocol if it ever changes. Reference interface for such an SDK (work in progress for use in Firebug and Eclipse): http://code.google.com/p/fbug/source/browse/branches/firebug1.7#firebug1.7/content/firebug/interface Closing as invalid, as this bug pertains to the old inspector UI and/or its tests. Please file a new bug (https://www.webkit.org/new-inspector-bug) if the bug/feature/issue is still relevant to WebKit trunk. |