Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(104)

Side by Side Diff: native_client_sdk/src/doc/devguide/devcycle/running.rst

Issue 254033002: [NaCl SDK Docs] Remove links to developers.google.com (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: . Created 6 years, 7 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 unified diff | Download patch | Annotate | Revision Log
OLDNEW
1 .. _devcycle-running: 1 .. _devcycle-running:
2 2
3 ####### 3 #######
4 Running 4 Running
5 ####### 5 #######
6 6
7 .. contents:: 7 .. contents::
8 :local: 8 :local:
9 :backlinks: none 9 :backlinks: none
10 :depth: 2 10 :depth: 2
(...skipping 260 matching lines...) Expand 10 before | Expand all | Expand 10 after
271 |ICON16| 271 |ICON16|
272 272
273 |ICON128| 273 |ICON128|
274 274
275 .. |ICON16| image:: /images/icon16.png 275 .. |ICON16| image:: /images/icon16.png
276 .. |ICON128| image:: /images/icon128.png 276 .. |ICON128| image:: /images/icon128.png
277 277
278 Put the icons in the same directory as the CWS manifest file. For more 278 Put the icons in the same directory as the CWS manifest file. For more
279 information about CWS manifest files and application icons, see: 279 information about CWS manifest files and application icons, see:
280 280
281 * `Chrome Web Store Tutorial: Getting Started 281 * `Chrome Web Store Tutorial: Getting Started </webstore/get_started_simple>`_
282 <https://developers.google.com/chrome/web-store/docs/get_started_simple>`_ 282 * `Chrome Web Store Formats: Manifest Files </extensions/manifest>`_
283 * `Chrome Web Store Formats: Manifest Files
284 <http://code.google.com/chrome/extensions/manifest.html>`_
285 283
286 Technique 1: Local server 284 Technique 1: Local server
287 ========================= 285 =========================
288 286
289 To run your application from a local server: 287 To run your application from a local server:
290 288
291 * Enable the :ref:`Native Client flag <flag>` in Chrome. 289 * Enable the :ref:`Native Client flag <flag>` in Chrome.
292 * Start a :ref:`local web server <web_server>`. 290 * Start a :ref:`local web server <web_server>`.
293 * Put your application under the examples directory in the SDK bundle you are 291 * Put your application under the examples directory in the SDK bundle you are
294 using (e.g., in the directory ``pepper_31/examples/my_app``). 292 using (e.g., in the directory ``pepper_31/examples/my_app``).
(...skipping 34 matching lines...) Expand 10 before | Expand all | Expand 10 after
329 * In the file dialog that appears, select your application directory. Unless 327 * In the file dialog that appears, select your application directory. Unless
330 you get an error dialog, you've now installed your app in Chrome. 328 you get an error dialog, you've now installed your app in Chrome.
331 #. Open a new tab in Chrome and click the **Apps** link at the bottom of the 329 #. Open a new tab in Chrome and click the **Apps** link at the bottom of the
332 page to show your installed apps: 330 page to show your installed apps:
333 |new-tab-apps| 331 |new-tab-apps|
334 #. The icon for your newly installed app should appear on the New Tab page. 332 #. The icon for your newly installed app should appear on the New Tab page.
335 Click the icon to launch the app. 333 Click the icon to launch the app.
336 334
337 For additional information about how to create CWS metadata and load your 335 For additional information about how to create CWS metadata and load your
338 application into Chrome (including troubleshooting information), see the 336 application into Chrome (including troubleshooting information), see the
339 `Chrome Web Store Tutorial: Getting Started 337 `Chrome Web Store Tutorial: Getting Started </webstore/get_started_simple>`_.
340 <https://developers.google.com/chrome/web-store/docs/get_started_simple>`_.
341 338
342 See also :ref:`run_sdk_examples_as_packaged`. 339 See also :ref:`run_sdk_examples_as_packaged`.
343 340
344 Technique 3: Hosted application loaded as an unpacked extension 341 Technique 3: Hosted application loaded as an unpacked extension
345 =============================================================== 342 ===============================================================
346 343
347 For development purposes, Chrome lets you load a hosted application as an 344 For development purposes, Chrome lets you load a hosted application as an
348 unpacked extension. To load and run your hosted application as an unpacked 345 unpacked extension. To load and run your hosted application as an unpacked
349 extension: 346 extension:
350 347
(...skipping 29 matching lines...) Expand all
380 * In the file dialog that appears, select your application directory. Unless 377 * In the file dialog that appears, select your application directory. Unless
381 you get an error dialog, you've now installed your app in Chrome. 378 you get an error dialog, you've now installed your app in Chrome.
382 #. Open a new tab in Chrome and click the **Apps** link at the bottom of the 379 #. Open a new tab in Chrome and click the **Apps** link at the bottom of the
383 page to show your installed apps: 380 page to show your installed apps:
384 |new-tab-apps| 381 |new-tab-apps|
385 #. The icon for your newly installed app should appear on the New Tab page. 382 #. The icon for your newly installed app should appear on the New Tab page.
386 Click the icon to launch the app. 383 Click the icon to launch the app.
387 384
388 For additional information about how to create CWS metadata and load your 385 For additional information about how to create CWS metadata and load your
389 application into Chrome (including troubleshooting information), see the 386 application into Chrome (including troubleshooting information), see the
390 `Chrome Web Store Tutorial: Getting Started 387 `Chrome Web Store Tutorial: Getting Started </webstore/get_started_simple>`_.
391 <https://developers.google.com/chrome/web-store/docs/get_started_simple>`_.
392 388
393 Technique 4: Chrome Web Store application with trusted testers 389 Technique 4: Chrome Web Store application with trusted testers
394 ============================================================== 390 ==============================================================
395 391
396 When you're ready to test your application more broadly, you can upload the 392 When you're ready to test your application more broadly, you can upload the
397 application to the Chrome Web Store and let some trusted testers run it. Here 393 application to the Chrome Web Store and let some trusted testers run it. Here
398 is how to do so: 394 is how to do so:
399 395
400 #. Create the Chrome Web Store metadata required to publish your application: 396 #. Create the Chrome Web Store metadata required to publish your application:
401 397
(...skipping 58 matching lines...) Expand 10 before | Expand all | Expand 10 after
460 Store. Copy the URL and mail it to your trusted testers. 456 Store. Copy the URL and mail it to your trusted testers.
461 457
462 * When you publish an application to test accounts, the application's CWS 458 * When you publish an application to test accounts, the application's CWS
463 listing is visible only to you and to people who are logged into those 459 listing is visible only to you and to people who are logged into those
464 accounts. Your application won't appear in search results, so you need to 460 accounts. Your application won't appear in search results, so you need to
465 give testers a direct link to your application's CWS listing. Users won't 461 give testers a direct link to your application's CWS listing. Users won't
466 be able to find the application by searching in the CWS. 462 be able to find the application by searching in the CWS.
467 463
468 To publish an application to the world after publishing it to test accounts, 464 To publish an application to the world after publishing it to test accounts,
469 you must first unpublish the application. For additional information see 465 you must first unpublish the application. For additional information see
470 `Publishing Your App 466 `Publishing Your App </webstore/docs/publish>`_, and in particular `Publishing
471 <https://developers.google.com/chrome/web-store/docs/publish>`_, and in 467 to test accounts </webstore/publish#testaccounts>`_.
472 particular `Publishing to test accounts
473 <https://developers.google.com/chrome/web-store/docs/publish#testaccounts>`_.
474 468
475 .. |menu-icon| image:: /images/menu-icon.png 469 .. |menu-icon| image:: /images/menu-icon.png
476 .. |extensions| image:: /images/extensions-management.png 470 .. |extensions| image:: /images/extensions-management.png
477 .. |new-tab-apps| image:: /images/new-tab-apps.png 471 .. |new-tab-apps| image:: /images/new-tab-apps.png
OLDNEW
« no previous file with comments | « native_client_sdk/src/doc/devguide/devcycle/debugging.rst ('k') | native_client_sdk/src/doc/devguide/distributing.rst » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698