説明なし

Aidan Follestad 780d62350f Release 0.4.7 10 年 前
gradle 5e8b31e8d4 Updates for Gradle stuff. 10 年 前
library 780d62350f Release 0.4.7 10 年 前
sample 780d62350f Release 0.4.7 10 年 前
.gitignore ec486efaa4 Updated dependencies and ignored/removed unneeded *.iml files from all folders 10 年 前
LICENSE.txt 95613c86bd Update LICENSE.txt 10 年 前
README.md 780d62350f Release 0.4.7 10 年 前
build.gradle 74d09ad5eb Release 0.4.4. See README for changelog. 10 年 前
gradlew b27b2168af Rebased repo. 10 年 前
gradlew.bat b27b2168af Rebased repo. 10 年 前
settings.gradle b27b2168af Rebased repo. 10 年 前
versions.properties 946cd4c2dc Updated Gradle version to 1.0.0 for official Android Studio release. 10 年 前

README.md

Material Dialogs

The code you see below is also found in the sample project. You can download a APK of the sample here: https://github.com/afollestad/material-dialogs/blob/master/sample/sample.apk. The sample's also available on Google Play: https://play.google.com/store/apps/details?id=com.afollestad.materialdialogssample.


What's New

Version 0.4.7
  1. Yet more fixes thanks to a pull request from hzsweers, see the pull request here.
  2. Note that the 3 variations of the action callbacks are deprecated and replaced with the single ButtonCallback interface.
  3. A fix for action button text styling on Lollipop, thanks plusCubed!
  4. Other fixes and improvements.
Version 0.4.6
  1. Some fixes thanks to a pull request from hzsweers, see the pull request here.
  2. The ability to force the action buttons to be stacked (see the Misc. section).
Version 0.4.5
  1. Crash fix for Huawei devices
  2. Removed some unnecessary logging.
  3. New methods in MaterialDialogCompat.Builder
  4. Other crash fixes and improvements.
Version 0.4.4
  1. Memory management improvements for Typefaces (thanks Kevin Barry of Nova Launcher!)
  2. Added dismiss, cancel, and show listener methods to the Builder.
Version 0.4.1 – 0.4.3
  1. Added md_item_color attribute to global theming.
  2. Added md_icon attribute to global theming.
  3. Fixed a crash bug on pre-Lollipop devices related to list dialogs.
  4. Fixed list item default color on dark dialogs for pre-Lollipop.
  5. Fixes to action button insets, and the stacking algorithm. Thanks plusCubed!
  6. Major padding/margin fixes for using an icon with list dialogs.
Version 0.4.0
  1. Yet more bug fixes and improvements throughout
  2. Action button selectors have rounded corners
  3. More global theming capabilities. Override the accent color used for action buttons, titles, and content from your Activity theme. See the Global Theming section below.
Version 0.3.5 – 0.3.6
  1. Bug fixes.
  2. Button stacking algorithm fixes.
Version 0.3.1 – 0.3.4
  1. Global theming! A single attribute can be added to your Activity theme to make all dialogs dark. See the Global Theming section below.
  2. Large performance improvements for list dialogs, thanks hzsweers! The item processor API was switched with custom list adapters, see the sample for an example.
  3. Other padding and logic fixes.
  4. Crash fix when updating list items after they had previously been set.
  5. The ability to set the content color when constructing a dialog builder.
Version 0.3.0
  1. MaterialDialogCompat allows easy migration from use of AlertDialog (see below).
  2. Convenience show() method in Builder, to skip call to build().
  3. Various important fixes from pull requests and the maintainer.

Gradle Dependency (jCenter)

Easily reference the library in your Android projects using this dependency in your module's build.gradle file:

dependencies {
    compile 'com.afollestad:material-dialogs:0.4.7'
}

Make sure you're using the jCenter repository, Android Studio uses this repository by default.

Check back here frequently for version updates.


Basic Dialog

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).

new MaterialDialog.Builder(this)
        .title("Use Google's Location Services?")
        .content("Let Google help apps determine location. This means sending anonymous location data to Google, even when no apps are running.")
        .positiveText("Agree")
        .negativeText("Disagree")
        .show();

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 displayde above the action buttons.


Migration from AlertDialogs

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

MaterialDialogCompat.Builder dialogBuilder = new MaterialDialogCompat.Builder(context);
dialogBuilder.setMessage(messageId);
dialogBuilder.setTitle(titleId);
dialogBuilder.setNegativeButton(R.string.OK, new DialogInterface.OnClickListener() {
    @Override
    public void onClick(DialogInterface dialog, int which) {
        dialog.dismiss();
        if (listener != null) {
            listener.onCancel(dialog);
        }
    }
});
dialogBuilder.create().show();

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.

Drawable d = // ... get from somewhere...
new MaterialDialog.Builder(this)
        .title("Use Google's Location Services?")
        .content("Let Google help apps determine location. This means sending anonymous location data to Google, even when no apps are running.")
        .positiveText("Agree")
        .icon(d)
        .show();

You can substitute a Drawable instance of a drawable resource ID or attribute ID.


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 orientated.

new MaterialDialog.Builder(this)
        .title("Use Google's Location Services?")
        .content("Let Google help apps determine location. This means sending anonymous location data to Google, even when no apps are running.")
        .positiveText("Turn on speed boost right now!")
        .negativeText("No thanks")
        .show();

If you have multiple action buttons, and together they're too long to fit on one line, the dialog will stack the buttons automatically.


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.

new MaterialDialog.Builder(this)
        .title("Use Google's Location Services?")
        .content("Let Google help apps determine location. This means sending anonymous location data to Google, even when no apps are running.")
        .positiveText("Agree")
        .negativeText("Disagree")
        .neutralText("More info")
        .show();

Callbacks

To know when the user selects an action button, you set a callback. To do this, use the ButtonCallback class and override its onPositive(), onNegative(), or onNeutral() methods as needed. The advantage to this is that you can override button functionality À la carte, so no need to stub empty methods.

new MaterialDialog.Builder(this)
        .callback(new MaterialDialog.ButtonCallback() {
            @Override
            public void onPositive(MaterialDialog dialog) {
            }
        });

new MaterialDialog.Builder(this)
        .callback(new MaterialDialog.ButtonCallback() {
            @Override
            public void onPositive(MaterialDialog dialog) {
            }

            @Override
            public void onNegative(MaterialDialog dialog) {
            }
        });

new MaterialDialog.Builder(this)
        .callback(new MaterialDialog.ButtonCallback() {
            @Override
            public void onPositive(MaterialDialog dialog) {
            }

            @Override
            public void onNegative(MaterialDialog dialog) {
            }

            @Override
            public void onNeutral(MaterialDialog dialog) {
            }
        });

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.

new MaterialDialog.Builder(this)
        .title("Social Networks")
        .items(new String[]{"Twitter", "Google+", "Instagram", "Facebook"})
        .itemsCallback(new MaterialDialog.ListCallback() {
            @Override
            public void onSelection(MaterialDialog dialog, View view, int which, CharSequence text) {
            }
        })
        .show();

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.

This also makes it so that an action button has to be pressed, tapping a list item won't dismiss the dialog. Note that this means the positive action button callback will be overridden if you specify one.

new MaterialDialog.Builder(this)
        .title("Social Networks")
        .items(new String[]{"Twitter", "Google+", "Instagram", "Facebook"})
        .itemsCallbackSingleChoice(-1, new MaterialDialog.ListCallback() {
            @Override
            public void onSelection(MaterialDialog dialog, View view, int which, CharSequence text) {
            }
        })
        .positiveText("Choose")
        .show();

If you want to preselect an item, pass an index 0 or greater in place of -1 in itemsCallbackSingleChoice(). If autoDismiss is turned off, then you must manually dismiss the dialog in the callback. Auto dismiss is on by default. When positiveText() is not used, the callback will be called every time you select an item since no action is available to press, without the dialog being dismissed. 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.


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.

This also makes it so that an action button has to be pressed, tapping a list item won't dismiss the dialog. Note that this means the positive action button callback will be overridden if you specify one.

new MaterialDialog.Builder(this)
        .title("Social Networks")
        .items(new String[]{"Twitter", "Google+", "Instagram", "Facebook"})
        .itemsCallbackMultiChoice(null, new MaterialDialog.ListCallbackMulti() {
            @Override
            public void onSelection(MaterialDialog dialog, Integer[] which, CharSequence[] text) {
            }
        })
        .positiveText("Choose")
        .show();

If you want to preselect item(s), pass an array of indices in place of null in itemsCallbackSingleChoice(). For an example, new Integer[] { 2, 5 }. If autoDismiss is turned off, then you must manually dismiss the dialog in the callback. Auto dismiss is on by default. When action buttons are not added, the callback will be called every time you select an item since no action is available to press, without the dialog being dismissed. 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.


If you want to preselect item(s), pass an array of indices in place of null in itemsCallbackSingleChoice(). For an example, new Integer[] { 2, 5 }. If autoDismiss is turned off, then you must manually dismiss the dialog in the callback. Auto dismiss is on by default. When action buttons are not added, the callback will be called every time you select an item since no action is available to press, without the dialog being dismissed. 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.


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. You also have access to the dialog's list via getListView() method.

MaterialDialog dialog = new MaterialDialog.Builder(this)
        .title(R.string.socialNetworks)
        .adapter(new ButtonItemAdapter(this, R.array.socialNetworks))
        .build();

ListView listView = dialog.getListView();
if (listView != null) {
    listView.setOnItemClickListener(new AdapterView.OnItemClickListener() {
        @Override
        public void onItemClick(AdapterView<?> parent, View view, int position, long id) {
            Toast.makeText(MainActivity.this, "Clicked item " + position, Toast.LENGTH_SHORT).show();
        }
    });
}

dialog.show();

Custom Views

Custom views are very easy to implement. To match the dialog show here: http://www.google.com/design/spec/components/dialogs.html#dialogs-behavior

new MaterialDialog.Builder(this)
        .title("Google Wifi")
        .customView(R.layout.custom_view)
        .positiveText("Connect")
        .positiveColor(Color.parseColor("#03a9f4"))
        .build()
        .show();

Where custom_view.xml contains a LinearLayout of TextViews, an EditText, and a CheckBox. You'll see in the sample project that you don't need to add padding to the edges of your custom view, the dialog already does that. Note that your custom view's top and bottom margins will be overrided; if your custom view is a ViewGroup (e.g. a LinearLayout or RelativeLayout), then the first and last child's top and bottom will be overided.

MaterialDialog inserts your view into a ScrollView and displays a divider above the action buttons, so don't wrap your custom view in a scroll view and don't worry about it being too long or needing a divider. However, you should avoid making any content that wouldn't belong in a dialog because of its size.

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.


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. Here's a basic example:

final int materialRed500 = Color.parseColor("#D50000");
new MaterialDialog.Builder(this)
        .title("Use Google's Location Services?")
        .content("Let Google help apps determine location. This means sending anonymous location data to Google, even when no apps are running.")
        .positiveText("Agree")
        .negativeText("Disagree")
        .positiveColor(materialRed500)
        .negativeColor(materialRed500)
        .neutralColor(materialRed500)
        .titleAlignment(Alignment.CENTER)
        .titleColor(materialRed500)
        .contentColor(Color.WHITE)
        .theme(Theme.DARK)
        .show();

To see more colors that fit the Material design palette, see this page: http://www.google.com/design/spec/style/color.html#color-color-palette


Global Theming

By default, the dialog inherits and extracts theme colors from other attributes and theme colors of the app or operating system. This behavior can be overridden in your Activity themes:

<style name="AppTheme" parent="Theme.AppCompat.Light.DarkActionBar">

    <!--
        All dialogs will default to Theme.DARK.
    -->
    <item name="md_dark_theme">true</item>

    <!--
        Applies an icon to all dialogs.
    -->
    <item name="md_dark_theme">true</item>

    <!--
        By default, the title text is pure black or pure white based on the theme.
    -->
    <item name="md_title_color">#E91E63</item>

    <!--
        By default, the content text is derived from the ?android:textColorSecondary OS attribute.
    -->
    <item name="md_content_color">#9C27B0</item>

    <!--
        By default, the accent color is derived from the colorAccent attribute of AppCompat or
        android:colorAccent attribute of the Material theme.
    -->
    <item name="md_accent_color">#673AB7</item>

    <!--
        By default, the list item text color is derived from the ?android:textColorSecondary OS attribute.
    -->
    <item name="md_item_color">#9C27B0</item>

</style>

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:

new MaterialDialog.Builder(this)
    .title("Use Google's Location Services?")
    .content("Let Google help apps determine location. This means sending anonymous location data to Google, even when no apps are running.")
    .positiveText("Agree")
    .showListener(new DialogInterface.OnShowListener() {
        @Override
        public void onShow(DialogInterface dialog) {
        }
    })
    .cancelListener(new DialogInterface.OnCancelListener() {
        @Override
        public void onCancel(DialogInterface dialog) {
        }
    })
    .dismissListener(new DialogInterface.OnDismissListener() {
        @Override
        public void onDismiss(DialogInterface dialog) {
        }
    })
    .show();

Misc

If you need to access a View in the custom view set to a MaterialDialog, you can use getCustomView() of MaterialDialog. This is especially useful if you pass a layout resource to the Builder.

MaterialDialog dialog = //... initialization via the builder ...
View view = dialog.getCustomView();

If you want to get a reference to the title frame (which contains the icon and title, e.g. to change visibility):

MaterialDialog dialog = //... initialization via the builder ...
TextView title = dialog.getTitleFrame();

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

MaterialDialog dialog = //... initialization via the builder ...
View negative = dialog.getActionButton(DialogAction.NEGATIVE);
View neutral = dialog.getActionButton(DialogAction.NEUTRAL);
View positive = dialog.getActionButton(DialogAction.POSITIVE);

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):

MaterialDialog dialog = //... initialization via the builder ...
dialog.setActionButton(DialogAction.NEGATIVE, "New Title");

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:

MaterialDialog dialog new MaterialDialog.Builder(this)
        // ... other initialization
        .autoDismiss(false)
        .show();

To customize fonts:

Typeface titleAndActions = // ... initialize
Typeface contentAndListItems = // ... initialize
MaterialDialog dialog new MaterialDialog.Builder(this)
        // ... other initialization
        .typeface(titleAndActions, contentAndListItems)
        .show();

If you want to force the dialog action buttons to be stacked (override the stacking algorithm):

MaterialDialog dialog new MaterialDialog.Builder(this)
        // ... other initialization
        .forceStacking(true)
        .show();