Android material design dialog

Material design Dialogs in Android

Aug 17, 2018 · 3 min read

According to material design documentation, “A dialog is a type of modal window that appears in front of app content to provide critical information or ask for a decision. Dialogs disable all app functionality when they appear, and remain on screen until confirmed, dismissed, or a required action has been taken”

How many types of dialogs are possible?

As per my knowledge, it should be four types of dialog:

• Alert Dialog
• Simple Dialog
• Confirmation Dialogs
• Full screen Dialog

Alert Dialog

Alerts are urgent interruptions, requiring acknowledgment, that inform the user about a situation. It’s really easy to create an alert dialog.

How to add?

I. In your build.gradle add latest appcompat library.

II. Make your activity extend android.support.v7.app.AppCompatActivity .

III. To create your dialog use android.support.v7.app.AlertDialog.Builder .

You can remove dialog theme while creating builder also in first line above.

I’ve added it to style it according to my application’s theme, checkout the code here from line 155.

Confirmation Dialog

Confirmation di a logs require users to explicitly confirm their choice before an option is committed. For example, users can listen to multiple ringtones but only make a final selection upon touching “OK.”

• Single choice Dialog
• Multi choice Dialog
• Date Picker
• Time Picker

Single Choice Dialog

• Step I & II is similar to Alert Dialog.
• To create dialog use android.support.v7.app.AlertDialog.Builder . To create dialog with single choice list use method setSingleChoiceItems in your builder object.

Multiple choice dialog

It’s similar to single choice dialog, use method setMultiChoiceItems in your builder object instead of setSingleChoiceItems.

Источник

Material Dialogs

Table of Contents (Core)

Table of Contents (Commons)

Sample Project

It’s also on Google Play:

Having the sample project installed is a good way to be notified of new releases. Although Watching this repository will allow GitHub to email you whenever I publish a release.

Gradle Dependency

Repository

Add this in your root build.gradle file (not your module build.gradle file):

The core module contains all the major classes of this library, including MaterialDialog and AlertDialogWrapper . You can create basic, list, single/multi choice, progress, input, etc. dialogs with core.

Commons

The commons module contains extensions to the library that not everyone may need. This includes the ColorChooserDialog , FolderChooserDialog , the Material Preference classes, and MaterialSimpleListAdapter / MaterialSimpleListItem .

It’s likely that new extensions will be added to commons later.

What’s New

See the project’s Releases page for a list of versions with their changelogs.

View Releases

If you Watch this repository, GitHub will send you an email every time I publish an update.

Basic Dialog

First of all, note that MaterialDialog extends DialogBase , which extends AlertDialog . While a very small number of the stock methods are purposely deprecated and don’t work, you have access to methods such as dismiss() , setTitle() , setIcon() , setCancelable() , etc. Alternatives are discussed below.

Here‘s a basic example that mimics the dialog you see on Google’s Material design guidelines (here: http://www.google.com/design/spec/components/dialogs.html#dialogs-usage). Note that you can always substitute literal strings and string resources for methods that take strings, the same goes for color resources (e.g. titleColor and titleColorRes ).

On Lollipop (API 21+) or if you use AppCompat, the Material dialog will automatically match the positiveColor (which is used on the positive action button) to the colorAccent attribute of your styles.xml theme.

If the content is long enough, it will become scrollable and a divider will be displayed above the action buttons.

Dismissing Dialogs

I‘ve had lots of issues asking how you dismiss a dialog. It works the same way that AlertDialog does, as both AlertDialog and MaterialDialog are an instance of android.app.Dialog (which is where dismiss() and show() come from). You cannot dismiss a dialog using it’s Builder . You can only dismiss a dialog using the dialog itself.

There’s many ways you can get an instance of MaterialDialog . The two major ways are through the show() and build() methods of MaterialDialog.Builder .

Through show() , which immediately shows the dialog and returns the visible dialog:

Through build() , which only builds the dialog but doesn’t show it until you say so:

Once the dialog is shown, you can dismiss it:

There are other various places where the MaterialDialog instance is given, such as in some callbacks that are discussed in future sections below.

Migration from AlertDialogs

If you’re migrating old dialogs you could use AlertDialogWrapper . You need change imports and replace AlertDialog.Builder with AlertDialogWrapper.Builder :

But it’s highly recommended to use original MaterialDialog API for new usages.

Displaying an Icon

MaterialDialog supports the display of an icon just like the stock AlertDialog; it will go to the left of the title.

You can limit the maximum size of the icon using the limitIconToDefaultSize() , maxIconSize(int size) , or maxIconSizeRes(int sizeRes) Builder methods.

Stacked Action Buttons

If you have multiple action buttons that together are too wide to fit on one line, the dialog will stack the buttons to be vertically oriented.

You can also force the dialog to stack its buttons with the forceStacking() method of the Builder .

Neutral Action Button

You can specify neutral text in addition to the positive and negative text. It will show the neutral action on the far left.

Callbacks

As of version 0.8.2.0, the callback() Builder method is deprecated in favor of the individual callback methods discussed below. Earlier versions will still require use of ButtonCallback .

To know when the user selects an action button, you set callbacks:

If you are listening for all three action buttons, you could just use onAny() . The which ( DialogAction ) parameter will tell you which button was pressed.

If autoDismiss is turned off, then you must manually dismiss the dialog in these callbacks. Auto dismiss is on by default.

List Dialogs

Creating a list dialog only requires passing in an array of strings. The callback ( itemsCallback ) is also very simple.

If autoDismiss is turned off, then you must manually dismiss the dialog in the callback. Auto dismiss is on by default. You can pass positiveText() or the other action buttons to the builder to force it to display the action buttons below your list, however this is only useful in some specific cases.

Single Choice List Dialogs

Single choice list dialogs are almost identical to regular list dialogs. The only difference is that you use itemsCallbackSingleChoice to set a callback rather than itemsCallback . That signals the dialog to display radio buttons next to list items.

If you want to preselect an item, pass an index 0 or greater in place of -1 in itemsCallbackSingleChoice() . Later, you can update the selected index using setSelectedIndex(int) on the MaterialDialog instance, if you’re not using a custom adapter.

If you do not set a positive action button using positiveText() , the dialog will automatically call the single choice callback when user presses the positive action button. The dialog will also dismiss itself, unless auto dismiss is turned off.

If you make a call to alwaysCallSingleChoiceCallback() , the single choice callback will be called every time the user selects an item.

Coloring Radio Buttons

Like action buttons and many other elements of the Material dialog, you can customize the color of a dialog‘s radio buttons. The Builder class contains a widgetColor() , widgetColorRes() , and widgetColorAttr() method. Their names and parameter annotations make them self explanatory. Note that by default, radio buttons will be colored with the color held in colorAccent (for AppCompat) or android:colorAccent (for the Material theme) in your Activity’s theme.

There’s also a global theming attribute as shown in the Global Theming section of this README: md_widget_color .

Multi Choice List Dialogs

Multiple choice list dialogs are almost identical to regular list dialogs. The only difference is that you use itemsCallbackMultiChoice to set a callback rather than itemsCallback . That signals the dialog to display check boxes next to list items, and the callback can return multiple selections.

If you want to preselect any items, pass an array of indices (resource or literal) in place of null in itemsCallbackMultiChoice() . Later, you can update the selected indices using setSelectedIndices(Integer[]) on the MaterialDialog instance, if you’re not using a custom adapter.

If you do not set a positive action button using positiveText() , the dialog will automatically call the multi choice callback when user presses the positive action button. The dialog will also dismiss itself, unless auto dismiss is turned off.

If you make a call to alwaysCallMultiChoiceCallback() , the multi choice callback will be called every time the user selects an item.

Coloring Check Boxes

Like action buttons and many other elements of the Material dialog, you can customize the color of a dialog‘s check boxes. The Builder class contains a widgetColor() , widgetColorRes() , and widgetColorAttr() method. Their names and parameter annotations make them self explanatory. Note that by default, check boxes will be colored with the color held in colorAccent (for AppCompat) or android:colorAccent (for the Material theme) in your Activity’s theme.

There’s also a global theming attribute as shown in the Global Theming section of this README: md_widget_color .

Assigning IDs to List Item Views

If you need to keep track of list items by ID rather than index, you can assign item IDs from an integer array:

You can also pass a literal integer array ( int[] ) in place of an array resource ID.

Custom List Dialogs

Like Android’s native dialogs, you can also pass in your own adapter via .adapter() to customize exactly how you want your list to work.

If you need access to the ListView , you can use the MaterialDialog instance:

Note that you don‘t need to be using a custom adapter in order to access the ListView , it’s there for single/multi choice dialogs, regular list dialogs, etc.

Custom Views

Custom views are very easy to implement.

If wrapInScrollView is true, then the library will place your custom view inside of a ScrollView for you. This allows users to scroll your custom view if necessary (small screens, long content, etc.). However, there are cases when you don‘t want that behavior. This mostly consists of cases when you’d have a ScrollView in your custom layout, including ListViews, RecyclerViews, WebViews, GridViews, etc. The sample project contains examples of using both true and false for this parameter.

Your custom view will automatically have padding put around it when wrapInScrollView is true. Otherwise you’re responsible for using padding values that look good with your content.

Later Access

If you need to access a View in the custom view after the dialog is built, you can use getCustomView() of MaterialDialog . This is especially useful if you pass a layout resource to the Builder , the dialog will handle the view inflation for you.

Typefaces

If you want to use custom fonts, you can make a call to typeface(String, String) when using the Builder . This will pull fonts from files in your project’s assets/fonts folder. For example, if you had Roboto.ttf and Roboto-Light.ttf in /src/main/assets/fonts , you would call typeface(«Roboto.ttf», «Roboto-Light.ttf») . This method will also handle recycling Typefaces via the TypefaceHelper which you can use in your own project to avoid duplicate allocations. The raw typeface(Typeface, Typeface) variation will not recycle typefaces, every call will allocate the Typeface again.

There’s a global theming attribute available to automatically apply fonts to every Material Dialog in your app, also.

Getting and Setting Action Buttons

If you want to get a reference to one of the dialog action buttons after the dialog is built and shown (e.g. to enable or disable buttons):

If you want to update the title of a dialog action button (you can pass a string resource ID in place of the literal string, too):

Theming

Before Lollipop, theming AlertDialogs was basically impossible without using reflection and custom drawables. Since KitKat, Android became more color neutral but AlertDialogs continued to use Holo Blue for the title and title divider. Lollipop has improved even more, with no colors in the dialog by default other than the action buttons. This library makes theming even easier.

Basics

By default, Material Dialogs will apply a light theme or dark theme based on the ?android:textColorPrimary attribute retrieved from the context creating the dialog. If the color is light (e.g. more white), it will guess the Activity is using a dark theme and it will use the dialog’s dark theme. Vice versa for the light theme. You can manually set the theme used from the Builder#theme() method:

Or you can use the global theming attribute, which is discussed in the section below. Global theming avoids having to constantly call theme setters for every dialog you show.

Colors

Pretty much every aspect of a dialog created with this library can be colored:

The names are self explanatory for the most part. The widgetColor method, discussed in a few other sections of this tutorial, applies to progress bars, check boxes, and radio buttons. Also note that each of these methods have 3 variations for setting a color directly, using color resources, and using color attributes.

Selectors

Selectors are drawables that change state when pressed or focused.

The first btnSelector line sets a selector drawable used for all action buttons. The second btnSelector line overwrites the drawable used only for the positive button. This results in the positive button having a different selector than the neutral and negative buttons. btnSelectorStacked sets a selector drawable used when the buttons become stacked, either because there’s not enough room to fit them all on one line, or because you used forceStacked(true) on the Builder . listSelector is used for list items, when you are NOT using a custom adapter.

An important note related to using custom action button selectors: make sure your selector drawable references inset drawables like the default ones do — this is important for correct action button padding.

Gravity

It‘s probably unlikely you’d want to change gravity of elements in a dialog, but it’s possible.

These are pretty self explanatory. titleGravity sets the gravity for the dialog title, contentGravity sets the gravity for the dialog content, btnStackedGravity sets the gravity for stacked action buttons, itemsGravity sets the gravity for list items (when you’re NOT using a custom adapter).

For, buttonsGravity refer to this:

With no positive button, the negative button takes it’s place except for with CENTER.

Material Palette

Global Theming

Most of the theming aspects discussed in the above section can be automatically applied to all dialogs you show from an Activity which has a theme containing any of these attributes:

The action button color is also derived from the android:colorAccent attribute of the Material theme, or colorAccent attribute of the AppCompat Material theme as seen in the sample project. Manually setting the color will override that behavior.

Show, Cancel, and Dismiss Callbacks

You can directly setup show/cancel/dismiss listeners from the Builder rather than on the resulting MaterialDialog instance.

Also note that the Builder has a cancelable() method that lets you disable dismissing the dialog when you tap outside the dialog window.

Input Dialogs

An input dialog is pretty self explanatory, it retrieves input from the user of your application with an input field (EditText). You can also display content above the EditText if you desire.

The input dialog will automatically handle focusing the EditText and displaying the keyboard to allow the user to immediately enter input. When the dialog is closed, the keyboard will be automatically dismissed.

Note that the dialog will force the positive action button to be visible, when it’s pressed the input is submitted to the callback.

Also Note that the call to inputType() is optional.

Coloring the EditText

Like action buttons and many other elements of the Material dialog, you can customize the color of a input dialog‘s EditText . The Builder class contains a widgetColor() , widgetColorRes() , and widgetColorAttr() method. Their names and parameter annotations make them self explanatory. Note that by default, EditTexts will be colored with the color held in colorAccent (for AppCompat) or android:colorAccent (for the Material theme) in your Activity’s theme.

There’s also a global theming attribute as shown in the Global Theming section of this README: md_widget_color .

Limiting Input Length

The code below will show a little indicator in the input dialog that tells the user how many characters they‘ve typed. If they type less than 2 characters, or more than 20, the dialog won’t allow the input to be submitted. It will also color the input field and character counter in error color passed for the third parameter.

If you pass 0 for the min length, there will be no min length. If you pass -1 for the max length, there will be no max length. If you don’t pass a third parameter at all, it will default to Material red.

*Note that inputRangeRes(int, int, int) takes a color resource ID for the third parameter, while inputRange(int, int, int) takes a literal color integer for the second parameter. You can use either one, or use the variation that doesn’t take a third parameter at all.

Custom Invalidation

The easiest way to invalidate (enable or disable the EditText based on whether you think the input is acceptable) input dialogs is to call alwaysCallInputCallback() from the Builder so that the callback is invoked every time the user changes their input. From there, you can constantly check what they‘ve typed. If you decide they shouldn’t be able to submit that, you can disable the submit button using this from within the callback:

Progress Dialogs

This library allows you to display progress dialogs with Material design that even use your app’s accent color to color the progress bars (if you use AppCompat to theme your app, or the Material theme on Lollipop).

Proguard

Normally, ObjectAnimator in the context it‘s used in this library (for custom progress drawables) would need special proguard rules so that certain elements aren’t removed when your app is built in release mode. Luckily, AAR packages are allowed to specify proguard rules that get included in apps that depend on them. So you do not need to worry about including any Proguard rules in order to ensure progress bars behave well.

Indeterminate Progress Dialogs

This will display the classic progress dialog with a spinning circle, see the sample project to see it in action:

Determinate (Seek Bar) Progress Dialogs

If a dialog is not indeterminate, it displays a horizontal progress bar that increases up until a max value. The comments in the code explain what this does.

See the sample project for this dialog in action, with the addition of threading.

Make an Indeterminate Dialog Horizontal

By default, indeterminate progress dialogs use a circular progress indicator. From the Builder , you can tell the dialog that it needs to use a horizontal indicator when displaying an indeterminate progress dialog:

Coloring the Progress Bar

Like action buttons and many other elements of the Material dialog, you can customize the color of a progress dialog‘s progress bar. The Builder class contains a widgetColor() , widgetColorRes() , and widgetColorAttr() method. Their names and parameter annotations make them self explanatory. Note that by default, progress bars will be colored with the color held in colorAccent (for AppCompat) or android:colorAccent (for the Material theme) in your Activity’s theme.

There’s also a global theming attribute as shown in the Global Theming section of this README: md_widget_color .

Custom Number and Progress Formats

Like the stock ProgressDialog , you can format the progress min/max numbers and the percentage indicator of determinate dialogs.

The values passed above are the default.

Tint Helper

You can use the MDTintHelper class to dynamically color check boxes, radio buttons, edit texts, and progress bars (to get around not being able to change styles.xml at runtime). It is used in the library to dynamically color UI elements to match your set widgetColor .

If you don’t want the dialog to automatically be dismissed when an action button is pressed or when the user selects a list item:

Color Chooser Dialogs

The Builder is used like this:

The Activity you show the dialog in must implement ColorCallback :

You can also specify custom colors to be displayed if you don’t want to use the built-in primary or accent color palettes (which consist of the entire Material Design Color Palette):

The first parameter for primary colors can also take an array resource ( R.array.colors ), which can be seen in the sample project. If you pass null for the second parameter, there will be no sub levels displayed for top level colors.

Finding Visible Dialogs

Since the ColorChooserDialog is a DialogFragment , it attaches to your Activity through its FragmentManager . ColorChooserDialog has a utility method called findVisible(AppCompatActivity, String) that will find a visible color chooser if any is visible:

User Color Input

By default, color chooser dialogs allow the user to input a custom color using RGB sliders or a Hexadecimal input field. This can be disabled if you don’t want users to be able to use it:

If you want the user to be able to input a custom color, but don’t want them to be able to change transparency (alpha):

Preference Dialogs

Android‘s EditTextPreference , ListPreference , and MultiSelectListPreference allow you to associate a preference activity’s settings with user input that’s received through typing or selection. Material Dialogs includes MaterialEditTextPreference , MaterialListPreference , and MaterialMultiSelectListPreference classes that can be used in your preferences XML to automatically use Material-themed dialogs. See the sample project for details.

By default, all of these preference classes will set their layout to R.layout.md_preference_custom . If you don’t want a default layout to be set, you can provide an attribute on the preferences in your XML:

File Selector Dialogs

The Builder is used like this:

The Activity you show the dialog in must implement FileCallback :

Folder Selector Dialogs

The Builder is used like this:

The Activity you show the dialog in must implement FolderCallback :

Источник