blocks|key|144511|text|解释：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|144512|您应该开始使用ToolBar而不是ActionBar。这直接取自Android开发人员文档。它允许比普通的ActionBar更灵活；但是，保留了一些更突出的功能，如添加徽标，支持“向上”导航，膨胀菜单和操作视图，如SearchView。|offset|length|style|CODE|BOLD|144513|教程：|144514|Implement+yourself(by+Chris+Banes)|144515|Collapsing+Toolbar,+FloatingActionButton,+NavigationView,+Snackbar(by+Chris+Banes)|144516|文档：|144517|Normal+Toolbar(API+21%2B)|144518|AppCompat+Support+v7+Toolbar(API+7%2B)|144519|144520|在应用程序内容中使用的标准工具栏。|blockquote|144521|144522|工具栏是在应用程序布局中使用的动作栏的泛化。虽然动作栏传统上是由框架控制的活动的不透明窗口装饰的一部分，但工具栏可以放置在视图层次结构内的任意嵌套级别。应用程序可以选择使用setActionBar()方法将工具栏指定为活动的操作栏。|144523|工具栏支持比ActionBar更集中的功能集。从头到尾，工具栏可能包含以下可选元素的组合：|144524|一个导航按钮。这可能是一个向上箭头，导航菜单切换，关闭，折叠，完成或应用程序选择的另一个字形。此按钮应始终用于访问工具栏容器中的其他导航目的地及其表示的内容，或者以其他方式离开工具栏表示的当前上下文。|144525|品牌徽标图像。此图像可以延伸到条形的高度，并且可以是任意宽度。|144526|标题和副标题。标题应该是工具栏在导航层次结构中的当前位置和包含的内容的路标。副标题(如果存在)应指示有关当前内容的任何扩展信息。如果应用程序使用徽标图像，它应该强烈考虑省略标题和副标题。|144527|一个或多个自定义视图。应用程序可以添加任意的子视图到工具栏。它们将出现在布局中的此位置。如果子视图的Toolbar.LayoutParams指示重力值为CENTER_HORIZONTAL，则在测量完所有其他元素后，视图将尝试在工具栏中剩余的可用空间内居中。|144528|操作菜单。操作菜单将固定在工具栏的末尾，提供一些常见的、重要的或典型的操作，以及一个用于其他操作的可选溢出菜单。在现代的Android+UI中，开发人员应该更多地依赖于工具栏的视觉上不同的配色方案，而不是他们的应用程序图标。在API21和更新版本的设备上，不鼓励使用应用程序图标加标题作为标准布局。|144529|entityMap|0|LINK|mutability|MUTABLE|url|https://chris.banes.me/2014/10/17/appcompat-v21/|1|https://github.com/chrisbanes/cheesesquare|2|http://developer.android.com/reference/android/widget/Toolbar.html|3|http://developer.android.com/reference/android/support/v7/widget/Toolbar.html^0|0|7|7|H|9|1H|9|2C|2|2O|4|2T|4|0|0|0|Y|0|0|K|K|16|E|1M|8|0|2A|1|0|0|7|7|0|N|2|0|L|7|0|10|3|0|0|0|0|0|3|0|0|0|7|0|0|7|0|0|7|0|0|B|0|0|5|0^^$0|@$1|2|3|4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1S|8|@$D|1T|E|1U|F|G]|$D|1V|E|1W|F|G]|$D|1X|E|1Y|F|G]|$D|1Z|E|20|F|H]|$D|21|E|22|F|H]|$D|23|E|24|F|H]]|9|@]|A|$]]|$1|I|3|J|5|6|7|25|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|26|8|@]|9|@$D|27|E|28|1|29]]|A|$]]|$1|M|3|N|5|6|7|2A|8|@$D|2B|E|2C|F|G]|$D|2D|E|2E|F|G]|$D|2F|E|2G|F|G]]|9|@$D|2H|E|2I|1|2J]]|A|$]]|$1|O|3|P|5|6|7|2K|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|2L|8|@$D|2M|E|2N|F|G]]|9|@$D|2O|E|2P|1|2Q]]|A|$]]|$1|S|3|T|5|6|7|2R|8|@$D|2S|E|2T|F|G]]|9|@$D|2U|E|2V|1|2W]]|A|$]]|$1|U|3|-4|5|6|7|2X|8|@]|9|@]|A|$]]|$1|V|3|W|5|X|7|2Y|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|2Z|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|30|8|@$D|31|E|32|F|H]]|9|@]|A|$]]|$1|11|3|12|5|6|7|33|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|34|8|@$D|35|E|36|F|H]]|9|@]|A|$]]|$1|15|3|16|5|6|7|37|8|@$D|38|E|39|F|H]]|9|@]|A|$]]|$1|17|3|18|5|6|7|3A|8|@$D|3B|E|3C|F|H]]|9|@]|A|$]]|$1|19|3|1A|5|6|7|3D|8|@$D|3E|E|3F|F|H]]|9|@]|A|$]]|$1|1B|3|1C|5|6|7|3G|8|@$D|3H|E|3I|F|H]]|9|@]|A|$]]|$1|1D|3|-4|5|6|7|3J|8|@]|9|@]|A|$]]]|1E|$1F|$5|1G|1H|1I|A|$1J|1K]]|1L|$5|1G|1H|1I|A|$1J|1M]]|1N|$5|1G|1H|1I|A|$1J|1O]]|1P|$5|1G|1H|1I|A|$1J|1Q]]]]

<h2>Explanation:</h2>

You should start using a <code>ToolBar</code> instead of the <code>ActionBar</code>. This is directly taken from the Android Developer documentation. It allows more flexibility than the normal <code>ActionBar</code>; however, retains some the more prominent features such as adding a Logo, supports "up" Navigation, inflating menus and actionviews such as the SearchView.

<h2>Tutorials:</h2>

<a href="https://chris.banes.me/2014/10/17/appcompat-v21/">Implement yourself(by Chris Banes)</a>

<a href="https://github.com/chrisbanes/cheesesquare">Collapsing Toolbar, <code>FloatingActionButton</code>, <code>NavigationView</code>, <code>Snackbar</code>(by Chris Banes)</a>

<h2>Documentation:</h2>

<a href="http://developer.android.com/reference/android/widget/Toolbar.html">Normal <code>Toolbar</code>(API 21+)</a>

<a href="http://developer.android.com/reference/android/support/v7/widget/Toolbar.html">AppCompat Support v7 <code>Toolbar</code>(API 7+)</a>

<blockquote>
 A standard toolbar for use within application content.
 
 A Toolbar is a generalization of action bars for use within
 application layouts. While an action bar is traditionally part of an
 Activity's opaque window decor controlled by the framework, a Toolbar
 may be placed at any arbitrary level of nesting within a view
 hierarchy. An application may choose to designate a Toolbar as the
 action bar for an Activity using the setActionBar() method.
 
 Toolbar supports a more focused feature set than ActionBar. From start
 to end, a toolbar may contain a combination of the following optional
 elements:
 
 A navigation button. This may be an Up arrow, navigation menu toggle,
 close, collapse, done or another glyph of the app's choosing. This
 button should always be used to access other navigational destinations
 within the container of the Toolbar and its signified content or
 otherwise leave the current context signified by the Toolbar. 
 
 A branded logo image. This may extend to the height of the bar and can
 be arbitrarily wide. 
 
 A title and subtitle. The title should be a
 signpost for the Toolbar's current position in the navigation
 hierarchy and the content contained there. The subtitle, if present
 should indicate any extended information about the current content. If
 an app uses a logo image it should strongly consider omitting a title
 and subtitle. 
 
 One or more custom views. The application may add
 arbitrary child views to the Toolbar. They will appear at this
 position within the layout. If a child view's Toolbar.LayoutParams
 indicates a Gravity value of CENTER_HORIZONTAL the view will attempt
 to center within the available space remaining in the Toolbar after
 all other elements have been measured. 
 
 An action menu. The menu of
 actions will pin to the end of the Toolbar offering a few frequent,
 important or typical actions along with an optional overflow menu for
 additional actions. In modern Android UIs developers should lean more
 on a visually distinct color scheme for toolbars than on their
 application icon. The use of application icon plus title as a standard
 layout is discouraged on API 21 devices and newer.
</blockquote>

I just read about the new Toolbar in Android Lollipop.
It inherits from ViewGroup.

Why are the advantages of using the new Toolbar over, say, a LinearLayout
to place your own views?

Android Lollipop Toolbar vs Custom view

Android

容器

我刚读到Android棒棒糖的新工具栏。它继承自ViewGroup。为什么使用新的工具栏比使用LinearLayout放置自己的视图更有优势？

问Android棒棒糖工具栏vs自定义视图
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Android棒棒糖工具栏vs自定义视图EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Android棒棒糖工具栏vs自定义视图
EN