Android M Preview for developers was released yesterday. As usual, many amazing new features are introduced. I noticed that Snackbar
is one of them.
I have read the document about Snackbar
, from which I learnt that Snackbar is in the library of Android Design Support Library, whose absolute path is android.support.design.widget.Snackbar
.
And the document says that:
Snackbars provide lightweight feedback about an operation. They show a brief message at the bottom of the screen on mobile and lower left on larger devices. Snackbars appear above all other elements on screen and only one can be displayed at a time.
They automatically disappear after a timeout or after user interaction elsewhere on the screen, particularly after interactions that summon a new surface or activity. Snackbars can be swiped off screen.
So, does Snackbar
behave like a Toast
or a Dialog
? Can Snackbars be used in a layout file? How could I use it programmatically?
P.S.:
- Any samples on use of Snackbar will be appreciated.
- Android Design Support Library is a new support library, could somebody show me more details of this library?
I set codeding
On
Activity
you can use:and on
Fragment
:Edit:
For changing background color I use something like this:
And for changing text color (despite theme):
Works like a charm ;-)
It is very simple to make a snackbar in android for 10 second
As for
Snackbar
,it acts like aToast
but is different with aToast
. Snackbars are shown on the bottom of the screen and contain text with an optional single action. They automatically time out after the given time length by animating off the screen. In addition, users can swipe them away before the timeout which is considerably more powerful than toasts, another lightweight feedback mechanism.You can use it programmatically like this:
Note the use of a View in the method of
make()
-Snackbar
will attempt to find it ensure that it is anchored to its bottom.What's more, Android Design Support Library is used for Android 2.1+ (API 7+), which features navigation drawer view, floating labels for editing text, floating action button, snackbar, tabs and something like that.
Navigation View
The navigation drawer can be an important focal point for identity and navigation within your app and consistency in the design here can make a considerable difference in how easy your app is to navigate, particularly for first time users.
NavigationView
makes this easier by providing the framework you need for the navigation drawer as well as the ability to inflate your navigation items through a menu resource.You can use it like this:
As for the drawer menu, it could be:
or:
You’ll get callbacks on selected items by setting a OnNavigationItemSelectedListener using setNavigationItemSelectedListener(). This provides you with the MenuItem that was clicked, allowing you to handle selection events, changed the checked status, load new content, programmatically close the drawer, or any other actions you may want.
Floating labels for editing text
Even the humble
EditText
has room to improve in material design. While anEditText
alone will hide the hint text after the first character is typed, you can now wrap it in aTextInputLayout
, causing the hint text to become a floating label above theEditText
, ensuring that users never lose context in what they are entering. In addition to showing hints, you can also display an error message below theEditText
by callingsetError()
.Floating Action Button
A floating action button is a round button denoting a primary action on your interface. The Design library’s
FloatingActionButton
gives you a single consistent implementation, by default colored using thecolorAccent
from your theme.As
FloatingActionButton
extendsImageView
, you’ll useandroid:src
or any of the methods such assetImageDrawable()
to control the icon shown within theFloatingActionButton
.Tabs
top level navigation pattern is commonly used for organizing different groupings of content. The Design library’s
TabLayout
implements both fixed tabs, where the view’s width is divided equally between all of the tabs, as well as scrollable tabs, where the tabs are not a uniform size and can scroll horizontally.Tabs can be added programmatically:
If you want to use
ViewPager
for horizontal paging between tabs, you can create tabs directly from yourPagerAdapter’s
getPageTitle()
and then connect the two together usingsetupWithViewPager()
. This ensures that tab selection events update theViewPager
and page changes update the selected tab.CoordinatorLayout and the app bar
the Design library introduces
CoordinatorLayout
, a layout which provides an additional level of control over touch events between child views, something which many of the components in the Design library take advantage of. If you try using an AppBarLayout allows yourToolbar
and other views (such as tabs provided byTabLayout
) to react to scroll events in a sibling view marked with a ScrollingViewBehavior. Therefore you can create a layout such as:Now, as the user scrolls the
RecyclerView
, theAppBarLayout
can respond to those events by using the children’s scroll flags to control how they enter (scroll on screen) and exit (scroll off screen).The Design library, AppCompat, and all of the Android Support Library are important tools in providing the building blocks needed to build a modern, great looking Android app without building everything from scratch.
The new
Snackbar
doesn't require Android-M.It is inside the new design support library and you can use it today.
Just update your SDK add this dependency in your code:
You can use a code like this:
It is like a Toast.
To assign an action you have to set the
OnClickListener
.If you would like to change the background color you can use something like this:
If you would like to have some built-in features as the swipe-to-dismiss gesture, or the FAB scrolling up the snackbar, simply having a
CoordinatorLayout
in your view hierarchy.have you seen http://android-developers.blogspot.in/2015/05/android-design-support-library.html?
it summarizes the whole support lib.