List of usage examples for android.support.v4.app FragmentActivity subclass-usage
From source file com.android.messaging.ui.TestActivity.java
/** * An empty activity that can be used to host a fragment or view for unit testing purposes. Lives in * app code vs test code due to requirement of ActivityInstrumentationTestCase2. */ public class TestActivity extends FragmentActivity { private FragmentEventListener mFragmentEventListener;
From source file bander.notepad.PrefsActivity.java
public class PrefsActivity extends FragmentActivity { Fragment myFragment = new PrefsFragment(); @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState);
From source file com.andro_yce.safedelhi.ScreenSlideActivity.java
/**
* Demonstrates a "screen-slide" animation using a {@link ViewPager}. Because {@link ViewPager}
* automatically plays such an animation when calling {@link ViewPager#setCurrentItem(int)}, there
* isn't any animation-specific code in this sample.
*
* <p>This sample shows a "next" button that advances the user to the next step in a wizard,
From source file com.android.quickreturnlistview.sample_app.MainActivity.java
public class MainActivity extends FragmentActivity implements ActionBar.TabListener { private ViewPager mPager; public void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.activity_main);
From source file au.id.tmm.anewreader.view.ItemDetailActivity.java
/** * Activity for displaying actual Items and their content. Implemented using a PagerAdapter * populated with individual Fragments containing the content for an Item. */ public class ItemDetailActivity extends FragmentActivity {
From source file com.a42.cordova.plugins.BaseGameActivity.java
/**
* Example base class for games. This implementation takes care of setting up
* the API client object and managing its lifecycle. Subclasses only need to
* override the @link{#onSignInSucceeded} and @link{#onSignInFailed} abstract
* methods. To initiate the sign-in flow when the user clicks the sign-in
* button, subclasses should call @link{#beginUserInitiatedSignIn}. By default,
From source file br.com.cardapiodigital.ScreenSlideActivity.java
/**
* Demonstrates a "screen-slide" animation using a {@link ViewPager}. Because {@link ViewPager}
* automatically plays such an animation when calling {@link ViewPager#setCurrentItem(int)}, there
* isn't any animation-specific code in this sample.
*
* <p>This sample shows a "next" button that advances the user to the next step in a wizard,
From source file com.arcfighter.basegameutil.BaseGameActivity.java
/**
* Example base class for games. This implementation takes care of setting up
* the API client object and managing its lifecycle. Subclasses only need to
* override the @link{#onSignInSucceeded} and @link{#onSignInFailed} abstract
* methods. To initiate the sign-in flow when the user clicks the sign-in
* button, subclasses should call @link{#beginUserInitiatedSignIn}. By default,
From source file br.com.futuring.cordova.plugins.BaseGameActivity.java
/**
* Example base class for games. This implementation takes care of setting up
* the API client object and managing its lifecycle. Subclasses only need to
* override the @link{#onSignInSucceeded} and @link{#onSignInFailed} abstract
* methods. To initiate the sign-in flow when the user clicks the sign-in
* button, subclasses should call @link{#beginUserInitiatedSignIn}. By default,
From source file at.wada811.android.library.demos.daydream.DayDreamSettingsActivity.java
@TargetApi(Build.VERSION_CODES.JELLY_BEAN_MR1) public class DayDreamSettingsActivity extends FragmentActivity { final DayDreamSettingsActivity self = this; @Override