Home
last modified time | relevance | path

Searched refs:pages (Results 1 – 25 of 35) sorted by relevance

12

/frameworks/base/docs/html/guide/webapps/
Doverview.jd26 screen support, because it's already easy to make your web pages look good on all types of screens
31 application that embeds some web pages (using a {@link android.webkit.WebView} in your Android
32 application layout). Figure 1 visualizes how you can provide access to your web pages from either
34 application simply as a means to launch your web site. Rather, the web pages you embed in your
36 interface between your Android application and your web pages that allows JavaScript in the web
37 pages to call upon APIs in your Android application—providing Android APIs to your web-based
43 screens), Android 2.0 added features to the WebKit framework to allow web pages to specify
62 <dd>How to embed web pages into your Android application using {@link android.webkit.WebView} and
Dtargeting.jd10 <li>Techniques in this document work for Android 2.0 and greater, and for web pages rendered
32 should carefully consider how your web pages appear on different kinds of screens. Because
34 that affect the way your web pages appear on Android devices.</p>
38 android.webkit.WebView} (the framework view widget for displaying web pages), on Android 2.0 and
42 <p>When targeting your web pages for Android devices, there are two fundamental factors that you
147 <p>As mentioned in the introduction above, the Android Browser loads pages in "overview mode" by
177 Android Browser and {@link android.webkit.WebView} scale web pages to match the perceived size on a
287 screen, the Android Browser and {@link android.webkit.WebView} scale web pages (effectively zoom
288 the pages) so they display at a
290 Android Browser and {@link android.webkit.WebView} apply approximately 1.5x scaling to web pages
[all …]
Dbest-practices.jd13 <p>Developing web pages and web applications for mobile devices presents a different set of
72 computer, you should make your web pages load as fast as possible. One way to speed it up is to
Dwebview.jd8 <li>Use {@link android.webkit.WebView} to display web pages in your Android application
46 extension of Android's {@link android.view.View} class that allows you to display web pages as a
222 navigate to other web pages that are not your own, within your {@link android.webkit.WebView}
298 pages. You can navigate backward and forward through the history with {@link
Ddebugging.jd29 debugging web pages with Firebug or Web Inspector, then you're probably familiar
/frameworks/base/docs/html/distribute/googleplay/strategies/
Dindex.jd27 …<a href="/distribute/googleplay/promote/product-pages.html" class="landing-page-link">Preparing fo…
/frameworks/base/docs/html/distribute/googleplay/publish/
Dindex.jd13 <p>Upload apps, build your product pages, configure prices and
Dpreparing.jd438 <li><strong><a href="{@docRoot}distribute/googleplay/promote/product-pages.html">Your Product Page<…
455 pages, ads, reviews, and more. You can also use special <a
/frameworks/base/tools/preload/loadclass/
DLoadClass.java61 int[] pages = new int[6]; in main() local
/frameworks/base/docs/html/distribute/googleplay/promote/
Dindex.jd25 …<a href="{@docRoot}distribute/googleplay/promote/product-pages.html" class="landing-page-link">You…
Dlinking.jd15 products in the way you want, from Android apps, web pages, ads, reviews,
172 <p>In general, you should use <code>http://</code> format for links on web pages
Dbadges.jd4 …rm below to quickly create badges to link users to your products from web pages, ads, reviews, and…
/frameworks/base/docs/html/training/implementing-navigation/
Dlateral.jd122 …atePagerAdapter}, which destroys fragments as the user navigates to other pages, minimizing memory…
193 …ned {@link android.support.v4.view.PagerTitleStrip} inside it. Individual pages (provided by the a…
229 // When swiping between pages, select the
Dtemporal.jd83 <p>Be careful when using this mechanism with highly dynamic web pages that can grow a large history…
/frameworks/base/docs/html/about/
Dmarketplace.jd45 using rich, colorful product pages that feature app screenshots, videos, and user reviews, as well
/frameworks/base/docs/html/distribute/googleplay/about/
Dvisibility.jd112 users, right from the Apps and Games home pages. The charts are generated
215 <h3 id="details">Rich, colorful product pages</h3>
227 <img src="{@docRoot}images/gp-details-pages-magicpiano.png" style="width:500px">
/frameworks/base/docs/html/tools/extras/
Dsupport-library.jd224 PagerAdapter.getPageTitle()} to supply title strings for pages, which defaults to no
241 <li>Added deferred start for off-screen pages to improve performance.</li>
300 <li>Added support for margins between pages.
305 <li>Added support to control how many pages are kept to either side
/frameworks/base/docs/html/
Dlicense.jd77 by the license unless specifically noted. For example, pages may link to videos or
/frameworks/base/docs/html/training/design-navigation/
Dancestral-temporal.jd68 to navigate between web pages, you may wish to trigger the embedded browser's default <em>back</em>
Ddescendant-lateral.jd158 …plemented by another UI element indicating the current page and available pages, to aid discoverab…
/frameworks/base/docs/html/about/versions/
Dandroid-2.2-highlights.jd172 which enables faster loading of JavaScript-heavy pages.</p>
/frameworks/base/docs/html/training/monetization/
Dads-and-ux.jd104 viewing web pages). Ads also come in different dimensions and shapes. Once you’ve decided to put an
/frameworks/wilhelm/doc/
DDoxyfile1030 # and Class Hierarchy pages using a tree view instead of an ordered list.
1214 # generate man pages
1218 # The MAN_OUTPUT tag is used to specify where the man pages will be put.
1225 # the generated man pages (default is the subroutine's section .3)
1247 # The XML_OUTPUT tag is used to specify where the XML pages will be put.
/frameworks/base/docs/html/guide/topics/ui/
Ddeclaring-layout.jd90 …outs and the screen elements they contain, in the same way you create web pages in HTML &mdash; wi…
389 <p>Displays web pages.</p>
/frameworks/base/docs/html/training/displaying-bitmaps/
Dcache-bitmap.jd136 use around 1.5MB (800*480*4 bytes), so this would cache a minimum of around 2.5 pages of images in

12