HomeSort by relevance Sort by last modified time
    Searched full:production (Results 376 - 400 of 711) sorted by null

<<11121314151617181920>>

  /external/chromium_org/chrome/browser/chromeos/contacts/
gdata_contacts_service_unittest.cc 190 // Missing photos should be allowed, though (as this can occur in production).
  /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/chromeos/dbus/
dbus_thread_manager.cc 233 // The DBusThreadManager implementation used in production.
update_engine_client.cc 73 // The UpdateEngineClient implementation used in production.
  /external/chromium_org/content/browser/download/
base_file_unittest.cc 234 // in production, where we would at least Initialize it.
  /external/chromium_org/content/test/
test_render_view_host.h 218 // production code solely to facilitate testing code.
  /external/chromium_org/net/url_request/
test_url_fetcher_factory.h 68 // Interface for tests to intercept production code classes using URLFetcher.
  /external/chromium_org/sync/internal_api/public/
sync_manager.h 265 // of reasons, e.g. swapping from a test instance to production, or a
  /external/chromium_org/third_party/WebKit/Source/core/loader/
DocumentThreadableLoader.cpp 192 // scheme and not contain the userinfo production. In addition, the redirect response must pass the access control check if the
  /external/chromium_org/third_party/bintrees/
README.txt 192 * status: 5 - Production/Stable
  /external/chromium_org/third_party/libjingle/source/talk/base/
task_unittest.cc 60 // in production code because we haven't yet had occasion to generate
  /external/chromium_org/third_party/re2/re2/
prog.h 308 // It is also recursive, so can't use in production (will overflow stacks).
  /external/chromium_org/third_party/smhasher/src/
Spooky.h 7 // Feb 2 2012: production, same bits as beta
  /external/chromium_org/third_party/tcmalloc/vendor/doc/
heapprofile.html 51 install profiler-linked binaries into a production, running
  /external/chromium_org/tools/checkdeps/
builddeps.py 261 # running production tests, since there are intentional DEPS
  /external/chromium_org/v8/src/platform/
time.cc 392 // be used in production. Its biggest issue is that it is per processor and it
  /external/libvpx/libvpx/examples/includes/geshi/geshi/
visualfoxpro.php 268 'Preview','Primary','Printer','Printquality','Procedures','Production',
  /external/llvm/docs/TableGen/
LangRef.rst 107 TableGen's top-level production consists of "objects".
  /external/protobuf/gtest/scons/
SConscript 247 additional_sources=['../test/production.cc'])
  /external/regex-re2/re2/
prog.h 308 // It is also recursive, so can't use in production (will overflow stacks).
  /external/smack/src/org/jivesoftware/smackx/filetransfer/
FileTransferNegotiator.java 77 * and shouldn't be used as the only transfer method in production systems.
  /frameworks/av/services/camera/libcameraservice/api1/client2/
ZslProcessor.cpp 174 // Create stream for HAL production
ZslProcessor3.cpp 130 // Create stream for HAL production
  /frameworks/base/core/java/android/database/sqlite/
SQLiteOpenHelper.java 48 // We leave this behavior disabled in production because it is inefficient and breaks
  /frameworks/base/core/java/android/view/inputmethod/
InputMethodInfo.java 96 * Caveat: mForceDefault must be false for production. This flag is only for test.

Completed in 650 milliseconds

<<11121314151617181920>>