From d40f3747b418e94e0c416fbfc9adc9be510593ed Mon Sep 17 00:00:00 2001 From: "kathyw@google.com" Date: Mon, 31 Aug 2009 23:45:23 +0000 Subject: Miscellaneous doc cleanup. TBR=aa Review URL: http://codereview.chromium.org/175039 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@24973 0039d316-1c4b-4281-b951-d872f2087c98 --- .../common/extensions/docs/static/bookmarks.html | 36 ++++++++++++++++------ .../common/extensions/docs/static/getstarted.html | 2 +- chrome/common/extensions/docs/static/index.html | 2 +- chrome/common/extensions/docs/static/overview.html | 10 +----- 4 files changed, 29 insertions(+), 21 deletions(-) diff --git a/chrome/common/extensions/docs/static/bookmarks.html b/chrome/common/extensions/docs/static/bookmarks.html index bf613fd..f03c7c2 100755 --- a/chrome/common/extensions/docs/static/bookmarks.html +++ b/chrome/common/extensions/docs/static/bookmarks.html @@ -2,18 +2,21 @@

-Use the chrome.bookmarks API to create, organize, and otherwise manipulate bookmarks. +Use the chrome.bookmarks API to create, organize, +and otherwise manipulate bookmarks.

Description

-

-[PENDING: intro goes here...] +

+[PENDING: This section needs to be reviewed and updated.]

-Bookmark objects are an important part of the chrome.bookmarks API. -Each bookmark object represents either a URL or a group of bookmarks, as you can see in the following figure. +BookmarkTreeNode objects +are an important part of the chrome.bookmarks API. +Each bookmark tree node represents +either a URL or a group of bookmarks, as you can see in the following figure.

+
+ +[PENDING: this figure needs to be updated] +

Properties

-

Objects that represent bookmarks can have the following properties: +

+Objects that represent bookmarks can have the following properties:

id
An integer ID that's unique for each bookmark. Don't save this ID in persistent storage; - the ID for a particular bookmark might change the next time the browser is started. + the ID for a particular bookmark might change + the next time the browser is started. + + [PENDING: these might be persistent now] +
title
@@ -54,6 +66,8 @@ Each bookmark object represents either a URL or a group of bookmarks, as you can (omitted for groups)
The URL of the page that the bookmark points to.
+ +
...

Examples

@@ -113,13 +127,15 @@ Here's how those bookmarks might be represented with bookmark objects:

Here's some code you could use to create that hierarchy:

-
-...code goes here...
+
+[PENDING: ...code goes here...]
 
+ + +--> diff --git a/chrome/common/extensions/docs/static/getstarted.html b/chrome/common/extensions/docs/static/getstarted.html index 381eacf..e733c67 100755 --- a/chrome/common/extensions/docs/static/getstarted.html +++ b/chrome/common/extensions/docs/static/getstarted.html @@ -181,7 +181,7 @@ and where to find more information.]

  • Learn more about - toolstrips + toolstrips
  • Package diff --git a/chrome/common/extensions/docs/static/index.html b/chrome/common/extensions/docs/static/index.html index 70cdebb..db900d9 100755 --- a/chrome/common/extensions/docs/static/index.html +++ b/chrome/common/extensions/docs/static/index.html @@ -76,7 +76,7 @@ Start with one of these sections: Google Chrome's extension system.
  • - Developer's Guide: + Developer's Guide: Get detailed information on using each feature and API.
  • diff --git a/chrome/common/extensions/docs/static/overview.html b/chrome/common/extensions/docs/static/overview.html index 277c5c6..70c368c 100755 --- a/chrome/common/extensions/docs/static/overview.html +++ b/chrome/common/extensions/docs/static/overview.html @@ -105,14 +105,6 @@ under the extension's top directory; it's the same as the relative URL.

    -

    -[QUESTION TO REVIEWERS: Is this section too big/detailed? -It seems a little weird to mention absolute URLs with mentioning getURL -and when you'd need it. -What's the motivation for covering absolute URLs? -Is the debugger the place you're most likely to see them?] -

    -

    For example, assume your extension has the ID aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa @@ -315,7 +307,7 @@ Two kinds of communication happen within an extension: Communication between content scripts and the extension.
    For example, - [PENDING: example goes here]. + [PENDING: typical use case goes here]. See Content Scripts for information about this type of communication. -- cgit v1.1