Lots of clean up on the messaging notification sample to show the real
correct way to do things. Also mark up a bunch of the sample for use
in the documentation.
Change-Id: I3a29a944c2971e142c33b29aff94b1ba0b40ae0e
This avoids everything breaking on pre-ICS platforms.
Also get rid of pref initialization in Application. I hate that. Hate
hate hate. Hate. Totally hate.
Totally.
Change-Id: Idb3526a96eb2dff49f9de8e5ae71149cb4ed6e96
1. Moving Accerssibility Service sample into ApiDemos since
we are putting all accessibility samples there.
2. Fixed regressions (mainly due to adding new event types)
in the Accessibility Service sample.
3. Updated the Query Window Content sample to have some
instructions and to work with touch exploration.
Change-Id: I226ac4130f7f8cae47bb52cbdeab9f104cfaba40
* UI is organized into multiple screens to make it easier to understand
* More feedback about local vs global (aggregate) policies
* Uses preference fragments for modern appearance
Backport of: I075161d389942786e6c95483becbff7ebe847078
Change-Id: Ie88c1577b2ebae124615cc4b45968851cf11187e
* UI is organized into multiple screens to make it easier to understand
* More feedback about local vs global (aggregate) policies
* Uses preference fragments for modern appearance
Change-Id: I075161d389942786e6c95483becbff7ebe847078
* Add Check Password button
* Use it to report overall password status - isActivePasswordSufficient()
and various password settings.
* Fixed a minor bug that cause the password quality to be reset to
"unspecified" every time you start the activity.
* Leave the two password buttons enabled all the time (set password
can be used when not active, and check password just puts up a toast
explaining why it can't be used when inactive.)
This code can be used to confirm bug b/4445007 and hopefully its fix, too.
Change-Id: I136706072257d2e49184a29b0aa5d7a524960c40
Also clean up the demo for the w/h qualifiers to use numbers
that are the same as what we will be recommending.
Change-Id: I87ed35d8dfcb41985e19f450f7853f883effd207
New API demo for the support library FragmentPager class.
Add API demo for new -wNNNdp and -hNNNdp configs.
Add new API demo for implementing a custom loader.
Also turn the fragment cursor list demo into a loader cursor demo.
Move them off into their own directory, so it is less confusing to
find them.
Also put in some additional samples -- throttle and arguments.
And add some docs.
Change-Id: I221e56c7ff203934796979bb5ed7ab8835f84b83
Shows how to make a basic custom theme with a custom background,
and a theme that selects between the old theme and Holo.
Also use a little trick to make the API demos for HC specific
samples be hidden on older versions of the platform.
Change-Id: Ie53e8103147e81975fca73b96bda989a00504534
startDrag() that crosses application boundaries will remain @hide until we get
more of the surrounding behaviors nailed down.
Drag-and-drop demo updated to only show app-local drag operations pro tem.
Change-Id: I9cdcd132c1aae45bc472e70293b7187b4cba9bca
The new sample code is a complete self-contained end-to-end
implementation of a content provider populating a list view
through a loader, dynamically changing its contents based on
user input in about 500 lines.
Once the framework support is implemented, this will demonstrate
using CursorLoader's new throttling feature.
Change-Id: Ia67da7284607477125c613c3135f93bc1d95d0cb
- Rename FragmentAnim to FragmentHideShow, and tweak it to look
less stupid.
- Reworking FragmentLayout to better represent a typical way to
use fragments.
- Tweak various UI elements.
Change-Id: I3f4861c33bafafd27108fe0e4193e0ac7711f69e
Drag/drop among four big dots on screen. Drags to a dot will have
the identity of the originating dot put into a text field below the dots.
In all cases, a text field to the right of the dots reports whether the
drag ended in a successful drop.
Attempting to start a drag from a dot reading "Drag ANR" should ANR and
be cleaned up properly.
Attempting to drop onto a dot reading "Drop ANR" should similarly ANR
and be cleaned up properly.
Drags from a dot labelled "Local" are restricted to targets within
the app's own window -- they are not draggable to the system "shirt
pocket" drop target, etc.
A drop onto the same dot that it originated from will append text to
that effect to the message that notes the dropped payload. This
uses the "local state" convenience mechanism in startDrag() and
DragEvent.getLocalState().
Change-Id: Ic5cd6a29186a84c91d3dc4187e83e7bcf530ba2f
