Added devtools.console.* and resource-related calls in inspectedWindow

Added devtools.console.* and resource-related calls in inspectedWindow

- added chrome.experimental.devtools.console.*
- added getResources(), onResourceAdded event and Resource type in
    chrome.experimental.devtools.inspectedWindow

BUG=none
TEST=none

[caseq1, 2011-09-19 14:58:20]

Live version:
http://www.corp.google.com/~caseq/devtoolsext/docs/experimental.devtools.html

[kathyw, 2011-09-19 16:28:28]

A few small issues.

http://codereview.chromium.org/7941001/diff/1/chrome/common/extensions/api/de...
File chrome/common/extensions/api/devtools_api.json (right):

http://codereview.chromium.org/7941001/diff/1/chrome/common/extensions/api/de...
chrome/common/extensions/api/devtools_api.json:12: "description": "An URL of the
resource."
An URL -> "A URL" or "The URL"

http://codereview.chromium.org/7941001/diff/1/chrome/common/extensions/api/de...
chrome/common/extensions/api/devtools_api.json:64: "description": "Set to
undefined if the operation completed succuessfully, describes error otherwise."
succuessfully -> successfully

http://codereview.chromium.org/7941001/diff/1/chrome/common/extensions/api/de...
chrome/common/extensions/api/devtools_api.json:434: "description": "Adds a
message to console.",
to -> to the

http://codereview.chromium.org/7941001/diff/1/chrome/common/extensions/api/de...
chrome/common/extensions/api/devtools_api.json:453: "description": "Text of the
console message, as represented by the first argument to the console.log() or a
similar method (no parameter substitution  performed)."
Text -> The text

http://codereview.chromium.org/7941001/diff/1/chrome/common/extensions/api/de...
chrome/common/extensions/api/devtools_api.json:458: "description": "A URL of the
script that originated the message, if available."
A URL -> The URL?

or maybe "A URL that identifies the script..."

http://codereview.chromium.org/7941001/diff/1/chrome/common/extensions/api/de...
chrome/common/extensions/api/devtools_api.json:461: "type": "numer",
numer -> number?

http://codereview.chromium.org/7941001/diff/1/chrome/common/extensions/api/de...
chrome/common/extensions/api/devtools_api.json:463: "description": "A line
number within the script that originated the message, if available."
A line number -> The line number? or "A relevant line number"?

Should the line number be the one that originated the message? Or is the fact
that the script generated the message the important thing? If the former, maybe:

The line number (within the script) where the message originated, if available.

http://codereview.chromium.org/7941001/diff/1/chrome/common/extensions/docs/s...
File chrome/common/extensions/docs/static/experimental.devtools.console.html
(right):

http://codereview.chromium.org/7941001/diff/1/chrome/common/extensions/docs/s...
chrome/common/extensions/docs/static/experimental.devtools.console.html:6: the
inspected page console and post messages there: <code>getMessages()</code>
there: -> there.

http://codereview.chromium.org/7941001/diff/1/chrome/common/extensions/docs/s...
chrome/common/extensions/docs/static/experimental.devtools.console.html:6: the
inspected page console and post messages there: <code>getMessages()</code>
No getMessages() method is documented in this page.

http://codereview.chromium.org/7941001/diff/1/chrome/common/extensions/docs/s...
chrome/common/extensions/docs/static/experimental.devtools.console.html:7:
returns the list of messages on the console, <code>onConsoleMessageAdded</code>
onConsoleMessageAdded -> onMessageAdded

http://codereview.chromium.org/7941001/diff/1/chrome/common/extensions/docs/s...
chrome/common/extensions/docs/static/experimental.devtools.console.html:9:
>addConsoleMessages()</code> allows an extension to add new messages.
No addConsoleMessages method is documented in this page. Do you mean addMessage?

[caseq, 2011-09-20 20:07:26]

On 2011/09/19 16:28:28, kathyw wrote:
> A few small issues.

Thanks for the quick review and sorry for a messy change.
Fixed everything.

> "A line
> number within the script that originated the message, if available."
> A line number -> The line number? or "A relevant line number"?
> 
> Should the line number be the one that originated the message? Or is the fact
> that the script generated the message the important thing? If the former,
maybe:
> 
> The line number (within the script) where the message originated, if
available.

If the line is there, the messages is always coming from a script, so I think we
can just not mention script altogether. Changed this to "The number of the line
where the message originated, if available.".

[kathyw, 2011-09-20 20:24:46]

One little issue in the console description. Otherwise, LGTM.

http://codereview.chromium.org/7941001/diff/7001/chrome/common/extensions/doc...
File chrome/common/extensions/docs/static/experimental.devtools.console.html
(right):

http://codereview.chromium.org/7941001/diff/7001/chrome/common/extensions/doc...
chrome/common/extensions/docs/static/experimental.devtools.console.html:8: event
provides notifications on new messages and <code>addMessages()</code>
addMessages -> addMessage?

Also, we usually use a terminal comma, which means
"new messages and" -> "new messages, and".

(It's correct either way, but it's good to be consistent.)

[caseq, 2011-09-21 08:47:50]

On 2011/09/20 20:24:46, kathyw wrote:
> One little issue in the console description. Otherwise, LGTM.

Thanks, fixed both and landed as r102089.