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

Side by Side Diff: chrome/common/extensions/docs/static/autoupdate.html

Issue 465039: Extension Doc Changes (no building or testable changes) (Closed)
Patch Set: Created 11 years 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
OLDNEW
1 <div id="pageData-title" class="pageData">Autoupdating</div> 1 <div id="pageData-name" class="pageData">Autoupdating</div>
2 <div id="pageData-showTOC" class="pageData">true</div> 2 <div id="pageData-showTOC" class="pageData">true</div>
3 3
4 <p>We want extensions to be autoupdated for some of the same reasons as Google C hrome itself: to incorporate bug and security fixes, add new features or perform ance enhancements, and improve user interfaces.</p> 4 <p>We want extensions to be autoupdated for some of the same reasons as Google C hrome itself: to incorporate bug and security fixes, add new features or perform ance enhancements, and improve user interfaces.</p>
5 5
6 <p>For extensions packaged and distributed via the <a href="https://chrome.googl e.com/extensions">gallery</a>, developers will be able to use a web interface to release updated versions of their extensions and do not need to concern themsel ves with the rest of this document.</p> 6 <p>For extensions packaged and distributed via the <a href="https://chrome.googl e.com/extensions">gallery</a>, developers will be able to use a web interface to release updated versions of their extensions and do not need to concern themsel ves with the rest of this document.</p>
7 7
8 <p>Those who choose to host extensions themselves instead of using the gallery w ill probably want to use autoupdate for their extensions as described below. You might want to make sure you are familiar with <a href="packaging.html">Packagin g</a> first.</p> 8 <p>Those who choose to host extensions themselves instead of using the gallery w ill probably want to use autoupdate for their extensions as described below. You might want to make sure you are familiar with <a href="packaging.html">Packagin g</a> first.</p>
9 9
10 10
11 <h2>Overview</h2> 11 <h2>Overview</h2>
(...skipping 85 matching lines...) Expand 10 before | Expand all | Expand 10 after
97 <pre>&lt;?xml version='1.0' encoding='UTF-8'?&gt; 97 <pre>&lt;?xml version='1.0' encoding='UTF-8'?&gt;
98 &lt;gupdate xmlns='http://www.google.com/update2/response' protocol='2.0'&gt; 98 &lt;gupdate xmlns='http://www.google.com/update2/response' protocol='2.0'&gt;
99 &nbsp;&nbsp;&lt;app appid='aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'&gt; 99 &nbsp;&nbsp;&lt;app appid='aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'&gt;
100 &nbsp;&nbsp; &nbsp;&lt;updatecheck&nbsp;codebase='http://myhost.com/mytestextens ion/mte_v2.crx'&nbsp;version='2.0' <b>prodversionmin='3.0.193.0'</b>/&gt; 100 &nbsp;&nbsp; &nbsp;&lt;updatecheck&nbsp;codebase='http://myhost.com/mytestextens ion/mte_v2.crx'&nbsp;version='2.0' <b>prodversionmin='3.0.193.0'</b>/&gt;
101 &nbsp;&nbsp;&lt;/app&gt; 101 &nbsp;&nbsp;&lt;/app&gt;
102 &lt;/gupdate&gt; 102 &lt;/gupdate&gt;
103 </pre> 103 </pre>
104 104
105 <p>This would ensure that users of this extension would autoupdate to version 2 only if they are running Google Chrome 3.0.193.0 or greater.</p> 105 <p>This would ensure that users of this extension would autoupdate to version 2 only if they are running Google Chrome 3.0.193.0 or greater.</p>
106 106
OLDNEW
« no previous file with comments | « chrome/common/extensions/docs/static/api_other.html ('k') | chrome/common/extensions/docs/static/background_pages.html » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698