-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[Spec] AppBar #10774
Comments
i love Transparent appbar |
Do you plan this only for shell? It will be available for the standard navigation page? |
@GiampaoloGabba We have to review and complete more tests, but it could also work outside of Shell. |
Shell only forces the design to use Shell. There are a lot of existing apps which do not use Shell. |
Yupp and don't forget that still a lot of new apps do not use Shell (basically everyone using a MVVM Framework like Prism) |
Support for app bar font icon with bubble text. Something like items in cart... |
It is so good beacause most of modern app have Variable transparent appbar.,i had waited for it long time,finally...we will get item! |
We should add LeftToolbarItems and RightToolbarItems @jsuarezruiz |
@jsuarezruiz it's a very good thing that we keep waiting for several years. |
Please don't tie this to the Shell in any way. The Shell is a template for quite an antiquated app design that forces the usage of tabs, which are not relevant for a whole lot of apps. The AppBar (and any other Xamarin) feature should not have any dependencies to the Shell. |
it's not
No it doesn't. You can structure the shell app to look like a single contenpage, a contentpage with a flyout, a flyout with tabs, etc.. Can you expand on antiquated? |
Sorry I meant flyout, not tabs. It's so heavily centered around that paradigm that it's not useful for much else than apps that gear towards a specific kind of ui with very limited customisation potential. Flyouts and tabs are of course a staple in a lot of apps, but the absolutely most visually appealing apps often don't use them at all. Heck, the shell's documentation itself says "Shell provides an opinionated navigation experience, based on flyouts and tabs". It's cool and all for those that use it, but building new features exclusively for the shell would be detrimental. Good to hear the app bar is not for the shell only, as the initial specification made it look like it would be a shell only feature. Thanks. |
We cut this Spec from the upcoming Forms releases in order to make additional room for the foundational improvements we need to focus on. In order to still ship these controls sooner we are planning to move them to the XamarinCommunityToolkit. We have good momentum there ( insert contributor recruiting pitch ;) ) and I hope this will be a reasonable option during this transitional period. Can follow and comment the Spec in .NET MAUI: dotnet/maui#152 |
I think this is the correct approach. The app bar is something that people can implement by themselves within the existing APIs if really needed, and would pretty much be a custom component. Xamarin.Forms serves best when it exposes any native functionality and does it as solidly and robustly as possible, while matching the feature set of the UWP XAML as closely as possible. Thank you. |
@jsuarezruiz is this something that we can expect in XCT? I saw that TabView was moved there but this wasn't |
AppBar
An app bar consists of a toolbar and potentially other views. Expose one or more actions.
The main benefit of using the appbar is being able to customize everything. Customization options like:
NOTE: AppBar is a cross-platform view that takes over when native navbar hit their limits, such as adding custom content, positioning with layouts, etc.
In Xamarin.Forms, the app bar are typically used in the Shell.AppBar property, which places the app bar as a fixed-height widget at the top of the screen.
API
Next, a list with the AppBar properties and events.
Properties
Events
Scenarios
Let's see some samples covering common scenarios.
Simple app bar
Let's see a basic example:
Custom app bar
Customizing the appearance using a transparent bar with a custom height and custom content (TitleView).
Placement
A top app bar (default placement) displays navigation and actions at the top of mobile screens.
A bottom app bar displays navigation and actions at the bottom of mobile screens.
Using Styles
Can customize the appearance of the tab content, tab strip, tab item, etc. using XAML styles or CSS.
Using XAML:
Using CSS:
Difficulty : Medium
The text was updated successfully, but these errors were encountered: