Reorganized files.
This commit is contained in:
Arthur Evans
Родитель
8d57b9b29a
Коммит
4ecfb8ec6e
|
|
@ -64,7 +64,7 @@
|
|||
|
||||
<h2>Use Developer Tools to find problems—and fix them</h2>
|
||||
|
||||
<p>Debugging web pages on the small screen is difficult. There's just not enough real estate to inspect elements and resources on the device. Now you can debug mobile web sites with the full suite of <a href="devtools/index.html">Chrome Developer Tools</a> running on a desktop browser that's connected to your phone via USB. See <a href="debugging.html">Remote Debugging</a> for further details.</p>
|
||||
<p>Debugging web pages on the small screen is difficult. There's just not enough real estate to inspect elements and resources on the device. Now you can debug mobile web sites with the full suite of <a href="/devtools/index.html">Chrome Developer Tools</a> running on a desktop browser that's connected to your phone via USB. See <a href="/devtools/docs/remote-debugging.html">Remote Debugging</a> for further details.</p>
|
||||
|
||||
<p>In addition to the powerful Chrome Developer Tools, Chrome for Android
|
||||
provides more advanced developer features:</p>
|
||||
17
index.html
17
index.html
|
|
@ -6,24 +6,25 @@
|
|||
<ul>
|
||||
<li>Using Chrome Mobile for devices running Android 4.0 and later, and iOS.</li>
|
||||
<li>With the default Android browser, for devices running versions of Android earlier than 4.0 (Ice Cream Sandwich).</li>
|
||||
<li>Within <code><a href="http://developer.android.com/guide/webapps/webview.html">WebView</a></code> on a native Android application.</li>
|
||||
<li>Within a <a href="webview/overview.html">WebView</a></code> in a native Android application.</li>
|
||||
</ul>
|
||||
|
||||
<p>Chrome Mobile browser is the base WebKit browser implemented by both Google Chrome for Android and Apple Mobile Safari. There are differences in the implementations of each. See the following pages:</p>
|
||||
<ul>
|
||||
<li><a href="overview.html">Chrome for Android</a></li>
|
||||
<li><a href="iosoverview.html">Chrome for iOS</a></li>
|
||||
<li><a href="android/overview.html">Chrome for Android</a></li>
|
||||
<li><a href="ios/overview.html">Chrome for iOS</a></li>
|
||||
</ul>
|
||||
|
||||
<!-- the first-time user procedure goes here -->
|
||||
<h2>Getting started</h2>
|
||||
<ol>
|
||||
<ul>
|
||||
<li>Visit <a href="https://play.google.com/store/apps/details?id=com.android.chrome">Google Play</a> to install Chrome for Android or <a href="http://itunes.apple.com/us/app/chrome/id535886823?ls=1&mt=8">AppStore</a> for Chrome for iOS.</li>
|
||||
<li>Read about <a href="overview.html">Chrome for Android
|
||||
<li>Read about <a href="android/overview.html">Chrome for Android
|
||||
features</a> to use in developing mobile web apps.</li>
|
||||
<li>Review the considerations for <a href="iosoverview.html">Chrome for iOS</a>.</li>
|
||||
<li>Review the considerations for <a href="ios/overview.html">Chrome for iOS</a>.</li>
|
||||
<li>Learn about developing applications in the <a href="webview/overview.html">Chrome WebView for Android</a>.</li>
|
||||
<li>Learn more about mobile web development on <a href="http://www.html5rocks.com/mobile">mobile HTML5 Rocks</a>.</li>
|
||||
</ol>
|
||||
</ul>
|
||||
|
||||
|
||||
<h2>Featured video</h2>
|
||||
|
|
@ -36,6 +37,6 @@ features</a> to use in developing mobile web apps.</li>
|
|||
<param name="wmode" value="transparent">
|
||||
<embed src="https://www.youtube.com/v/s4zpL4VBbuU" type="application/x-shockwave-flash" wmode="transparent" width="300" height="193"></object></p>
|
||||
|
||||
<p>Read more about it in <a href="debugging.html">Remote Debugging</a>.</p>
|
||||
<p>Read more about it in <a href="/devtools/docs/remote-debugging.html">Remote Debugging</a>.</p>
|
||||
|
||||
{{/partials.standard_multidevice_article}}
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@
|
|||
|
||||
<p>Feedly prioritizes speed and intuitive usability to provide users with easy, direct access to their favorite content. Some of Feedly’s mobile publishers use partial RSS feeds. Users who click on these feeds navigate out of Feedly app to read the remainder of the content in the browser. As a result, the Feedly team prioritized helping users navigate between the Feedly app and the browser.</p>
|
||||
|
||||
<p>The integration of the Chrome <a href="ios-links.html#callback">callback</a> feature into the Feedly iPhone and iPad app “was a no brainer and surprisingly simple to implement,” said the Feedly team.</p>
|
||||
<p>The integration of the Chrome <a href="links.html#callback">callback</a> feature into the Feedly iPhone and iPad app “was a no brainer and surprisingly simple to implement,” said the Feedly team.</p>
|
||||
|
||||
<p>The Feedly team notes that “90% of the time, once a user has finished reading an article, they want to resume skimming their feedly, looking for the next article to read.” Chrome callback enables a seamless transition between Feedly and Chrome, helping users access the content they want faster.</p>
|
||||
|
||||
|
|
@ -4,7 +4,7 @@
|
|||
|
||||
<p>Chrome for iOS is designed to be fast. Users search and navigate fast, directly from the same omnibox. Results appear as the user types (prefetching). Users open and quickly switch between an unlimited number of tabs. With sign-in to Chrome, the user's tabs, bookmarks, passwords, and omnibox data sync automatically from other Chrome instances to the iPhone, iPod touch, or iPad, eliminating the delay otherwise inherent with switching between devices. Moreover, the user can send pages from Chrome on the computer to the iPhone, iPod touch, or iPad with one click and read them on the go, even when offline.
|
||||
|
||||
<p>Chrome for iOS is derived from the WebKit browser codebase, as is Apple's Mobile Safari. However, while Apple allows only Safari to access iOS facilities like the iOS Nitro engine, Chrome uses Apple's <a href="http://developer.apple.com/library/ios/#documentation/uikit/reference/UIWebView_Class/Reference/Reference.html">UIWebView</a> for loading and rendering content. Any of the considerations for UIWebView apply to Chrome for iOS. See the <a href="faq.html">Chrome Mobile FAQ</a> for more information.</p>
|
||||
<p>Chrome for iOS is derived from the WebKit browser codebase, as is Apple's Mobile Safari. However, while Apple allows only Safari to access iOS facilities like the iOS Nitro engine, Chrome uses Apple's <a href="http://developer.apple.com/library/ios/#documentation/uikit/reference/UIWebView_Class/Reference/Reference.html">UIWebView</a> for loading and rendering content. Any of the considerations for UIWebView apply to Chrome for iOS. See the <a href="/multidevice/faq.html">Chrome Mobile FAQ</a> for more information.</p>
|
||||
|
||||
<p>There are considerations as well for opening URLs in Chrome for iOS, see <a href="ios-links.html">Opening links in Chrome</a>.</p>
|
||||
|
||||
|
|
@ -4,11 +4,11 @@
|
|||
|
||||
<p><a href="http://getpocket.com">Pocket</a> provides a cross-device experience where users can save articles and almost any other type of web content to view later, on or offline. The Pocket team strives to make taking any type of content with you “as simple an action as putting it in your pocket.”</p>
|
||||
|
||||
<img src="images/pocket.png" style="width: 50%; height: 50%; float:left; margin-right:30px; margin-bottom:5px;"/>
|
||||
<img src="/multidevice/images/pocket.png" style="width: 50%; height: 50%; float:left; margin-right:30px; margin-bottom:5px;"/>
|
||||
|
||||
<p>Pocket excels at presenting that content in a clean, clutter-free viewing experience across platforms. Still, there are times when users want access to a full browsing experience. In addition, Pocket notes, "Chrome users spend nearly 30% more time in the app than users of the next leading browser."</p>
|
||||
|
||||
<p>Chrome <a href="ios-links.html#callback">callback</a> enables Pocket to pass users seamlessly between Chrome browser and the Pocket app while maintaining Pocket’s simple design. Now, users, which save over 43 million items a month, have a quick and intuitive way to return to the Pocket app while viewing their saved content on the web.</p>
|
||||
<p>Chrome <a href="/multidevice/ios/links.html#callback">callback</a> enables Pocket to pass users seamlessly between Chrome browser and the Pocket app while maintaining Pocket’s simple design. Now, users, which save over 43 million items a month, have a quick and intuitive way to return to the Pocket app while viewing their saved content on the web.</p>
|
||||
|
||||
<p>With a growing base of engaged, tech-savvy users, Pocket looks to continue enhancing the way its more than 9.5 million users discover and consume content.</p>
|
||||
|
||||
|
|
@ -423,6 +423,6 @@ for non-local pages:</p>
|
|||
|
||||
<p>For tips on getting the visuals just right, see <a href="pixelperfect.html">Pixel-Perfect UI in the WebView</a>.</p>
|
||||
|
||||
<p>If you run into trouble, the Chrome DevTools are your friends. See <a href="https://developers.google.com/chrome-developer-tools/docs/remote-debugging">Remote Debugging on Android</a> to get started.</p>
|
||||
<p>If you run into trouble, the Chrome DevTools are your friends. See <a href="/devtools/docs/remote-debugging">Remote Debugging on Android</a> to get started.</p>
|
||||
|
||||
{{/partials.standard_multidevice_article}}
|
||||
|
|
@ -12,7 +12,7 @@ so rendering should be much more consistent between the WebView and Chrome.</p>
|
|||
|
||||
<p>For tips on scaling WebView content for mobile devices, see <a href="pixelperfect.html">Pixel-Perfect UI in the WebView</a>. </p>
|
||||
|
||||
<p>The new WebView also supports <a href="https://developers.google.com/chrome-developer-tools/docs/remote-debugging">remote debugging</a>
|
||||
<p>The new WebView also supports <a href="/devtools/docs/remote-debugging">remote debugging</a>
|
||||
using the Chrome DevTools.</p>
|
||||
|
||||
<h2 id="webview_faq">WebView FAQ</h2>
|
||||
Загрузка…
Ссылка в новой задаче