Chromium Code Reviews Chromium Code Reviews
Issue 912633002:
NaCl docs: clarify Chrome apps instead of packaged apps (Closed)
Base URL: https://chromium.googlesource.com/chromium/src.git@master| OLD | NEW |
|---|---|
| 1 .. _devcycle-running: | 1 .. _devcycle-running: |
| 2 | 2 |
| 3 ####### | 3 ####### |
| 4 Running | 4 Running |
| 5 ####### | 5 ####### |
| 6 | 6 |
| 7 | 7 |
| 8 .. contents:: | 8 .. contents:: |
| 9 :local: | 9 :local: |
| 10 :backlinks: none | 10 :backlinks: none |
| (...skipping 25 matching lines...) Expand all Loading... | |
| 36 | 36 |
| 37 Native Client applications and the Chrome Web Store | 37 Native Client applications and the Chrome Web Store |
| 38 =================================================== | 38 =================================================== |
| 39 | 39 |
| 40 Before reading about how to run Native Client applications, it's important to | 40 Before reading about how to run Native Client applications, it's important to |
| 41 understand a little bit about how Native Client applications are distributed. | 41 understand a little bit about how Native Client applications are distributed. |
| 42 As explained in :doc:`Distributing Your Application <../distributing>`, Native | 42 As explained in :doc:`Distributing Your Application <../distributing>`, Native |
| 43 Client applications must currently be distributed through the **Chrome Web | 43 Client applications must currently be distributed through the **Chrome Web |
| 44 Store (CWS)**. Applications in the CWS are one of three types: | 44 Store (CWS)**. Applications in the CWS are one of three types: |
| 45 | 45 |
| 46 * A **hosted application** is an application that you host on a server of your | 46 * A **hosted application** is an application that you host on a server of your |
|
binji
2015/02/10 17:49:40
same here
| |
| 47 choice. To distribute an application as a hosted application, you upload | 47 choice. To distribute an application as a hosted application, you upload |
| 48 application metadata to the CWS. | 48 application metadata to the CWS. Learn more on the `Chrome App </apps>`_ |
| 49 documentation page. | |
| 49 | 50 |
| 50 * A **packaged application** is an application that is hosted in the CWS and | 51 * A **packaged application** is an application that is hosted in the CWS and |
| 51 downloaded to the user's machine. To distribute an application as a packaged | 52 downloaded to the user's machine. To distribute an application as a packaged |
| 52 application, you upload the entire application, including all application | 53 application, you upload the entire application, including all application |
| 53 assets and metadata, to the CWS. | 54 assets and metadata, to the CWS. Learn more on the `Chrome App </apps>`_ |
| 55 documentation page. | |
| 54 | 56 |
| 55 * An **extension** is a packaged application that has a tiny UI component | 57 * An **extension** is a packaged application that has a tiny UI component |
| 56 (extensions are typically used to extend the functionality of the Chrome | 58 (extensions are typically used to extend the functionality of the Chrome |
| 57 browser). To distribute an application as an extension, you upload the entire | 59 browser). To distribute an application as an extension, you upload the entire |
| 58 application, including all application assets and metadata, to the CWS. | 60 application, including all application assets and metadata, to the CWS. Learn |
| 61 more on the `Chrome extensions </extensions>`_ documentation page. | |
| 59 | 62 |
| 60 It's clearly not convenient to package and upload files to the Chrome Web Store | 63 It's clearly not convenient to package and upload files to the Chrome Web Store |
| 61 every time you want to run a new build of your application, but there are four | 64 every time you want to run a new build of your application, but there are four |
| 62 alternative techniques you can use to run the application during development. | 65 alternative techniques you can use to run the application during development. |
| 63 These techniques are listed in the following table and described in detail | 66 These techniques are listed in the following table and described in detail |
| 64 below. Each technique has certain requirements (NaCl flag, web server, and/or | 67 below. Each technique has certain requirements (NaCl flag, web server, and/or |
| 65 CWS metadata); these are explained in the :ref:`Requirements <requirements>` | 68 CWS metadata); these are explained in the :ref:`Requirements <requirements>` |
| 66 section below. | 69 section below. |
| 67 | 70 |
| 68 | 71 |
| (...skipping 402 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
| 471 be able to find the application by searching in the CWS. | 474 be able to find the application by searching in the CWS. |
| 472 | 475 |
| 473 To publish an application to the world after publishing it to test accounts, | 476 To publish an application to the world after publishing it to test accounts, |
| 474 you must first unpublish the application. For additional information see | 477 you must first unpublish the application. For additional information see |
| 475 `Publishing Your App </webstore/docs/publish>`_, and in particular `Publishing | 478 `Publishing Your App </webstore/docs/publish>`_, and in particular `Publishing |
| 476 to test accounts </webstore/publish#testaccounts>`_. | 479 to test accounts </webstore/publish#testaccounts>`_. |
| 477 | 480 |
| 478 .. |menu-icon| image:: /images/menu-icon.png | 481 .. |menu-icon| image:: /images/menu-icon.png |
| 479 .. |extensions| image:: /images/extensions-management.png | 482 .. |extensions| image:: /images/extensions-management.png |
| 480 .. |new-tab-apps| image:: /images/new-tab-apps.png | 483 .. |new-tab-apps| image:: /images/new-tab-apps.png |
| OLD | NEW |
