Chromium Code Reviews Chromium Code Reviews
Issue 10914218:
Removing references to legacy packaged apps across extension docs. (Closed)
Base URL: svn://svn.chromium.org/chrome/trunk/src| Index: chrome/common/extensions/docs/server2/templates/public/extensions/index.html |
| diff --git a/chrome/common/extensions/docs/server2/templates/public/extensions/index.html b/chrome/common/extensions/docs/server2/templates/public/extensions/index.html |
| index f7a0f843ff8ff142f70dfd48ea31015d631f2ed1..4c52bd0f2e5ee3495f4387dd4034e10928328888 100644 |
| --- a/chrome/common/extensions/docs/server2/templates/public/extensions/index.html |
| +++ b/chrome/common/extensions/docs/server2/templates/public/extensions/index.html |
| @@ -18,40 +18,22 @@ |
| can modify and enhance the functionality of the Chrome browser. |
| You write them using web technologies such as |
| HTML, JavaScript, and CSS. |
| - You can also use the extension system to build |
| - <a href="apps.html">packaged apps</a>, |
| - a downloadable kind of |
| - <a href="http://code.google.com/chrome/apps/index.html">installable web app</a>. |
| </p> |
| <p> |
| <img src="{{static}}/images/index/gmail-small.png" width="91" height="35" align="right" style="margin-top:0px; margin-left:0.5em" alt="A screenshot of an extension's icon in the browser bar"> |
| - From a user's point of view, |
| - extensions and packaged apps are very different |
| - because they present very different user interfaces. |
| Extensions have little to no user interface. |
| For example, the image to the right shows the icon |
| that provides the UI for the |
| <a href="samples.html#gmail">Gmail extension</a>. |
| </p> |
| <p> |
| - <img src="{{static}}/images/index/html5app.png" width="200" height="160" align="right" style="margin-top:0px; margin-left:0.5em" alt="A screenshot of a packaged app that implements a jigsaw puzzle"> |
|
Mihai Parparita -not on Chrome
2012/09/16 04:55:02
Another image that can be removed.
|
| - Packaged apps, on the other hand, |
| - look and feel like regular web apps, |
| - with a big-screen design |
| - and rich UI. |
| - The image to the right shows a jigsaw puzzle game |
| - implemented by a packaged app. |
| - </p> |
| - <p> |
| - Both extensions and packaged apps bundle all their files |
| + Extensions bundle all their files |
| into a single file that the user downloads and installs. |
| This bundling means that, unlike ordinary web apps, |
| - extensions and packaged apps don't need to depend |
| - on content from the web. |
| + extensions don't need to depend on content from the web. |
| </p> |
| <p> |
| - You can distribute your extension or packaged app |
| - by using the |
| + You can distribute your extension using the |
| <a href="https://chrome.google.com/webstore/developer/dashboard">Chrome Developer Dashboard</a> |
| to publish to the |
| <a href="http://chrome.google.com/webstore">Chrome Web Store</a>. |
| @@ -65,8 +47,6 @@ |
| <ol> |
| <li> |
| Follow the <a href="getstarted.html">Getting Started tutorial</a> |
| - <!-- PENDING: once we have one for packaged apps, change to |
| - "for _extensions_ or _packaged_apps_" --> |
| </li> |
| <li> |
| Read the |
