| /external/antlr/antlr-3.4/antlr3-maven-plugin/src/site/apt/examples/ |
| simple.apt | 3 If your grammar files are organized into the default locations as described in the {{{../index.html}introduction}},
4 then configuring the pom.xml file for your project is as simple as adding this to it
28 Your input files under <<<antlr3>>> should be stored in sub directories that
29 reflect the package structure of your java parsers. If your grammar file parser.g contains:
|
| /external/chromium-trace/catapult/third_party/gsutil/gslib/addlhelp/ |
| subdirs.py | 34 the object gs://your-bucket/abc/def/ghi.txt is just an object that happens to
49 gsutil cp your-file gs://your-bucket/abc/
51 gsutil will create the object gs://your-bucket/abc/your-file.
56 gsutil cp your-file gs://your-bucket/abc
59 object gs://your-bucket/abc/your-file.
65 gsutil cp -r your-dir gs://your-bucket/ab
[all...] |
| /external/littlemock/src/com/google/testing/littlemock/ |
| Captor.java | 25 * Used to automatically inject a {@link ArgumentCaptor} object for use in your tests.
27 * <p>Just annotate your capture field on your test as follows:
33 * done in your setUp() call, or in a test base class) all your capture objects will be
|
| /external/oauth/core/src/main/java/net/oauth/ |
| consumer.properties.sample | 3 ma.gnolia.consumerKey: - Your key here -
4 ma.gnolia.consumerSecret: - Your secret here -
9 twitter.consumerKey: - Your key here -
10 twitter.consumerSecret: - Your secret here -
11 twitter.callbackURL: - Your URL here -
|
| /frameworks/base/docs/html/training/in-app-billing/ |
| list-iab-products.jd | 6 previous.title=Preparing Your In-app Billing Application
32 <p>Before publishing your In-app Billing application, you'll need to define the product list of digital goods available for purchase in the <a href="https://play.google.com/apps/publish/">Google Play Developer Console</a>. </p>
35 <p>From the Developer Console, you can define product information for in-app products and associate the product list with your application.</p>
37 <p>To add new in-app products to your product list:</p>
39 <li>Build a signed APK file for your In-app Billing application. To learn how to build and sign your APK, see <a href="{@docRoot}tools/publishing/preparing.html#publishing-build">Building Your Application for Release</a>. Make sure that you are using your final (not debug) certificate and private key to sign your application.
44 <li>Click on the option to add a new product, then complete the form to specify the product information such as the item?s unique product ID (also called its <em>SKU</em>), description, price, and country availability. Note down the product ID since you might need this information to query purchase details in your application later. <p class="note"><strong>Important:</strong> The In-app Billing Version 3 servic (…)
[all...] |
| preparing-iab-app.jd | 1 page.title=Preparing Your In-app Billing Application
18 <li><a href="#AddToDevConsole">Add Your App to the Developer Console</a></li>
41 <p>Before you can start using the In-app Billing service, you'll need to add the library that contains the In-app Billing Version 3 API to your Android project. You also need to set the permissions for your application to communicate with Google Play. In addition, you'll need to establish a connection between your application and Google Play. You should also verify that the In-app Billing API version that you are using in your application is supported by Google Play.</p>
44 <p>In this training class, you will use a reference implementation for the In-app Billing Version 3 API called the {@code TrivialDrive} sample application. The sample includes convenience classes to quickly set up the In-app Billing service, marshal and unmarshal data types, and handle In-app Billing requests from the main thread of your application.</p>
54 wizard to import the sample to a directory of your choosing. The sample code
63 <h2 id="AddToDevConsole">Add Your Application to the Developer Console</h2>
64 <p>The Google Play Developer Console is where you publish your In-app Billing application and manage the various digital goods that are available for purchase f (…)
[all...] |
| /frameworks/base/docs/html/training/app-indexing/ |
| enabling-app-indexing.jd | 12 <li><a href="#sitemap">Add Deep Links in Your Sitemap</a></li>
13 <li><a href="#webpages">Add Deep Links in Your Web Pages</a></li>
14 <li><a href="#robots">Allow Google to Crawl URLs Requested By Your App</a></li>
27 for the Google search engine, can also index content in your Android app.
31 your existing <a href="https://support.google.com/webmasters/answer/156184?hl=en" class="external-link" target="_blank">Sitemap</a> file or in the {@code <head>} element of each web
32 page in your site, in the same way as you would for web pages.</p>
41 <li><strong>package_name.</strong> Represents the package name for your APK as
43 <li><strong>scheme.</strong> The URI scheme that matches your intent filter.</li>
44 <li><strong>host_path.</strong> Identifies the specific content within your application.
47 <p>The following sections describe how to add a deep link URI to your Sitema
[all...] |
| /frameworks/base/docs/html/distribute/engage/ |
| game-services.jd | 2 page.metaDescription= Bring out the competitor in your users with cloud save, multiplayer game play, and more.
14 <li><a href="#simplify">Simplify your game development</a></li>
16 <li><a href="#socialize">Socialize your games</a></li>
18 <li><a href="#manage">Manage your games</a></li>
25 one the most popular additions to users? devices. Making your games stand out
41 reporting and statistics to help you track and improve your game?s
50 <h3 id="simplify">Simplify your game development</h3>
56 authorizing and authenticating your game.
61 features into your games by using the <a href=
79 time in your games and try new features; reward them with experience point
[all...] |
| /frameworks/base/docs/html/guide/topics/resources/ |
| runtime-changes.jd | 28 android.app.Activity#onCreate(Bundle) onCreate()}). The restart behavior is designed to help your
29 application adapt to new configurations by automatically reloading your application with
32 <p>To properly handle a restart, it is important that your activity restores its previous
37 your activity so that you can save data about the application state. You can then restore the state
41 <p>To test that your application restarts itself with the application state intact, you should
43 tasks in your application. Your application should be able to restart at any time without loss of
45 an incoming phone call and then returns to your application much later after your application
46 process may have been destroyed. To learn how you can restore your activity state, read about the <
[all...] |
| /frameworks/base/docs/html/training/managing-audio/ |
| volume-playback.jd | 1 page.title=Controlling Your App?s Volume and Playback
18 <li><a href="#HardwareVolumeKeys">Use Hardware Volume Keys to Control Your App?s Audio
20 <li><a href="#PlaybackControls">Use Hardware Playback Control Keys to Control Your App?s Audio
34 <p>A good user experience is a predictable one. If your app plays media it?s important that your
35 users can control the volume of your app using the hardware or software volume controls of their
39 playback keys should perform their respective actions on the audio stream used by your app.</p>
45 your app will use.</p>
51 <p>Most of these streams are restricted to system events, so unless your app is a replacement alarm
52 clock, you?ll almost certainly be playing your audio using the {@lin
[all...] |
| /frameworks/base/docs/html/distribute/googleplay/work/ |
| about.jd | 2 page.metaDescription=Distribute your apps directly to enterprises and business users.
11 <p>As a Google Play developer, your free apps are automatically ready to be selected by Android for Work customers and made available to their workforces on Google Play for Work. However, to allow businesses access to bulk purchase your paid apps, you must opt-in and agree to the <a href="https://play.google.com/about/work/developer-distribution-agreement-addendum.html">Google Play for Work Addendum</a> to the Developer Distribution Agreement.</p>
21 <p>Get your business related apps listed in a business specific gateway so they stand out from consumer apps.</p>
23 <p>Reach new audiences at scale because businesses will be able to deploy your free apps in bulk. Bulk purchasing also allows businesses to buy your paid app at scale.</p>
25 <p>You can continue to offer free apps with in-app purchases. Business employees will be able to make purchases just as they would if they personally installed your app. </p>
39 <p>Provides a secure gateway for distributing apps within your company, whether they are available publicly or distributed privately to employees at your organization.</p>
41 <p>Maintain app settings, such as server addresses and default user settings, from your admin console for enabled apps.</p
[all...] |
| /frameworks/base/docs/html/distribute/tools/ |
| open-distribution.jd | 8 As an open platform, Android offers choice. You can distribute your Android
10 combination of approaches that meets your needs. From publishing in an app
11 marketplace to serving your apps from a web site or emailing them directly
16 The process for building and packaging your apps for distribution is the
24 The sections below highlight some of the alternatives for distributing your
37 Usually, to reach the broadest possible audience, you?d distribute your apps
43 useful if you want to distribute your apps to a large global audience.
44 However, you can distribute your apps through any app marketplace you want or
54 helps prevent unauthorized installation and use of your apps.
59 Distributing Your Apps by Emai
[all...] |
| /packages/services/Car/service/res/values/ |
| strings.xml | 18 <!-- Permission text: can access your car's information [CHAR LIMIT=NONE] -->
20 <!-- Permission text: can access your car's information [CHAR LIMIT=NONE] -->
21 <string name="car_permission_desc">Access your car\'s information.</string>
25 <string name="car_permission_desc_camera">Access your car\'s camera(s).</string>
26 <!-- Permission text: can access your car's fuel level [CHAR LIMIT=NONE] -->
28 <!-- Permission text: can access your car's fuel level [CHAR LIMIT=NONE] -->
29 <string name="car_permission_desc_fuel">Access your car\'s fuel level information.</string>
33 <string name="car_permission_desc_hvac">Access your car\'s hvac.</string>
34 <!-- Permission text: can access your car's mileage information [CHAR LIMIT=NONE] -->
36 <!-- Permission text: can access your car's mileage information [CHAR LIMIT=NONE] --
[all...] |
| /developers/build/prebuilts/androidtv/visual-game-controller/ |
| project.properties | 2 # Do not modify this file -- YOUR CHANGES WILL BE ERASED!
7 # "ant.properties", and override values to adapt the script to your
10 # To enable ProGuard to shrink and obfuscate your code, uncomment this (available properties: sdk.dir, user.home):
|
| /external/chromium-trace/catapult/third_party/webapp2/docs/tutorials/gettingstarted/ |
| uploading.rst | 3 Uploading Your Application
6 Console. Once you have registered an application ID for your application, you
7 upload it to your website using ``appcfg.py``, a command-line tool provided
9 your application by clicking the Deploy button.
27 Sign in to App Engine using your Google account. If you do not have a Google
35 also purchase a top-level domain name for your app, or use one that you have
39 setting from ``helloworld`` to your registered application ID.
44 To upload your finished application to Google App Engine, run the following
53 Enter your Google username and password at the prompts.
55 You can now see your application running on App Engine. If you set up a fre
[all...] |
| /external/okhttp/ |
| CONTRIBUTING.md | 9 sure your code compiles by running `mvn clean verify`. Checkstyle failures
10 during compilation indicate errors in your style and can be viewed in the
13 Before your code can be accepted into the project you must also sign the
|
| /external/okhttp/okio/ |
| CONTRIBUTING.md | 9 sure your code compiles by running `mvn clean verify`. Checkstyle failures
10 during compilation indicate errors in your style and can be viewed in the
13 Before your code can be accepted into the project you must also sign the
|
| /external/opencv3/samples/cpp/example_cmake/ |
| CMakeLists.txt | 21 # Add OpenCV headers location to your include paths
24 # Declare the executable target built from your sources
27 # Link your application with OpenCV libraries
|
| /external/selinux/policycoreutils/sepolicy/sepolicy/help/ |
| lockdown_unconfined.txt | 4 By default any system process that is started at boot that do not have SELinux Policy defined for them, run as initrc_t or init_t. These domains are unconfined by SELinux. Other similar processes which do not have SELinux Policy written for them run also unconfined. By disabling the unconfined module moves you closer to what used to be called strict policy, and locks down your machine tighter.
6 Disabling the unconfined module will leave certain unconfined domains running on your system, specifically the unconfined_t user. If you do not
7 want unconfined_t users on your system you would need to remove them from the 'Login Mapping' and Users Screens.
|
| /external/webrtc/talk/app/webrtc/androidtests/ |
| project.properties | 2 # Do not modify this file -- YOUR CHANGES WILL BE ERASED!
7 # "ant.properties", and override values to adapt the script to your
10 # To enable ProGuard to shrink and obfuscate your code, uncomment this (available properties: sdk.dir, user.home):
|
| /external/webrtc/webrtc/examples/androidapp/ |
| project.properties | 2 # Do not modify this file -- YOUR CHANGES WILL BE ERASED!
7 # "ant.properties", and override values to adapt the script to your
10 # To enable ProGuard to shrink and obfuscate your code, uncomment this (available properties: sdk.dir, user.home):
|
| /external/webrtc/webrtc/examples/androidtests/ |
| project.properties | 2 # Do not modify this file -- YOUR CHANGES WILL BE ERASED!
7 # "ant.properties", and override values to adapt the script to your
10 # To enable ProGuard to shrink and obfuscate your code, uncomment this (available properties: sdk.dir, user.home):
|
| /frameworks/base/core/java/android/ |
| package.html | 6 <p>You can use some resources directly from these {@link android.R} classes in your own
7 applications, but you should generally use only resources that you've provided directly in your
10 may change between platform versions, causing unforeseen conflicts with your design. Typically,
|
| /frameworks/base/core/res/assets/webkit/ |
| incognito_mode_start_page.html | 8 won't appear in your browser history or search history, and they won't
9 leave other traces, like cookies, on your device after you close the
19 <li>Malicious software that tracks your keystrokes in exchange for free smileys</li>
|
| /frameworks/base/core/res/res/raw/ |
| incognito_mode_start_page.html | 8 won't appear in your browser history or search history, and they won't
9 leave other traces, like cookies, on your device after you close the
19 <li>Malicious software that tracks your keystrokes in exchange for free smileys</li>
|
