Chromium Code Reviews| OLD | NEW |
|---|---|
| 1 <!DOCTYPE html><!-- This page is a placeholder for generated extensions api doc. Note: | 1 <!DOCTYPE html><!-- This page is a placeholder for generated extensions api doc. Note: |
| 2 1) The <head> information in this page is significant, should be uniform | 2 1) The <head> information in this page is significant, should be uniform |
| 3 across api docs and should be edited only with knowledge of the | 3 across api docs and should be edited only with knowledge of the |
| 4 templating mechanism. | 4 templating mechanism. |
| 5 3) All <body>.innerHTML is genereated as an rendering step. If viewed in a | 5 3) All <body>.innerHTML is genereated as an rendering step. If viewed in a |
| 6 browser, it will be re-generated from the template, json schema and | 6 browser, it will be re-generated from the template, json schema and |
| 7 authored overview content. | 7 authored overview content. |
| 8 4) The <body>.innerHTML is also generated by an offline step so that this | 8 4) The <body>.innerHTML is also generated by an offline step so that this |
| 9 page may easily be indexed by search engines. | 9 page may easily be indexed by search engines. |
| 10 --><html xmlns="http://www.w3.org/1999/xhtml"><head> | 10 --><html xmlns="http://www.w3.org/1999/xhtml"><head> |
| (...skipping 322 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
| 333 </p> | 333 </p> |
| 334 | 334 |
| 335 <!-- STATIC CONTENT PLACEHOLDER --> | 335 <!-- STATIC CONTENT PLACEHOLDER --> |
| 336 <div id="static"><div id="pageData-name" class="pageData">Packaging</div > | 336 <div id="static"><div id="pageData-name" class="pageData">Packaging</div > |
| 337 <div id="pageData-showTOC" class="pageData">true</div> | 337 <div id="pageData-showTOC" class="pageData">true</div> |
| 338 | 338 |
| 339 <p> | 339 <p> |
| 340 This page describes how to package your extension. | 340 This page describes how to package your extension. |
| 341 As the <a href="overview.html">Overview</a> explains, | 341 As the <a href="overview.html">Overview</a> explains, |
| 342 extensions are packaged as signed ZIP files | 342 extensions are packaged as signed ZIP files |
| 343 with the file extension "crx" — | 343 with the file extension "crx"—for example, |
| 344 for example, <code>myextension.crx</code>. | 344 <code>myextension.crx</code>. |
| 345 </p> | 345 </p> |
| 346 | 346 |
| 347 <p> | 347 <p> |
| 348 <b>Note:</b> | 348 <b>Note:</b> |
| 349 You might not need to package your extension. | 349 You might not need to package your extension. |
| 350 If you publish your extension using the | 350 If you publish your extension using the |
| 351 <a href="https://chrome.google.com/webstore/developer/dashboard">Chrome Develope r Dashboard</a>, | 351 <a href="https://chrome.google.com/webstore/developer/dashboard">Chrome Develope r Dashboard</a>, |
| 352 then the only reason to create your own <code>.crx</code> file | 352 then the only reason to create your own <code>.crx</code> file |
| 353 would be to distribute a non-public version — | 353 would be to distribute a non-public version—for example, |
| 354 for example, to alpha testers. | 354 to alpha testers. |
| 355 You can find information on publishing extensions and apps in the | |
| 356 Chrome Web Store getting started tutorial, starting at | |
| 357 <a href="http://code.google.com/chrome/webstore/docs/get_started_simple.html#ste p5">Step 5: Zip up your app</a>. | |
| 355 </p> | 358 </p> |
| 356 | 359 |
| 357 <!-- [PENDING: Refer to instructions on submitting an extension for inclusion in the gallery.] --> | |
| 358 | |
| 359 <p> | 360 <p> |
| 360 When you package an extension, | 361 When you package an extension, |
| 361 the extension is assigned a unique key pair. | 362 the extension is assigned a unique key pair. |
| 362 The extension's ID is based on a hash of the public key. | 363 The extension's ID is based on a hash of the public key. |
| 363 The private key is kept private | 364 The private key is kept private |
| 364 and used to sign each version of the extension. | 365 and used to sign each version of the extension. |
| 365 </p> | 366 </p> |
| 366 | 367 |
| 367 | 368 |
| 368 <a name="H2-0"></a><h2>Creating a package</h2> | 369 <a name="H2-0"></a><h2>Creating a package</h2> |
| (...skipping 13 matching lines...) Expand all Loading... | |
| 382 click the +. | 383 click the +. |
| 383 </li> | 384 </li> |
| 384 | 385 |
| 385 <li> | 386 <li> |
| 386 Click the <b>Pack extension</b> button. | 387 Click the <b>Pack extension</b> button. |
| 387 A dialog appears. | 388 A dialog appears. |
| 388 </li> | 389 </li> |
| 389 | 390 |
| 390 <li> | 391 <li> |
| 391 In the <b>Extension root directory</b> field, | 392 In the <b>Extension root directory</b> field, |
| 392 specify the path to the extension's folder — | 393 specify the path to the extension's folder—for example, |
| 393 for example, <code>c:\myext</code>. | 394 <code>c:\myext</code>. |
| 394 (Ignore the other field; | 395 (Ignore the other field; |
| 395 you don't specify a private key file | 396 you don't specify a private key file |
| 396 the first time you package a particular extension.) | 397 the first time you package a particular extension.) |
| 397 </li> | 398 </li> |
| 398 | 399 |
| 399 <li> | 400 <li> |
| 400 Click <b>OK</b>. | 401 Click <b>OK</b>. |
| 401 The packager creates two files: | 402 The packager creates two files: |
| 402 a <code>.crx</code> file, | 403 a <code>.crx</code> file, |
| 403 which is the actual extension that can be installed, | 404 which is the actual extension that can be installed, |
| (...skipping 36 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
| 440 by going to this URL: <b>chrome://extensions</b> | 441 by going to this URL: <b>chrome://extensions</b> |
| 441 </li> | 442 </li> |
| 442 | 443 |
| 443 <li> | 444 <li> |
| 444 Click the <b>Pack extension</b> button. | 445 Click the <b>Pack extension</b> button. |
| 445 A dialog appears. | 446 A dialog appears. |
| 446 </li> | 447 </li> |
| 447 | 448 |
| 448 <li> | 449 <li> |
| 449 In the <b>Extension root directory</b> field, | 450 In the <b>Extension root directory</b> field, |
| 450 specify the path to the extension's folder — | 451 specify the path to the extension's folder—for example, |
|
Boris Smus
2011/08/30 23:18:31
Deliberately removed spaces around the hyphen?
| |
| 451 for example, <code>c:\myext</code>. | 452 <code>c:\myext</code>. |
| 452 </li> | 453 </li> |
| 453 | 454 |
| 454 <li> | 455 <li> |
| 455 In the <b>Private key file</b> field, | 456 In the <b>Private key file</b> field, |
| 456 specify the location of the | 457 specify the location of the |
| 457 already generated <code>.pem</code> file for this extension — | 458 already generated <code>.pem</code> file for this extension—for |
| 458 for example, <code>c:\myext.pem</code>. | 459 example, <code>c:\myext.pem</code>. |
| 459 </li> | 460 </li> |
| 460 | 461 |
| 461 <li> | 462 <li> |
| 462 Click <b>OK</b>. | 463 Click <b>OK</b>. |
| 463 </li> | 464 </li> |
| 464 </ol> | 465 </ol> |
| 465 | 466 |
| 466 <p>If the updated extension is successfully packaged, you'll see a dialog like t his:</p> | 467 <p>If the updated extension is successfully packaged, you'll see a dialog like t his:</p> |
| 467 | 468 |
| 468 <img src="images/update-success.gif" width="298" height="160"> | 469 <img src="images/update-success.gif" width="298" height="160"> |
| (...skipping 231 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
| 700 _uff=0; | 701 _uff=0; |
| 701 urchinTracker(); | 702 urchinTracker(); |
| 702 } | 703 } |
| 703 catch(e) {/* urchinTracker not available. */} | 704 catch(e) {/* urchinTracker not available. */} |
| 704 </script> | 705 </script> |
| 705 <!-- end analytics --> | 706 <!-- end analytics --> |
| 706 </div> | 707 </div> |
| 707 </div> <!-- /gc-footer --> | 708 </div> <!-- /gc-footer --> |
| 708 </div> <!-- /gc-container --> | 709 </div> <!-- /gc-container --> |
| 709 </body></html> | 710 </body></html> |
| OLD | NEW |