| /frameworks/base/docs/html/guide/practices/design/ |
| index.jd | 6 <p>The documents below help you learn the nuances of Android and get started building great applications more quickly, They discuss important aspects of application design that directly influence the user experience of your application, when in the hands of a mobile device user. You should read and consider these design goals as you plan your application and throughout its development, especially if you are new to developing for mobile devices.</p>
|
| /cts/tools/host/test/com/android/cts/ |
| TestSessionBuilderTests.java | 43 private static final String mTmpPlanFileName = "plan";
77 + "\t<Description>Demo test plan</Description>\n"
160 * Test getting and removing entries from plan file.
171 + "\t<Description>Demo test plan</Description>\n"
256 + "\t<Description>Demo test plan</Description>\n"
333 + "<Description>Demo test plan</Description>\n"
421 * Test loading plan with excluded list from the xml file.
435 + "<Description>Demo test plan</Description>\n"
509 * Test building and loading plan with excluding list of embedded suite.
593 * Test building and loading plan with excluding list of the top suite
[all...] |
| /cts/tools/host/src/com/android/cts/ |
| CommandParser.java | 32 * <li> CommandParser cp = CommandParser.parse("start -plan test_plan")
34 * <li> cp.getValue("-plan") will get "test_plan"
|
| TestPlan.java | 56 * Get test package names via test plan file path.
|
| TestPackage.java | 439 * <li> null: nothing should be added to plan;
440 * <li> list size equals 0: the whole package should be added to plan;
441 * <li> list size greater than 0: the given excluded list should be added to plan.
463 //return null to tell the caller nothing to add to the plan
528 * in the test plan.
[all...] |
| TestSessionLog.java | 37 * Store the information of a test plan.
116 * Get the test plan name.
118 * @return The test plan name.
|
| /external/v8/test/mjsunit/ |
| string-match.js | 84 var stringSample = "A man, a plan, a canal: Panama";
130 ["A", "man", "a", "plan", "a", "canal", "Panama"],
|
| /external/bluetooth/glib/gio/tests/ |
| g-file.c | 420 {"dav://www.gtk.org/plan/", TRUE, TRUE, "dav://www.gtk.org/plan/meetings/20071218.txt", "meetings/20071218.txt"},
421 {"dav://www.gtk.org/plan/meetings", TRUE, TRUE, "dav://www.gtk.org/plan/meetings/20071218.txt", "20071218.txt"},
497 {"dav://www.gtk.org/plan/meetings", FALSE, TRUE, "meetings"},
|
| /external/dbus/doc/ |
| Makefile.in | 234 dbus-specification.xml dbus-test-plan.xml dbus-tutorial.xml \
240 dbus-test-plan.html \
412 @DBUS_XML_DOCS_ENABLED_TRUE@dbus-test-plan.html: dbus-test-plan.xml
|
| dbus-test-plan.xml | 9 <title>D-Bus Test Plan</title>
25 This document tries to explain the details of the test plan for D-Bus
|
| /external/dropbear/libtomcrypt/notes/ |
| tech0003.txt | 9 public key functions. If all you plan on using are the hashes and ciphers than only about 1KB of stack is required
|
| /external/qemu/distrib/sdl-1.2.12/src/video/xbios/ |
| SDL_xbios_centscreen.h | 58 unsigned short plan; /* bitplanes */ member in struct:__anon4519
|
| /external/webkit/WebCore/dom/ |
| Attr.h | 34 // therefore it has to be a fullblown Node. The plan
|
| /packages/wallpapers/Basic/res/values-fr/ |
| strings.xml | 34 <string name="wallpaper_fall_desc" msgid="595888373487204297">"Feuilles d\'automne tombant <br> sur l\'onde de l\'étang :<br> arrière-plan Zen"</string>
|
| /packages/wallpapers/Basic/res/values-tr/ |
| strings.xml | 34 <string name="wallpaper_fall_desc" msgid="595888373487204297">"A?a??da hafifçe dalgalanan gölcü?e<br> Sonbahar yapraklar? dökülüyor:<br> Zen s?v? arka plan"</string>
|
| /development/docs/ |
| howto_SDK_git_cygwin.txt | 56 If you plan to contribute, you might want to get "gitk" also.
96 If you plan on contributing, you will notice that even after a fresh "repo
|
| /frameworks/base/docs/html/guide/tutorials/localization/ |
| index.jd | 15 <li><a href="#plan">Plan the Localization</a></li>
224 <h2 id="plan">Plan the Localization</h2>
225 <p>The first step in localizing an application is to plan how the application
229 plan for how the application will appear in different locales.</p>
310 <p>As shown in the table above, the plan calls for five flag icons in addition
473 the plan is for <code>text_a</code> and <code>text_b</code> to be in Japanese
|
| /frameworks/base/docs/html/resources/articles/ |
| avoiding-memory-leaks.jd | 8 plan on using all of this memory, you should use as little as possible
91 on the activities life cycle. If you plan on keeping long-lived objects
|
| /frameworks/base/docs/html/resources/tutorials/localization/ |
| index.jd | 15 <li><a href="#plan">Plan the Localization</a></li>
224 <h2 id="plan">Plan the Localization</h2>
225 <p>The first step in localizing an application is to plan how the application
229 plan for how the application will appear in different locales.</p>
310 <p>As shown in the table above, the plan calls for five flag icons in addition
473 the plan is for <code>text_a</code> and <code>text_b</code> to be in Japanese
|
| /frameworks/base/telephony/java/com/android/internal/telephony/cdma/sms/ |
| CdmaSmsAddress.java | 75 * Numbering Plan identification is a 0 or 4-bit value that
76 * indicates which numbering plan identification is set. (See
|
| /cts/tools/host/src/res/ |
| cts_result.xsl | 47 <!-- Header with phone and plan information -->
186 <!-- plan information -->
212 <TD class="rowtitle">Plan name</TD>
|
| cts_result.css | 44 /* Device and test plan summary below the title */
|
| /packages/apps/Calendar/res/values-pl/ |
| strings.xml | 42 <string name="show_agenda_view" msgid="7971854300981408347">"Poka? plan dnia"</string>
44 <string name="agenda_view" msgid="5566084759423843245">"Plan dnia"</string>
|
| /dalvik/dx/src/com/android/dx/ssa/back/ |
| FirstFitLocalCombiningAllocator.java | 743 // by source index: set of sources needing moves in high scoring plan
793 * If we were unable to find a plan for a fit centered around
850 * Attempts to build a plan for fitting a range of sources into rop
854 * @param insn {@code non-null;} insn to plan range for
[all...] |
| /development/pdk/docs/compatibility/ |
| cts-intro.jd | 20 <li>Launch the CTS. The CTS test harness loads the test plan onto the attached devices. For each test in the test harness:
|
