| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Change-Id: I1df85b6a954c29344d537737da57683b2c7941fd
|
| |
|
|
|
|
|
| |
add corresponding graffle files
update discussion of activity state restore for clarification
Change-Id: I7c6a68b627b35d0b648fac071a06960a7e833686
|
| |
|
|
|
|
| |
deprecate "optimizing for 3.0" doc
Change-Id: I290ff5cd22c714e639fb820251c9e1d763f750df
|
| |
|
|
|
|
| |
and polish it up
Change-Id: Ie5fb51d6a4109acec6dd403cde2b630df8724bba
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
docs: Rewrite of App Fundamentals.. Part 2.
This introduces three new docs:
Services:
Provides an introduction to using services and describes the
service lifecycle (previously in the "Component Lifecycles" section
of the fundamentals.jd document)
Bound Services:
A guide for services that offer binding.
AIDL:
A doc about using AIDL (primarily for creating a service interface)
Also includes edits to IntentService javadocs to clarify
different behaviors for some callback methods
Includes a new version of the services lifecycle diagram
and an additional diagram for determining onRebind()
These files are orphaned for now---they're not linked in the sidenav,
until I get the last couple documents submitted for the app fundamentals.
Change-Id: I7fb0a8faff1f18b7d6b9a7b59f66f55a1b6168f1
|
|
|
This introduces two new docs:
Activities
Provides a fundamental introduction to how activities work, including
the basics about layout, manifest entries, starting activies, getting results,
and the complete discussion about the lifecycle (which used to be in the
fundamentals.jd document under "Component Lifecycles"), but also now includes more
information about saving instance state (with new diagrams).
Tasks and Back Stack
A large expansion of the material originally presented in the fundamentals.jd
document under "Activities and Tasks". This doc talks all about how tasks and
the back stack work. This content re-organization is important because fragments
can now become a part of the back stack (which is a task-oriented concept), thus,
it's important to separate the task ideas from being tied directly to activities only,
which is how tasks are currently discussed. However, fragments are not yet discussed
here in detail---that will come later when the fragment dev guide is introduced.
Change-Id: I46425b5c2c3b928dc81bafd05a88ad3ea1c5be53
|
