This website requires JavaScript.
Explore
Help
Sign In
drgreen
/
android_frameworks_base
Watch
1
Star
0
Fork
0
You've already forked android_frameworks_base
Code
Issues
Pull Requests
Actions
Packages
Projects
Releases
Wiki
Activity
android_frameworks_base
/
docs
History
Scott Main
5302798581
Merge "docs: Rewrite of App Fundamentals.. Part 1. 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."
2010-10-05 15:19:27 -07:00
..
html
Merge "docs: Rewrite of App Fundamentals.. Part 1. 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."
2010-10-05 15:19:27 -07:00
docs-documentation-redirect.html
auto import from //depot/cupcake/@135843
2009-03-03 19:31:44 -08:00
docs-redirect-index.html
auto import from //depot/cupcake/@135843
2009-03-03 19:31:44 -08:00
docs-redirect.html
auto import from //depot/cupcake/@135843
2009-03-03 19:31:44 -08:00
docs-samples-redirect.html
auto import from //depot/cupcake/@135843
2009-03-03 19:31:44 -08:00
knowntags.txt
Fix the rest of the javadoc warnings.
2010-09-16 13:38:25 -04:00
overview-ext.html
auto import from //depot/cupcake/@135843
2009-03-03 19:31:44 -08:00