HomeSort by relevance Sort by last modified time
    Searched full:lifecycle (Results 26 - 50 of 335) sorted by null

12 3 4 5 6 7 8 91011>>

  /external/chromium_org/third_party/angle/src/common/
RefCountObject.h 8 // lifecycle support for GL objects using the traditional BindObject scheme, but
  /external/guava/guava/src/com/google/common/util/concurrent/
Service.java 25 * {@link #stop()} lifecycle methods to transfer into and out of this state.
27 * lifecycle of a service is:
85 * Returns the lifecycle state of the service.
119 * The lifecycle states of a service.
  /frameworks/wilhelm/src/android/
AudioRecorder_to_android.h 18 * AudioRecorder lifecycle
MediaPlayer_to_android.h 20 * Player lifecycle
  /packages/apps/Email/emailcommon/src/com/android/emailcommon/
Logging.java 36 * If true, logging regarding UI (such as activity/fragment lifecycle) will be enabled.
  /frameworks/base/docs/html/training/basics/fragments/
creating.jd 32 <p>You can think of a fragment as a modular section of an activity, which has its own lifecycle,
59 key lifecycle methods to insert your app logic, similar to the way you would with an {@link
83 <p>Just like an activity, a fragment should implement other lifecycle callbacks that allow you to
85 between its lifecycle states. For instance, when the activity's {@link
89 <p>More information about the fragment lifecycle and callback methods is available in the <a
  /frameworks/base/docs/html/guide/components/
fragments.jd 13 <li>Fragments have their own lifecycle, state, and back stack</li>
34 <li><a href="#Lifecycle">Handling the Fragment Lifecycle</a>
36 <li><a href="#CoordinatingWithActivity">Coordinating with the activity lifecycle</a></li>
61 modular section of an activity, which has its own lifecycle, receives its own input events, and
65 <p>A fragment must always be embedded in an activity and the fragment's lifecycle is directly
66 affected by the host activity's lifecycle. For example, when the activity is paused, so are all
69 href="{@docRoot}guide/components/activities.html#Lifecycle">lifecycle state</a>), you can
103 activity, side by side, and each fragment has its own set of lifecycle callback methods and handl
    [all...]
activities.jd 27 <li><a href="#Lifecycle">Managing the Activity Lifecycle</a>
29 <li><a href="#ImplementingLifecycleCallbacks">Implementing the lifecycle callbacks</a></li>
72 through the activity's lifecycle callback methods.
79 are all part of the activity lifecycle.</p>
82 including a complete discussion of how the activity lifecycle works, so you can properly manage
91 system calls when the activity transitions between various states of its lifecycle, such as when
109 <p>There are several other lifecycle callback methods that you should use in order to provide a
111 to be stopped and even destroyed. All of the lifecycle callback methods are discussed later, in
112 the section about <a href="#Lifecycle">Managing the Activity Lifecycle</a>.</p
    [all...]
bound-services.jd 25 <li><a href="#Lifecycle">Managing the Lifecycle of a Bound Service</a></li>
91 <p>Be sure to read the section about <a href="#Lifecycle">Managing the Lifecycle of a Bound
92 Service</a>, for more information about the service lifecycle when adding binding to a
608 matching bring-up and tear-down moments of the client's lifecycle. For example:
622 android.app.Activity#onPause onPause()}, because these callbacks occur at every lifecycle transition
641 <h2 id="Lifecycle">Managing the Lifecycle of a Bound Service</h2>
645 to manage the lifecycle of your service if it's purely a boun
    [all...]
  /external/chromium_org/chrome/common/extensions/docs/templates/articles/
app_codelab6_lifecycle.html 1 <h1 id="lab_6_lifecycle">Manage App Lifecycle</h1>
3 <p>Like everything in this world, apps have a lifecycle. They are installed, launched, restarted, suspended when the system needs to free up resources and uninstalled. This lab will show you the basics of the Chrome app lifecycle and how its heart, the event page (aka background script), is used.</p>
10 <p>For simpler apps, the event page listens to the app lifecycle events and reacts appropriately.
11 There are two important lifecycle events, $ref:app.runtime.onLaunched and $ref:app.runtime.onRestarted.</p>
204 <p><a href="app_lifecycle.html">Manage App Lifecycle</a> tutorial</p>
  /development/samples/TicTacToeMain/
_index.html 30 <code>GameActivity</code>, that handles most of the application lifecycle.</p>
38 handles most of the application lifecycle and manages general game play.</li>
  /external/chromium_org/chrome/common/extensions/docs/templates/json/
apps_sidenav.json 47 "title": "5 - Manage App Lifecycle",
97 "title": "App Lifecycle",
intro_tables.json 14 "text": "Manage App Lifecycle"
30 "text": "Manage App Lifecycle"
181 "text": "Manage App Lifecycle"
  /development/samples/training/basic/ActivityLifecycle/src/com/example/android/lifecycle/util/
StatusTracker.java 17 package com.example.android.lifecycle.util;
  /docs/source.android.com/src/devices/tech/test_infra/tradefed/fundamentals/
options.jd 29 interfaces included in the <a href="lifecycle.html">Test Lifecycle</a>, and only when that class is
30 <em>instantiated</em> by the lifecycle machinery.</p>
91 append to fields specified by Lifecycle Objects within each config.</p>
  /external/chromium/chrome/browser/chromeos/login/
cookie_fetcher.h 23 // A CookieFetcher manages its own lifecycle. It deletes itself once it's
  /external/chromium_org/ash/test/
test_system_tray_delegate.h 23 // don't need to care its lifecycle.
  /external/chromium_org/cc/input/
top_controls_manager.h 79 TopControlsManagerClient* client_; // The client manages the lifecycle of
  /external/chromium_org/chrome/common/extensions/api/
app_runtime.idl 5 // Use the <code>chrome.app.runtime</code> API to manage the app lifecycle.
  /external/chromium_org/chrome/renderer/extensions/
chrome_v8_context_set_unittest.cc 16 TEST(ChromeV8ContextSet, Lifecycle) {
  /external/guava/
mvn-deploy.sh 6 # first cleans, then builds the normal lifecycle through compilation
  /frameworks/base/test-runner/src/android/test/
ApplicationTestCase.java 27 * a controlled environment. It provides basic support for the lifecycle of a
31 * <p><b>Lifecycle Support.</b>
34 * In order to support the lifecycle of a Application, this test case will make the
  /frameworks/base/docs/html/guide/topics/resources/
runtime-changes.jd 2 page.tags="activity","lifecycle"
34 href="{@docRoot}guide/components/activities.html#Lifecycle">Activity
35 lifecycle</a>, in which Android calls
47 href="{@docRoot}guide/components/activities.html#Lifecycle">Activity lifecycle</a>.</p>
244 technique an escape from retaining your state during normal activity lifecycle. Not only because
  /external/chromium_org/base/android/java/src/org/chromium/base/
ActivityStatus.java 162 * <a href="http://developer.android.com/guide/components/activities.html#Lifecycle">
163 * Activity Lifecycle
219 * side, hence lifecycle management is greatly simplified.
  /developers/build/prebuilts/gradle/BasicSyncAdapter/BasicSyncAdapterSample/src/main/java/com/example/android/basicsyncadapter/
SyncService.java 32 * manage the lifecycle of our {@link SyncAdapter} and provide a handle to said SyncAdapter to the

Completed in 1491 milliseconds

12 3 4 5 6 7 8 91011>>