[Webkit-unassigned] [Bug 24273] Inspector Plugins or Extend Capability

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Sep 1 05:41:40 PDT 2009


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





--- Comment #3 from Patrick Mueller <pmuellr at yahoo.com>  2009-09-01 05:41:40 PDT ---
Some more thinking on this.  Again, related to localStorage.  (note: there used
to be a "settings" facility available on InspectorController, on the JS side,
which is now gone).

The idea is to create a new debugger command called "!settings", or some such. 
Think "defauilts" on the Mac command-line.  This would be a general purpose
facility to provide a read/write store for settings for Inspector related
things.

Next, have a setting called "userScript".  If set, this would be considered a
file name, and at the end of inspector.js we'd dynamically add a new <script>
element to the inspector's main document with that file.

The story would then be something like this:

- develop your extension in a .js file somewhere on your local file system
- while in Inspector, at the command console prompt, run
   !settings set userScript /users/foo/myExtension/main.js
- next time Inspector loads, that script will load at the end, via the
dynamically inserted <script> element
- to "turn the extension off", run
   !settings delete userScript

Lots of issues here, but would be a way to get started playing with the concept
of extending the Inspector, inexpensively.

-- 
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