Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit c59662e6 authored by Andrew Solovay's avatar Andrew Solovay Committed by Android Git Automerger
Browse files

am 8722e141: am 4653cdec: am 350286e6: Merge "docs: Clarified when you can put...

am 8722e141: am 4653cdec: am 350286e6: Merge "docs: Clarified when you can put the fragments in the root view." into mnc-preview-docs

* commit '8722e141':
  docs: Clarified when you can put the fragments in the root view.
parents d9f525fb 8722e141
Loading
Loading
Loading
Loading
+1 −5
Original line number Diff line number Diff line
@@ -907,11 +907,7 @@ to ensure the best fit in the action bar.</p>
<p>To get started, your layout must include a {@link android.view.ViewGroup} in which you place
each {@link android.app.Fragment} associated with a tab. Be sure the {@link android.view.ViewGroup}
has a resource ID so you can reference it from your code and swap the tabs within it.
Alternatively, if the tab content will fill the activity layout, then your activity doesn't need a
layout at all (you don't even need to call {@link android.app.Activity#setContentView
setContentView()}). Instead, you can place each fragment in the default root view, which you can
refer to with the {@code android.R.id.content} ID.</p>

</p>

<p>Once you determine where the fragments appear in the layout, the basic procedure to add tabs
is:</p>