/packages/apps/Exchange/src/com/android/exchange/service/ |
ContactsSyncAdapterService.java | 91 * The missing piece at this point is integration with the push/ping mechanism in EAS; this will
|
/prebuilts/python/darwin-x86/2.7.5/lib/python2.7/idlelib/ |
extend.txt | 74 The final piece of the puzzle is the file "config-extensions.def", which is
|
/prebuilts/python/linux-x86/2.7.5/lib/python2.7/idlelib/ |
extend.txt | 74 The final piece of the puzzle is the file "config-extensions.def", which is
|
/prebuilts/python/darwin-x86/2.7.5/lib/python2.7/test/ |
test_doctest.py | 669 >>> for piece in parser.parse(s): 670 ... if isinstance(piece, doctest.Example): 671 ... print 'Example:', (piece.source, piece.want, piece.lineno) 673 ... print ' Text:', `piece` 684 >>> for piece in parser.get_examples(s): 685 ... print (piece.source, piece.want, piece.lineno [all...] |
/prebuilts/python/linux-x86/2.7.5/lib/python2.7/test/ |
test_doctest.py | 669 >>> for piece in parser.parse(s): 670 ... if isinstance(piece, doctest.Example): 671 ... print 'Example:', (piece.source, piece.want, piece.lineno) 673 ... print ' Text:', `piece` 684 >>> for piece in parser.get_examples(s): 685 ... print (piece.source, piece.want, piece.lineno [all...] |
/external/chromium_org/base/strings/ |
string_piece.h | 6 // A string-like object that points to a sized piece of memory. 405 const StringPiece& piece);
|
/external/chromium_org/chrome/common/extensions/docs/server2/test_data/github_file_system/test_owner/repo/commits/ |
HEAD | 124 "patch": "@@ -1,6 +1,6 @@\n ## Overview of Chrome In App Payments API\n \n-You can use the Chrome In App Payments API (Chrome IAP API) to sell digital and virtual goods within a Chrome App. When you use the Chrome IAP API, the Chrome Wallet App (embedded in Chrome) communicates with the Google Wallet servers and handles all the required checkout details so your app does not have to process any financial transactions. The actual integration work to enable in app payments is similar to using the [Google Wallet digital goods API](https://developers.google.com/commerce/wallet/digital/docs/) for websites except that the Chrome IAP API requires you to embed a piece of JavaScript ([buy.js](https://raw.github.com/GoogleChrome/chrome-app-samples/master/in-app-payments/buy.js)) within your app to trigger the payment flow.\n+You can use the Chrome In-App Payments API (Chrome IAP API) to sell digital and virtual goods within a Chrome App. When you use the Chrome IAP API, the Chrome In-App Payments Service (embedded in Chrome) communicates with the Google Wallet servers and handles all the required checkout details so your app does not have to process any financial transactions. The actual integration work to enable in app payments is similar to using the [Google Wallet digital goods API](https://developers.google.com/commerce/wallet/digital/docs/) for websites except that the Chrome IAP API requires you to embed a piece of JavaScript ([buy.js](https://raw.github.com/GoogleChrome/chrome-app-samples/master/in-app-payments/buy.js)) within your app to trigger the payment flow.\n \n ## Sample app\n Here?s a sample app that calls into the Chrome IAP API and provides options to trigger payments via the sandbox server as well as the production server:"
|
/external/chromium_org/gpu/command_buffer/common/ |
cmd_buffer_common.h | 394 // result a piece at a time to help solve that problem in a generic way. 462 // Gets a piece of a result the service as available.
|
/external/chromium_org/gpu/command_buffer/service/ |
common_decoder_unittest.cc | 400 // Check that we can get a piece. 482 // Check we can get a piece.
|
/external/chromium_org/third_party/mesa/src/src/glsl/ |
ralloc.h | 111 * Resize a piece of ralloc-managed memory, preserving data. 223 * Free a piece of ralloc-managed memory.
|
/external/chromium_org/third_party/openssl/openssl/crypto/rc4/asm/ |
rc4-parisc.pl | 196 or $ix,$acc,$acc ; last piece, no need to dep 216 or $ix,$acc,$acc ; last piece, no need to dep
|
/external/compiler-rt/lib/asan/ |
asan_mac.cc | 212 // If the current piece isn't the runtime library name, 222 // Move on to the next piece.
|
/external/mesa3d/src/glsl/ |
ralloc.h | 111 * Resize a piece of ralloc-managed memory, preserving data. 223 * Free a piece of ralloc-managed memory.
|
/external/openssl/crypto/rc4/asm/ |
rc4-parisc.pl | 196 or $ix,$acc,$acc ; last piece, no need to dep 216 or $ix,$acc,$acc ; last piece, no need to dep
|
/external/proguard/src/proguard/retrace/ |
ReTrace.java | 259 // Copy a literal piece of input line. 315 // Copy the last literal piece of input line.
|
/frameworks/base/docs/html/distribute/googleplay/policies/ |
ip.jd | 61 dramatic or artistic piece of work. As soon as you create an original piece
|
/dalvik/vm/reflect/ |
Reflect.h | 134 * Return an array of Annotation objects for the specified piece. For method
|
/development/samples/BackupRestore/src/com/example/android/backuprestore/ |
MultiRecordExampleAgent.java | 36 * stores each distinct piece of application data in a separate record within
|
/docs/source.android.com/src/devices/tech/test_infra/tradefed/ |
index.jd | 100 trivial to write drivers that can coordinate some external piece of hardware with the test case
|
/external/apache-http/src/org/apache/http/impl/cookie/ |
NetscapeDraftSpec.java | 99 * the HTTP headers a new piece of data which is to be stored by
|
/external/chromium/chrome/browser/autocomplete/ |
autocomplete_edit_view.h | 148 // Every piece of code that can change the edit should call these functions
|
/external/chromium/net/base/ |
escape.h | 65 // you wouldn't want this since it might not be interpreted in one piece
|
/external/chromium/net/tools/dump_cache/ |
url_to_filename_encoder.h | 176 // ",-/", and then rewrites segment to contain just the truncated piece so
|
/external/chromium_org/chrome/browser/history/ |
top_sites.h | 55 // While testing the history system, we want to set the thumbnail to a piece
|
/external/chromium_org/chrome/browser/spellchecker/ |
spellcheck_platform_mac_unittest.cc | 278 {"peice", "piece"},
|