/docs/source.android.com/src/compatibility/ |
overview.jd | 20 <p>The Android compatibility program makes it easy for mobile device 62 Ensuring compatibility should be easy and inexpensive to
|
/external/bluetooth/bluedroid/bta/ag/ |
bta_ag_rfc.c | 208 ** Description RFCOMM callback functions. This is an easy way to 226 ** Description RFCOMM data callback functions. This is an easy way to
|
/external/chromium/third_party/libjingle/source/talk/base/ |
task.h | 48 // threads, keeping it easy, keeping it real. :-) It does this by 93 // easy to debug, and fast.
|
/external/chromium_org/chrome/browser/history/ |
scored_history_match.h | 155 // assign it. This allows easy lookups of scores without requiring 165 // it. This allows easy lookups of scores without requiring math.
|
/external/chromium_org/third_party/libjingle/source/talk/base/ |
task.h | 48 // threads, keeping it easy, keeping it real. :-) It does this by 93 // easy to debug, and fast.
|
thread_unittest.cc | 207 // There's no easy way to verify the name was set properly at this time. 230 // There's no easy way to verify the priority was set properly at this time.
|
/external/clang/www/ |
OpenProjects.html | 61 C code. It would be relatively easy to turn this into a JIT compiler using 91 experience -- it should be easy to cross compile applications, install support
|
/external/dexmaker/src/dx/java/com/android/dx/util/ |
FixedSizeList.java | 49 // Easy out. 54 // Another easy out.
|
/external/qemu/distrib/sdl-1.2.15/src/cdrom/macosx/ |
SDL_syscdrom_c.h | 35 not necessarily the first CD-ROM device on the system. (Somewhat easy to fix 65 That's easy, since these volumes have a flag that indicates this special
|
/external/tcpdump/ |
makemib | 41 # by farily easy to rewrite this not to use recursion (and also easy to
|
/frameworks/base/docs/html/google/play/billing/ |
billing_best_practices.jd | 78 which means it is relatively easy for an attacker to reverse engineer your application if you use 113 information, but you do not want to make it easy for a hacker or malicious user to replace the
|
/external/llvm/docs/tutorial/ |
LangImpl8.rst | 26 Part of the idea of this tutorial was to show you how easy and fun it 35 Fortunately, our current setup makes it very easy to add global 49 arrays are very easy and are quite useful for many different 216 Third, it is *possible and easy* to add language-specific optimizations, 218 example, it is easy to add language-specific optimization passes that 259 that they are garbage collected or to allow easy implementation of
|
OCamlLangImpl8.rst | 26 Part of the idea of this tutorial was to show you how easy and fun it 35 Fortunately, our current setup makes it very easy to add global 49 arrays are very easy and are quite useful for many different 216 Third, it is *possible and easy* to add language-specific optimizations, 218 example, it is easy to add language-specific optimization passes that 259 that they are garbage collected or to allow easy implementation of
|
/external/markdown/MarkdownTest/Tests_2004/ |
Markdown Documentation - Syntax.html | 50 <p>Markdown is intended to be as easy-to-read and easy-to-write as is feasible.</p> 75 to insert HTML tags. In my opinion, HTML tags are already easy to 76 insert. The idea for Markdown is to make it easy to read, write, and 138 <p>in your anchor tag <code>href</code> attribute. Needless to say, this is easy to 175 ampersands are <em>always</em> encoded automatically. This makes it easy to use 293 <p>Any decent text editor should make email-style quoting easy. For 521 easy to include example HTML source code using Markdown -- just paste 540 it's also easy to use Markdown to write about Markdown's own syntax.</p> 815 entities automatically, which makes it easy to include example HTM [all...] |
Markdown Documentation - Syntax.text-out | 62 <p>Markdown is intended to be as easy-to-read and easy-to-write as 92 easy to insert. The idea for Markdown is to make it easy to read, 154 this is easy to forget, and is probably the single most common 191 makes it easy to use Markdown to write about HTML code. (As opposed 308 <p>Any decent text editor should make email-style quoting easy. For 533 automatically converted into HTML entities. This makes it very easy 553 This means it's also easy to use Markdown to write about Markdown's 830 HTML entities automatically, which makes it easy to include exampl [all...] |
Markdown Documentation - Syntax.text-res | 62 <p>Markdown is intended to be as easy-to-read and easy-to-write as 92 easy to insert. The idea for Markdown is to make it easy to read, 154 this is easy to forget, and is probably the single most common 191 makes it easy to use Markdown to write about HTML code. (As opposed 308 <p>Any decent text editor should make email-style quoting easy. For 533 automatically converted into HTML entities. This makes it very easy 553 This means it's also easy to use Markdown to write about Markdown's 830 HTML entities automatically, which makes it easy to include exampl [all...] |
/external/markdown/MarkdownTest/Tests_2007/ |
Markdown Documentation - Syntax.html | 50 <p>Markdown is intended to be as easy-to-read and easy-to-write as is feasible.</p> 75 to insert HTML tags. In my opinion, HTML tags are already easy to 76 insert. The idea for Markdown is to make it easy to read, write, and 138 <p>in your anchor tag <code>href</code> attribute. Needless to say, this is easy to 175 ampersands are <em>always</em> encoded automatically. This makes it easy to use 293 <p>Any decent text editor should make email-style quoting easy. For 521 easy to include example HTML source code using Markdown -- just paste 540 it's also easy to use Markdown to write about Markdown's own syntax.</p> 815 entities automatically, which makes it easy to include example HTM [all...] |
/external/markdown/tests/extensions-x-def_list/ |
markdown-syntax.html | 46 <p>Markdown is intended to be as easy-to-read and easy-to-write as is feasible.</p> 67 to insert HTML tags. In my opinion, HTML tags are already easy to 68 insert. The idea for Markdown is to make it easy to read, write, and 117 <p>in your anchor tag <code>href</code> attribute. Needless to say, this is easy to 142 ampersands are <em>always</em> encoded automatically. This makes it easy to use 238 <p>Any decent text editor should make email-style quoting easy. For 413 easy to include example HTML source code using Markdown -- just paste 428 it's also easy to use Markdown to write about Markdown's own syntax.</p> 634 entities automatically, which makes it easy to include example HTM [all...] |
/external/markdown/tests/extensions-x-toc/ |
syntax-toc.html | 34 <p>Markdown is intended to be as easy-to-read and easy-to-write as is feasible.</p> 54 to insert HTML tags. In my opinion, HTML tags are already easy to 55 insert. The idea for Markdown is to make it easy to read, write, and 103 <p>in your anchor tag <code>href</code> attribute. Needless to say, this is easy to 128 ampersands are <em>always</em> encoded automatically. This makes it easy to use 220 <p>Any decent text editor should make email-style quoting easy. For 393 easy to include example HTML source code using Markdown -- just paste 408 it's also easy to use Markdown to write about Markdown's own syntax.</p> 609 entities automatically, which makes it easy to include example HTM [all...] |
/external/markdown/tests/markdown-test/ |
markdown-syntax.html | 46 <p>Markdown is intended to be as easy-to-read and easy-to-write as is feasible.</p> 67 to insert HTML tags. In my opinion, HTML tags are already easy to 68 insert. The idea for Markdown is to make it easy to read, write, and 117 <p>in your anchor tag <code>href</code> attribute. Needless to say, this is easy to 142 ampersands are <em>always</em> encoded automatically. This makes it easy to use 238 <p>Any decent text editor should make email-style quoting easy. For 413 easy to include example HTML source code using Markdown -- just paste 428 it's also easy to use Markdown to write about Markdown's own syntax.</p> 634 entities automatically, which makes it easy to include example HTM [all...] |
/external/llvm/docs/ |
TestSuiteMakefileGuide.rst | 204 program. Though these lines are still drowned in the output, it's easy 220 "``gmake TEST=nightly report``" should work), it is really easy to run 232 and formats them for easy viewing. This consists of two files, a
|
/external/openssh/contrib/caldera/ |
openssh.spec | 3 # because the link appeared broken. The rest is for easy compilation, 183 #leave this line for easy edits. 189 #leave this line for easy edits.
|
/frameworks/base/docs/html/design/patterns/ |
app-structure.jd | 82 <li>If your top level consists of multiple views, make sure that it's easy for the user to navigate between them by adding view controls to your action bar.</li> 94 A calendar is about productivity, so an efficient, easy-to-skim view with higher data density works 107 <p><em>Fixed tabs</em> display top-level views concurrently and make it easy to explore and switch between them. They are always visible on the screen, and can't be moved out of the way like scrollable tabs. <em>Fixed tabs</em> should always allow the user to navigate between the views by swiping left or right on the content area.</p>
|
/sdk/eclipse/plugins/com.android.ide.eclipse.tests/unittests/com/android/ide/eclipse/adt/internal/editors/layout/gle2/ |
ImageUtilsTest.java | 223 // it for BufferedImages (since it's easier; easy image painting, easy scaling, 224 // easy transparency handling, etc). However, this meant that we would need to
|
/cts/tests/res/values/ |
strings.xml | 111 <string name="easy">Easy</string>
|