Bug 109922

Summary: [WK2] Expose WebInspectorServer through the C API
Product: WebKit Reporter: Jocelyn Turcotte <jturcotte>
Component: New BugsAssignee: Jocelyn Turcotte <jturcotte>
Status: RESOLVED WONTFIX    
Severity: Normal CC: benjamin, hausmann, joepeck, jturcotte, sam
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on: 108475, 109921    
Bug Blocks:    
Attachments:
Description Flags
Patch none

Jocelyn Turcotte
Reported 2013-02-15 04:01:46 PST
[WK2] Expose WebInspectorServer through the C API
Attachments
Patch (14.77 KB, patch)
2013-02-15 04:03 PST, Jocelyn Turcotte 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Jocelyn Turcotte
Comment 1 2013-02-15 04:03:26 PST
Created attachment 188531 [details] Patch
Jocelyn Turcotte
Comment 2 2013-02-15 04:10:04 PST
Comment about the approach: This seems like the most straightforward and clean thing to do if we want to avoid knowing about WebContext at all in higher layers. Tell me if you see a better way to deal with it. Other options that I see: - Have this exposed in each port's C API directory - Have a WKInspectorServerPrivate.h instead - Keep the WebInspectorServer a singleton (abadonning bug 109921) and expose a port-specific / private that boots the global server instance without any reference to WKContext
Jocelyn Turcotte
Comment 3 2013-02-19 07:32:30 PST
Benjamin or Sam, would you have any opinion about the API part? See comment #2.
Jocelyn Turcotte
Comment 4 2013-03-13 06:51:35 PDT
Comment on attachment 188531 [details] Patch This kind of API would only make sense if more than Qt would use it, and since GTK and EFL expose the C API directly to the applications it wouldn't be possible to keep the current behavior. Abandonning in favor of bug #112254.
Note You need to log in before you can comment on or make changes to this bug.