summaryrefslogtreecommitdiffstats
path: root/chrome/common/extensions
diff options
context:
space:
mode:
authorkathyw@chromium.org <kathyw@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-08-19 20:41:31 +0000
committerkathyw@chromium.org <kathyw@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-08-19 20:41:31 +0000
commit6187f2d174dc5f9f788e727fcdccd1277a5d82ff (patch)
tree7b2cd596f1772b0f0313e5485dda12f0f1bcb91e /chrome/common/extensions
parent0326752ddaebd5d2f3835c22839951d337f23923 (diff)
downloadchromium_src-6187f2d174dc5f9f788e727fcdccd1277a5d82ff.zip
chromium_src-6187f2d174dc5f9f788e727fcdccd1277a5d82ff.tar.gz
chromium_src-6187f2d174dc5f9f788e727fcdccd1277a5d82ff.tar.bz2
Miscellaneous changes, mostly related to the gallery.
BUG=none TEST=none Review URL: http://codereview.chromium.org/3186018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@56743 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/common/extensions')
-rw-r--r--chrome/common/extensions/docs/devguide.html2
-rw-r--r--chrome/common/extensions/docs/faq.html2
-rw-r--r--chrome/common/extensions/docs/getstarted.html2
-rw-r--r--chrome/common/extensions/docs/hosting.html36
-rw-r--r--chrome/common/extensions/docs/packaging.html2
-rw-r--r--chrome/common/extensions/docs/static/devguide.html2
-rw-r--r--chrome/common/extensions/docs/static/faq.html2
-rw-r--r--chrome/common/extensions/docs/static/getstarted.html2
-rw-r--r--chrome/common/extensions/docs/static/hosting.html34
-rw-r--r--chrome/common/extensions/docs/static/packaging.html2
-rw-r--r--chrome/common/extensions/docs/static/tut_debugging.html3
-rw-r--r--chrome/common/extensions/docs/tut_debugging.html3
12 files changed, 71 insertions, 21 deletions
diff --git a/chrome/common/extensions/docs/devguide.html b/chrome/common/extensions/docs/devguide.html
index 3407601..33f7127 100644
--- a/chrome/common/extensions/docs/devguide.html
+++ b/chrome/common/extensions/docs/devguide.html
@@ -404,7 +404,7 @@ and <a href="overview.html">Overview</a>.
</tr>
<tr>
<td> <a href="hosting.html">Hosting</a> </td>
- <td> Host extensions in the Extensions gallery or on your own servers </td>
+ <td> Host extensions in the Extensions Gallery or on your own servers </td>
</tr>
<tr>
<td> <a href="external_extensions.html">Other Deployment Options</a> </td>
diff --git a/chrome/common/extensions/docs/faq.html b/chrome/common/extensions/docs/faq.html
index 3d66bbc..fef29b6 100644
--- a/chrome/common/extensions/docs/faq.html
+++ b/chrome/common/extensions/docs/faq.html
@@ -417,7 +417,7 @@ try the
Yes, using the
<a href="http://code.google.com/chrome/extensions/trunk/npapi.html">NPAPI interface</a>.
Because of the possibility for abuse, though, we will review your extension
- before hosting it in the Google Chrome Extensions gallery.
+ before hosting it in the Google Chrome Extensions Gallery.
</p>
<h3 id="faq-dev-07">Can Google Chrome Extensions encode/decode JSON data?</h3>
diff --git a/chrome/common/extensions/docs/getstarted.html b/chrome/common/extensions/docs/getstarted.html
index 91413bb..1261ae8 100644
--- a/chrome/common/extensions/docs/getstarted.html
+++ b/chrome/common/extensions/docs/getstarted.html
@@ -363,6 +363,8 @@ to the toolbar of Google Chrome.
<img src="images/toolsmenu.gif" width="43" height="34" alt="" align="absmiddle" style="margin:0; padding:0">
(or the Window menu on Mac)
and choosing <b>Extensions</b>.
+ (If you're using version 6 or later,
+ choose <b>Tools &gt; Extensions</b>.)
</li>
<li>
diff --git a/chrome/common/extensions/docs/hosting.html b/chrome/common/extensions/docs/hosting.html
index 69a17ff..85f8834f 100644
--- a/chrome/common/extensions/docs/hosting.html
+++ b/chrome/common/extensions/docs/hosting.html
@@ -234,7 +234,7 @@
<h2>Contents</h2>
<ol>
<li>
- <a href="#gallery">Publishing to the Extensions gallery</a>
+ <a href="#gallery">Publishing to the Extensions Gallery</a>
<ol>
<li style="display: none; ">
<a>h3Name</a>
@@ -299,15 +299,37 @@
<div id="pageData-showTOC" class="pageData">true</div>
<p>
-Google provides a free hosting service: the
-<a href="http://chrome.google.com/extensions">Extensions gallery</a>.
-Another option is hosting your extension on other servers,
-instead of or in addition to using Google's gallery.
+Until the
+<a href="http://code.google.com/chrome/webstore/">Chrome Web Store</a>
+is available to the public,
+you can host your extension
+using the <a href="https://chrome.google.com/extensions">Extensions Gallery</a>.
+Once the store is public,
+the gallery's contents will be merged into the store.
+Another option
+is hosting your extension on other servers.
+</p>
+
+<p>
This page gives tips for using the gallery,
as well as details on how to host extensions on your own server.
</p>
-<h2 id="gallery">Publishing to the Extensions gallery</h2>
+<h2 id="gallery">Publishing to the Extensions Gallery</h2>
+
+<p>
+To publish extensions,
+you first need to pay a one-time
+<a href="http://blog.chromium.org/2010/08/security-improvements-and-registration.html">$5 developer registration fee</a>.
+</p>
+
+<p class="note">
+<b>Note:</b>
+If you used the Chrome Developer Dashboard before
+the first developer preview release of the Chrome Web Store —
+to publish an extension, for example —
+you don't need to pay the fee.
+</p>
<p>
Publishing to the gallery is easy,
@@ -317,7 +339,7 @@ if you take a little time to prepare:
<ul>
<li> Visit the
- <a href="http://chrome.google.com/extensions">gallery</a>
+ <a href="https://chrome.google.com/extensions">gallery</a>
and look at similar extensions' pages.
Your extension's page should look at least as good as theirs. </li>
<li> Consider creating a support site for your extension,
diff --git a/chrome/common/extensions/docs/packaging.html b/chrome/common/extensions/docs/packaging.html
index 740ca76..d691f93 100644
--- a/chrome/common/extensions/docs/packaging.html
+++ b/chrome/common/extensions/docs/packaging.html
@@ -391,7 +391,7 @@ You'll need it later if you want to do any of the following:
<ul>
<li><a href="#update">Update</a> the extension</li>
<li>Upload the extension to the
-<a href="https://chrome.google.com/extensions">extensions gallery</a> </li>
+<a href="https://chrome.google.com/extensions">Extensions Gallery</a> </li>
</ul>
<p>
diff --git a/chrome/common/extensions/docs/static/devguide.html b/chrome/common/extensions/docs/static/devguide.html
index d9189e4..6b76694 100644
--- a/chrome/common/extensions/docs/static/devguide.html
+++ b/chrome/common/extensions/docs/static/devguide.html
@@ -114,7 +114,7 @@ and <a href="overview.html">Overview</a>.
</tr>
<tr>
<td> <a href="hosting.html">Hosting</a> </td>
- <td> Host extensions in the Extensions gallery or on your own servers </td>
+ <td> Host extensions in the Extensions Gallery or on your own servers </td>
</tr>
<tr>
<td> <a href="external_extensions.html">Other Deployment Options</a> </td>
diff --git a/chrome/common/extensions/docs/static/faq.html b/chrome/common/extensions/docs/static/faq.html
index 280b5ef..76b6c9c 100644
--- a/chrome/common/extensions/docs/static/faq.html
+++ b/chrome/common/extensions/docs/static/faq.html
@@ -127,7 +127,7 @@ try the
Yes, using the
<a href="http://code.google.com/chrome/extensions/trunk/npapi.html">NPAPI interface</a>.
Because of the possibility for abuse, though, we will review your extension
- before hosting it in the Google Chrome Extensions gallery.
+ before hosting it in the Google Chrome Extensions Gallery.
</p>
<h3 id="faq-dev-07">Can Google Chrome Extensions encode/decode JSON data?</h3>
diff --git a/chrome/common/extensions/docs/static/getstarted.html b/chrome/common/extensions/docs/static/getstarted.html
index f0aa1131..497652c 100644
--- a/chrome/common/extensions/docs/static/getstarted.html
+++ b/chrome/common/extensions/docs/static/getstarted.html
@@ -66,6 +66,8 @@ to the toolbar of Google Chrome.
align="absmiddle" style="margin:0; padding:0">
(or the Window menu on Mac)
and choosing <b>Extensions</b>.
+ (If you're using version 6 or later,
+ choose <b>Tools > Extensions</b>.)
</li>
<li>
diff --git a/chrome/common/extensions/docs/static/hosting.html b/chrome/common/extensions/docs/static/hosting.html
index b12c8c9..cacd261 100644
--- a/chrome/common/extensions/docs/static/hosting.html
+++ b/chrome/common/extensions/docs/static/hosting.html
@@ -2,15 +2,37 @@
<div id="pageData-showTOC" class="pageData">true</div>
<p>
-Google provides a free hosting service: the
-<a href="http://chrome.google.com/extensions">Extensions gallery</a>.
-Another option is hosting your extension on other servers,
-instead of or in addition to using Google's gallery.
+Until the
+<a href="http://code.google.com/chrome/webstore/">Chrome Web Store</a>
+is available to the public,
+you can host your extension
+using the <a href="https://chrome.google.com/extensions">Extensions Gallery</a>.
+Once the store is public,
+the gallery's contents will be merged into the store.
+Another option
+is hosting your extension on other servers.
+</p>
+
+<p>
This page gives tips for using the gallery,
as well as details on how to host extensions on your own server.
</p>
-<h2 id="gallery">Publishing to the Extensions gallery</h2>
+<h2 id="gallery">Publishing to the Extensions Gallery</h2>
+
+<p>
+To publish extensions,
+you first need to pay a one-time
+<a href="http://blog.chromium.org/2010/08/security-improvements-and-registration.html">$5 developer registration fee</a>.
+</p>
+
+<p class="note">
+<b>Note:</b>
+If you used the Chrome Developer Dashboard before
+the first developer preview release of the Chrome Web Store &mdash;
+to publish an extension, for example &mdash;
+you don't need to pay the fee.
+</p>
<p>
Publishing to the gallery is easy,
@@ -20,7 +42,7 @@ if you take a little time to prepare:
<ul>
<li> Visit the
- <a href="http://chrome.google.com/extensions">gallery</a>
+ <a href="https://chrome.google.com/extensions">gallery</a>
and look at similar extensions' pages.
Your extension's page should look at least as good as theirs. </li>
<li> Consider creating a support site for your extension,
diff --git a/chrome/common/extensions/docs/static/packaging.html b/chrome/common/extensions/docs/static/packaging.html
index b929cac..93cc4d5 100644
--- a/chrome/common/extensions/docs/static/packaging.html
+++ b/chrome/common/extensions/docs/static/packaging.html
@@ -80,7 +80,7 @@ You'll need it later if you want to do any of the following:
<ul>
<li><a href="#update">Update</a> the extension</li>
<li>Upload the extension to the
-<a href="https://chrome.google.com/extensions">extensions gallery</a> </li>
+<a href="https://chrome.google.com/extensions">Extensions Gallery</a> </li>
</ul>
<p>
diff --git a/chrome/common/extensions/docs/static/tut_debugging.html b/chrome/common/extensions/docs/static/tut_debugging.html
index de4053b..1c5db982 100644
--- a/chrome/common/extensions/docs/static/tut_debugging.html
+++ b/chrome/common/extensions/docs/static/tut_debugging.html
@@ -246,7 +246,8 @@ here are suggestions for what to do next:
Example: <code>console.log("Hello, world!")</code>
</li>
<li>
- Explore the
+ Follow the <a href="http://www.chromium.org/devtools/google-chrome-developer-tools-tutorial">Developer Tools tutorial</a>,
+ explore the
<a href="http://www.chromium.org/devtools">Developer Tools site</a>,
and watch some video tutorials.
</li>
diff --git a/chrome/common/extensions/docs/tut_debugging.html b/chrome/common/extensions/docs/tut_debugging.html
index cf716a7..2a52942 100644
--- a/chrome/common/extensions/docs/tut_debugging.html
+++ b/chrome/common/extensions/docs/tut_debugging.html
@@ -548,7 +548,8 @@ here are suggestions for what to do next:
Example: <code>console.log("Hello, world!")</code>
</li>
<li>
- Explore the
+ Follow the <a href="http://www.chromium.org/devtools/google-chrome-developer-tools-tutorial">Developer Tools tutorial</a>,
+ explore the
<a href="http://www.chromium.org/devtools">Developer Tools site</a>,
and watch some video tutorials.
</li>