native_client_sdk/src/doc/devguide/devcycle/running.rst - Issue 511963004: Rearrange tables so that navigation can be added back to certain pages.

Unified Diff: native_client_sdk/src/doc/devguide/devcycle/running.rst

Issue 511963004: Rearrange tables so that navigation can be added back to certain pages. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: Add numbers to techniques table to correspond to later headings. Created 6 years, 3 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Download patch

« native_client_sdk/doc_generated/devguide/devcycle/dynamic-loading.html ('K') | « native_client_sdk/src/doc/devguide/devcycle/dynamic-loading.rst ('k') | native_client_sdk/src/doc/devguide/devcycle/vs-addin.rst » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: native_client_sdk/src/doc/devguide/devcycle/running.rst

diff --git a/native_client_sdk/src/doc/devguide/devcycle/running.rst b/native_client_sdk/src/doc/devguide/devcycle/running.rst

index a411235be3f9794d4494013ab3f66f7e4556c012..33944947330d92bcd001109cf99e34768da13b81 100644

--- a/native_client_sdk/src/doc/devguide/devcycle/running.rst

+++ b/native_client_sdk/src/doc/devguide/devcycle/running.rst

@@ -1,7 +1,5 @@

.. _devcycle-running:

-:template: standard_nacl_api

#######

Running

#######

@@ -67,49 +65,57 @@ below. Each technique has certain requirements (NaCl flag, web server, and/or

CWS metadata); these are explained in the :ref:`Requirements <requirements>`

section below.

-.. list-table::

- :header-rows: 1

- * - #

- - Technique

- - Requires NaCl flag

- - Requires Web Server

- - Requires CWS Metadata

- - Description

- * - 1

- - Local server

- - |CHK|

- -

- - Run a local server and simply point your browser to your application on

- the server.

- * - 2

- - Packaged application loaded as an unpacked extension

- -

- - |CHK|

- - Load your packaged application into Chrome as an unpacked extension and

- run it without a server. An unpacked extension is simply an application

- whose source and metadata files are located in a plain (unzipped) folder

- on your development machine. The CWS manifest file (explained below) must

- specify a ``local_path`` field.

- * - 3

- - Hosted application loaded as an unpacked extension

- -

- - |CHK|

- - Load your hosted application into Chrome as an unpacked extension and run

- it from a server (which can be a local server). The CWS manifest file

- must specify a ``web_url`` field.

- * - 4

- - CWS application with untrusted testers

- -

- - |CHK|

- - This is the standard technique for distributing a packaged or hosted

- application in the CWS, but you can limit the application to a few

- trusted testers. This technique requires a server if your application is

- a hosted application.

++--------------------------------------------------------+----------+----------+

+| Technique | Requires | Requires |

+| | Web | CWS |

+| | Server | Metadata |

++========================================================+==========+==========+

+|**1. Local server** | |CHK| | |

+| | | |

+| .. | | |

+| | | |

+| Run a local server and simply point your browser to | | |

+| your application on the server. | | |

+| | | |

+| .. Note:: | | |

+| :class: note | | |

+| | | |

+| This technique requires the NaCl flag. | | |

++---------------------------------------------+----------+----------+----------+

+|**2. Packaged application loaded as an unpacked | | |CHK| |

+|extension** | | |

+| | | |

+| .. | | |

+| | | |

+| Load your packaged application into Chrome as an | | |

+| unpacked extension and run it without a server. An | | |

+| unpacked extension is an application whose source and | | |

+| metadata files are located in an unzipped folder on | | |

+| your development machine. The CWS manifest file | | |

+| (explained below) must specify a local_path field. | | |

++--------------------------------------------------------+----------+----------+

+|**3. Hosted application loaded as an unpacked | |CHK| | |CHK| |

+|extension** | | |

+| | | |

+| .. | | |

+| | | |

+| Load your hosted application into Chrome as an | | |

+| unpacked extension and run it from a server (which can| | |

+| be a local server). The CWS manifest file must specify| | |

+| a web_url field. | | |

++--------------------------------------------------------+----------+----------+

+|**4. CWS application with untrusted testers** | | |CHK| |

+| | | |

+| .. | | |

+| | | |

+| The standard technique for distributing a packaged or | | |

+| hosted application in the CWS. You can limit the | | |

+| application to trusted testers. This technique | | |

+| requires a server if your application is a hosted | | |

+| application. | | |

++--------------------------------------------------------+----------+----------+

.. |CHK| image:: /images/check-red.png