| /frameworks/base/docs/html/training/improving-layouts/ |
| D | optimizing-layout.jd | 40 lead to an excessively deep view hierarchy. Furthermore, nesting several instances of {@link
47 href="{@docRoot}tools/help/hierarchy-viewer.html">Hierarchy Viewer</a> and <a
56 href="{@docRoot}tools/help/hierarchy-viewer.html">Hierarchy Viewer</a> that allows
76 <strong>Load View Hierarchy</strong> to view the layout hierarchy of the selected component. For
80 <img src="{@docRoot}images/training/hierarchy-linearlayout.png" alt="" />
81 <p class="img-caption"><strong>Figure 2.</strong> Layout hierarchy for the layout in figure 1,
86 <img src="{@docRoot}images/training/hierarchy-layouttimes.png" alt="" />
87 <p class="img-caption"><strong>Figure 3.</strong> Clicking a hierarchy node shows its
91 <p style="clear:left">In figure 2, you can see there is a 3-level hierarchy with some problems
110 android.widget.RelativeLayout}, you can see that the layout becomes a 2-level hierarchy. Inspection
[all …]
|
| D | loading-ondemand.jd | 43 or participate in the layout. As such, it's cheap to inflate and cheap to leave in a view hierarchy.
78 hierarchy. It is replaced by the inflated layout and the ID for the root view of that layout is
|
| /frameworks/opt/setupwizard/library/main/src/com/android/setupwizardlib/items/ |
| D | ItemAdapter.java | 35 public ItemAdapter(ItemHierarchy hierarchy) { in ItemAdapter() argument
36 mItemHierarchy = hierarchy; in ItemAdapter()
87 public void onChanged(ItemHierarchy hierarchy) { in onChanged() argument
|
| D | ItemGroup.java | 157 public void onChanged(ItemHierarchy hierarchy) { in onChanged() argument
|
| /frameworks/base/docs/html/training/transitions/ |
| D | overview.jd | 20 <p>To help you animate a change between one view hierarchy and another, Android provides the
28 <dd>Applies one or more animation effects to all of the views in a view hierarchy.</dd>
51 <dd>Defines callbacks that provide finer control over the animation and hierarchy change
64 animates changes to all the views in two view hierarchies. A view hierarchy can be as simple
67 over time between the initial or <em>starting</em> view hierarchy and the final or <em>ending</em>
68 view hierarchy.</p>
94 <p>A scene stores the state of a view hierarchy, including all its views and their property
95 values. A view hierarchy can be a simple view or a complex tree of views and child layouts.
96 Storing the view hierarchy state in a scene enables you to transition into that state from
102 if you generated a view hierarchy dynamically or if you are modifying it at runtime.</p>
[all …]
|
| D | transitions.jd | 140 <p>The framework changes the view hierarchy inside the scene root with the view hierarchy
161 select targets that are part of the view hierarchy associated with a scene.</p>
209 make changes by adding, modifying, and removing child views within the current hierarchy. For
219 hierarchy that you modify in code.</p>
221 <p>If you make changes within the current view hierarchy in this fashion, you do not need to
223 hierarchy using a <em>delayed transition</em>. This feature of the transitions framework
224 starts with the current view hierarchy state, records changes you make to its views, and applies
227 <p>To create a delayed transition within a single view hierarchy, follow these steps:</p>
241 <p>The following example shows how to animate the addition of a text view to a view hierarchy
283 // Start recording changes to the view hierarchy
[all …]
|
| D | scenes.jd | 16 <p>Scenes store the state of a view hierarchy, including all its views and their property
26 hierarchy without using scenes, as described in
35 file. Use this technique when the view hierarchy in the file is mostly static. The resulting
36 scene represents the state of the view hierarchy at the time you created the
37 {@link android.transition.Scene} instance. If you change the view hierarchy, you have to
38 recreate the scene. The framework creates the scene from the entire view hierarchy in the
44 scene root and the resource ID of the layout file that contains the view hierarchy for the
159 <p>To create a scene from a view hierarchy in your code, use the
166 instance from the scene root element and the view hierarchy for the scene in your code:</p>
174 // Obtain the view hierarchy to add as a child of
[all …]
|
| D | index.jd | 68 Learn how to create a scene to store the state of a view hierarchy.
73 Learn how to apply a transition between two scenes of a view hierarchy.
|
| /frameworks/opt/setupwizard/library/full-support/src/com/android/setupwizardlib/items/ |
| D | RecyclerItemAdapter.java | 47 public RecyclerItemAdapter(ItemHierarchy hierarchy) { in RecyclerItemAdapter() argument
48 mItemHierarchy = hierarchy; in RecyclerItemAdapter()
131 public void onChanged(ItemHierarchy hierarchy) { in onChanged() argument
|
| /frameworks/support/design/src/android/support/design/internal/ |
| D | NavigationMenuPresenter.java | 161 SparseArray<Parcelable> hierarchy = new SparseArray<>(); in onSaveInstanceState() local
162 mMenuView.saveHierarchyState(hierarchy); in onSaveInstanceState()
163 state.putSparseParcelableArray(STATE_HIERARCHY, hierarchy); in onSaveInstanceState()
174 SparseArray<Parcelable> hierarchy = state.getSparseParcelableArray(STATE_HIERARCHY); in onRestoreInstanceState() local
175 if (hierarchy != null) { in onRestoreInstanceState()
176 mMenuView.restoreHierarchyState(hierarchy); in onRestoreInstanceState()
|
| /frameworks/base/docs/html/training/design-navigation/ |
| D | index.jd | 24 <p>This class shows you how to plan out the high-level screen hierarchy for your application and th…
39 …r allowing users to navigate deep into, as well as across, your content hierarchy. Also learn abou…
42 <dd>Learn how to allow users to navigate upwards in the content hierarchy. Also learn about best
|
| D | ancestral-temporal.jd | 33 screen hierarchy, we need to provide a method for navigating up the hierarchy, to parent and
81 hierarchy, generally known as the application's home screen.</p>
87 be taken to the parent screen in the hierarchy. This navigation step is usually the previous screen
|
| /frameworks/base/docs/html/guide/topics/ui/ |
| D | overview.jd | 18 <p>The user interface for each component of your app is defined using a hierarchy of {@link
22 draw some part of the UI. This hierarchy tree can be as simple or complex as you need
26 <p class="img-caption"><strong>Figure 1.</strong> Illustration of a view hierarchy, which defines a
|
| /frameworks/base/docs/html/training/basics/activity-lifecycle/ |
| D | recreating.jd | 92 view hierarchy, such as the text in an {@link android.widget.EditText} widget or the scroll position
110 // Always call the superclass so it can save the view hierarchy state
117 can save the state of the view hierarchy.</p>
164 // Always call the superclass so it can restore the view hierarchy
175 can restore the state of the view hierarchy.</p>
|
| /frameworks/base/docs/html/guide/topics/ui/accessibility/ |
| D | apps.jd | 24 <li><a href="#virtual-hierarchy">Providing a customized accessibility context</a></li>
486 are used by accessibility services to investigate the view hierarchy that generated an accessibility
542 <h3 id="virtual-hierarchy">Providing a customized accessibility context</h3>
545 inspect the containing view hierarchy of a user interface component that generates an
550 from the view hierarchy. An example of this is a custom interface control that has two or more
552 adequate information because the clickable subsections are not part of the view hierarchy.</p>
568 the framework provides a way to specify a virtual view hierarchy. A <em>virtual view
569 hierarchy</em> is a way for application developers to provide a complementary view hierarchy
573 <p>Another situation where a virtual view hierarchy may be needed is a user interface containing
579 provide a virtual view hierarchy from this container to clearly represent the information and
[all …]
|
| D | checklist.jd | 124 <a href="{@docRoot}guide/topics/ui/accessibility/apps.html#virtual-hierarchy">virtual
125 view hierarchy</a> for your control using
161 <a href="{@docRoot}guide/topics/ui/accessibility/apps.html#virtual-hierarchy">virtual view
162 … hierarchy</a> for your control using {@link android.view.accessibility.AccessibilityNodeProvider}
|
| /frameworks/base/docs/html/training/custom-views/ |
| D | optimizing-view.jd | 53 requestLayout()}, the Android UI system needs to traverse the entire view hierarchy to find out how
55 to be. If it finds conflicting measurements, it may need to traverse the hierarchy multiple times.
|
| /frameworks/base/docs/html-intl/intl/ru/training/basics/activity-lifecycle/ |
| D | recreating.jd | 109 // Always call the superclass so it can save the view hierarchy state
163 // Always call the superclass so it can restore the view hierarchy
|
| /frameworks/base/docs/html-intl/intl/ja/training/basics/activity-lifecycle/ |
| D | recreating.jd | 109 // Always call the superclass so it can save the view hierarchy state
163 // Always call the superclass so it can restore the view hierarchy
|
| /frameworks/base/docs/html-intl/intl/ko/training/basics/activity-lifecycle/ |
| D | recreating.jd | 109 // Always call the superclass so it can save the view hierarchy state
163 // Always call the superclass so it can restore the view hierarchy
|
| /frameworks/base/docs/html-intl/intl/zh-tw/training/basics/activity-lifecycle/ |
| D | recreating.jd | 109 // Always call the superclass so it can save the view hierarchy state
163 // Always call the superclass so it can restore the view hierarchy
|
| /frameworks/base/docs/html-intl/intl/zh-cn/training/basics/activity-lifecycle/ |
| D | recreating.jd | 109 // Always call the superclass so it can save the view hierarchy state
163 // Always call the superclass so it can restore the view hierarchy
|
| /frameworks/base/docs/html/design/patterns/ |
| D | navigation.jd | 33 between screens, rather than the app's hierarchy.</p>
52 <p>Sometimes a screen doesn't have a strict position within the app's hierarchy, and can be reached
58 in the same place within the app's hierarchy, and no new navigation history is created.</p>
94 deep within your app's hierarchy. For example, Gmail's Inbox widget and new message notification can
210 <p>When your app registers to handle intents with an activity deep within the app's hierarchy,
|
| /frameworks/base/docs/html/training/implementing-navigation/ |
| D | descendant.jd | 39 <p><em>Descendant navigation</em> is navigation down the application's information hierarchy. This …
53 <p>There are cases where descending into your application's information hierarchy leads to activiti…
|
| /frameworks/base/docs/html/guide/topics/ui/layout/ |
| D | relative.jd | 28 because it can eliminate nested view groups and keep your layout hierarchy flat, which improves
72 view declared in the hierarchy. The example below demonstrates such a scenario.</p>
|