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

Side by Side Diff: chrome/common/extensions/docs/templates/articles/about_apps.html

Issue 291663002: Adjustments to the fatnav and sidenav, and other CSS updates (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Added missing copyright license. Fixed bad indentation on search.js Created 6 years, 6 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 <meta name="doc-family" content="apps"> 1 <meta name="doc-family" content="apps">
2 <h1>What Are Chrome Apps?</h1> 2 <h1>What Are Chrome Apps?</h1>
3 3
4 <p> 4 <p>
5 Chrome Apps deliver an experience as capable as a native app, 5 Chrome Apps deliver an experience as capable as a native app,
6 but as safe as a web page. 6 but as safe as a web page.
7 Just like web apps, 7 Just like web apps,
8 Chrome Apps are written in HTML5, JavaScript, and CSS. 8 Chrome Apps are written in HTML5, JavaScript, and CSS.
9 But Chrome Apps look and behave like native apps, 9 But Chrome Apps look and behave like native apps,
10 and they have native-like capabilities 10 and they have native-like capabilities
11 that are much more powerful than those available to web apps. 11 that are much more powerful than those available to web apps.
12 </p> 12 </p>
13 13
14 <p> 14 <div class="video-container">
15 <iframe title="YouTube video player" width="610" height="380" src="//www.youtube .com/embed/lBUGTVIJVfM" frameborder="0" allowfullscreen></iframe> 15 <iframe title="YouTube video player" width="610" height="380" src="//www.youtu be.com/embed/lBUGTVIJVfM" frameborder="0" allowfullscreen></iframe>
16 </p> 16 </div>
17 17
18 <p> 18 <p>
19 Chrome Apps have access to Chrome APIs and services not available to 19 Chrome Apps have access to Chrome APIs and services not available to
20 traditional web sites. You can build powerful apps that interact with network 20 traditional web sites. You can build powerful apps that interact with network
21 and hardware devices, media tools, and much more. Here's a short list of 21 and hardware devices, media tools, and much more. Here's a short list of
22 examples: 22 examples:
23 </p> 23 </p>
24 24
25 <ul> 25 <ul>
26 » <li>Shells (VMWare, Citrix, SSH, RDP or VNC clients)</li> 26 <li>Shells (VMWare, Citrix, SSH, RDP or VNC clients)</li>
27 » <li>Music/video streaming</li> 27 <li>Music/video streaming</li>
28 » <li>Photo/video/music editing</li> 28 <li>Photo/video/music editing</li>
29 </ul> 29 </ul>
30 30
31 <p> 31 <p>
32 Watch the Chrome Apps<strong> 32 Watch the Chrome Apps<strong>
33 <a href="http://www.youtube.com/watch?v=j8oFAr1YR-0">2012</a> 33 <a href="http://www.youtube.com/watch?v=j8oFAr1YR-0">2012</a>
34 and 34 and
35 <a href="http://www.youtube.com/watch?v=f2tJRXDTMuY">2013</a> 35 <a href="http://www.youtube.com/watch?v=f2tJRXDTMuY">2013</a>
36 Google I/O presentations</strong> for an in-depth introduction. 36 Google I/O presentations</strong> for an in-depth introduction.
37 </p> 37 </p>
38 38
39 <h2 id="look">How they look</h2> 39 <h2 id="look">How they look</h2>
40 40
41 <p> 41 <p>
42 When a user opens a Chrome App, 42 When a user opens a Chrome App,
43 their focus is specifically on the tasks 43 their focus is specifically on the tasks
44 relating to the app. 44 relating to the app.
45 Chrome Apps have no traditional chrome: 45 Chrome Apps have no traditional chrome:
46 the omnibox (address bar), tab strip, 46 the omnibox (address bar), tab strip,
47 and other browser interface elements no longer appear. 47 and other browser interface elements no longer appear.
48 Like native apps, they don’t live within the browser. 48 Like native apps, they don’t live within the browser.
49 When launched, Chrome Apps can open in windows 49 When launched, Chrome Apps can open in windows
50 that look like this (and you can style 50 that look like this (and you can style
51 your windows in all different ways): 51 your windows in all different ways):
52 </p> 52 </p>
53 <br>
54 53
55 <img src="{{static}}/images/editor.png" 54 <img src="{{static}}/images/editor.png"
56 width="770"
57 height="586"
58 alt="Text editor Chrome App in a standalone window"> 55 alt="Text editor Chrome App in a standalone window">
59 56
60 <h2 id="behave">How they behave</h2> 57 <h2 id="behave">How they behave</h2>
61 58
62 <p> 59 <p>
63 Chrome App pages always load locally. 60 Chrome App pages always load locally.
64 This allows apps to be less dependent on the network. 61 This allows apps to be less dependent on the network.
65 Once a user installs an app, they have full control over the app's lifecycle. 62 Once a user installs an app, they have full control over the app's lifecycle.
66 Apps open and close quickly, 63 Apps open and close quickly,
67 and the system can shut apps down at any time to improve performance. 64 and the system can shut apps down at any time to improve performance.
(...skipping 21 matching lines...) Expand all
89 The app container and programming models control how Chrome Apps look and behave . 86 The app container and programming models control how Chrome Apps look and behave .
90 These models aim to provide users with a more native experience. 87 These models aim to provide users with a more native experience.
91 Powerful APIs have been added so your apps can have native-like capabilities, 88 Powerful APIs have been added so your apps can have native-like capabilities,
92 and a serious security model is enforced to make sure these APIs are not abused. </p> 89 and a serious security model is enforced to make sure these APIs are not abused. </p>
93 90
94 <p> 91 <p>
95 To learn more about how to develop Chrome Apps: 92 To learn more about how to develop Chrome Apps:
96 </p> 93 </p>
97 94
98 <ul> 95 <ul>
99 » <li> 96 <li>
100 » » <a href="app_architecture">Understanding the Architecture</a> 97 <a href="app_architecture">Understanding the Architecture</a>
101 » » introduces the app container, programming, and security models. 98 introduces the app container, programming, and security models.
102 » </li> 99 </li>
103 » <li> 100 <li>
104 » » <a href="app_lifecycle">The Fundamentals</a> 101 <a href="app_lifecycle">The Fundamentals</a>
105 » » shows how to use this architecture and how to build 102 shows how to use this architecture and how to build
106 » » for offline, manage data, and embed external content. 103 for offline, manage data, and embed external content.
107 » </li> 104 </li>
108 » <li> 105 <li>
109 » » <a href="app_network">Advanced Technologies</a> 106 <a href="app_network">Advanced Technologies</a>
110 » » shows how to use the powerful network and hardware APIs. 107 shows how to use the powerful network and hardware APIs.
111 » </li> 108 </li>
112 » <li> 109 <li>
113 » » <a href="app_deprecated">Disabled Features</a> 110 <a href="app_deprecated">Disabled Features</a>
114 » » describes the web features that have been disabled 111 describes the web features that have been disabled
115 » » and what to use in their place, where relevant. 112 and what to use in their place, where relevant.
116 » </li> 113 </li>
117 </ul> 114 </ul>
118 115
119 <p class="backtotop"><a href="#top">Back to top</a></p> 116 <p class="backtotop"><a href="#top">Back to top</a></p>
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698