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 176 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
187 <p> | 187 <p> |
188 Packaged apps deliver an experience as capable as a native app, | 188 Packaged apps deliver an experience as capable as a native app, |
189 but as safe as a web page. | 189 but as safe as a web page. |
190 Just like web apps, | 190 Just like web apps, |
191 packaged apps are written in HTML5, JavaScript, and CSS. | 191 packaged apps are written in HTML5, JavaScript, and CSS. |
192 But packaged apps look and behave like native apps, | 192 But packaged apps look and behave like native apps, |
193 and they have native-like capabilities | 193 and they have native-like capabilities |
194 that are much more powerful than those available to web apps. | 194 that are much more powerful than those available to web apps. |
195 </p> | 195 </p> |
196 <p> | 196 <p> |
197 <iframe title="YouTube video player" width="610" height="380" src="http://www.yo
utube.com/embed/lBUGTVIJVfM" frameborder="0" allowfullscreen=""></iframe> | 197 <iframe title="YouTube video player" width="610" height="380" src="http://www.yo
utube.com/embed/lBUGTVIJVfM" frameborder="0" allowfullscreen=""></iframe><br> |
198 </p> | 198 </p> |
199 <p> | 199 <p> |
200 With access to Chrome APIs and services | 200 Packaged apps have have access to Chrome APIs and services not available to |
201 not available to traditional web apps, | 201 traditional web sites. You can build powerful apps that interact with network |
202 you can build powerful apps that interact | 202 and hardware devices, media tools, and much more. Here's a short list of |
203 with network and hardware devices, | 203 examples: |
204 as well as, media apps. | |
205 Here's a short list of examples: | |
206 </p> | 204 </p> |
207 <ul> | 205 <ul> |
208 <li>Shells (VMWare, Citrix, SSH, RDP or VNC clients)</li> | 206 <li>Shells (VMWare, Citrix, SSH, RDP or VNC clients)</li> |
209 <li>Music/video streaming</li> | 207 <li>Music/video streaming</li> |
210 <li>Photo/video/music editing</li> | 208 <li>Photo/video/music editing</li> |
211 </ul> | 209 </ul> |
| 210 <p> |
| 211 Watch the <a href="http://www.youtube.com/watch?v=j8oFAr1YR-0">Chrome Apps |
| 212 Google I/O presentation</a> for an in-depth introduction. |
| 213 </p> |
212 <h2 id="look">How they look</h2> | 214 <h2 id="look">How they look</h2> |
213 <p> | 215 <p> |
214 When a user opens a packaged app, | 216 When a user opens a packaged app, |
215 their focus is specifically on the tasks | 217 their focus is specifically on the tasks |
216 relating to the app. | 218 relating to the app. |
217 Packaged apps have no traditional chrome: | 219 Packaged apps have no traditional chrome: |
218 the omnibox (address bar), tab strip, | 220 the omnibox (address bar), tab strip, |
219 and other browser interface elements no longer appear. | 221 and other browser interface elements no longer appear. |
220 Like native apps, they don’t live within the browser. | 222 Like native apps, they don’t live within the browser. |
221 When launched, packaged apps can open in windows | 223 When launched, packaged apps can open in windows |
(...skipping 97 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
319 _uff=0; | 321 _uff=0; |
320 urchinTracker(); | 322 urchinTracker(); |
321 } | 323 } |
322 catch(e) {/* urchinTracker not available. */} | 324 catch(e) {/* urchinTracker not available. */} |
323 </script> | 325 </script> |
324 <!-- end analytics --> | 326 <!-- end analytics --> |
325 </div> | 327 </div> |
326 </div> <!-- /gc-footer --> | 328 </div> <!-- /gc-footer --> |
327 </div> <!-- /gc-container --> | 329 </div> <!-- /gc-container --> |
328 </body></html> | 330 </body></html> |
OLD | NEW |