|
10 жил өмнө | |
---|---|---|
gradle | 10 жил өмнө | |
library | 10 жил өмнө | |
sample | 10 жил өмнө | |
.gitignore | 10 жил өмнө | |
LICENSE.txt | 10 жил өмнө | |
README.md | 10 жил өмнө | |
build.gradle | 10 жил өмнө | |
gradlew | 10 жил өмнө | |
gradlew.bat | 10 жил өмнө | |
settings.gradle | 10 жил өмнө | |
versions.properties | 10 жил өмнө |
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.
- The ability to choose whether or not custom views are placed inside of a
ScrollView
(the second parameter ofcustomView()
in theBuilder
). This is heavily based off a pull request by Kevin Barry, thanks for your help! See the Custom Views section for more details, see the sample project for an example in action.- An enormous amount of fixes for padding and spacing throughout the different types of dialogs. A top divider is also used when there's scrollable content.
- Other bug fixes and improvements throughout.
- Improvements for padding in list dialogs.
- Fixed the
forceStacking
option.- Single choice dialogs will wait to send selection callbacks until positive action button is pressed, if the positive action button is set.
- Pull request from hzsweers: https://github.com/afollestad/material-dialogs/pull/146
- List items use pure black or white text depending on theme by default, rather than the former gray-ish color.
- Yet more fixes thanks to a pull request from hzsweers.
- Note that the 3 variations of the action callbacks are deprecated and replaced with the single
ButtonCallback
interface.- A fix for action button text styling on Lollipop, thanks plusCubed!
- Other fixes and improvements.
- The ability to force the action buttons to be stacked (see the Misc. section).
- Crash fix for Huawei devices
- Removed some unnecessary logging.
- New methods in
MaterialDialogCompat.Builder
- Other crash fixes and improvements.
- Memory management improvements for Typefaces (thanks Kevin Barry of Nova Launcher!)
- Added
dismiss
,cancel
, andshow
listener methods to theBuilder
.
- Added
md_item_color
attribute to global theming.- Added
md_icon
attribute to global theming.- Fixed a crash bug on pre-Lollipop devices related to list dialogs.
- Fixed list item default color on dark dialogs for pre-Lollipop.
- Fixes to action button insets, and the stacking algorithm. Thanks plusCubed!
- Major padding/margin fixes for using an icon with list dialogs.
- Bug fixes and improvements throughout
- Action button selectors have rounded corners
- Global theming capabilities. Override the accent color used for action buttons, titles, and content from your Activity theme. See the Global Theming section below.
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.5.0'
}
Make sure you're using the jCenter repository, Android Studio uses this repository by default.
Check back here frequently for version updates.
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.
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();
}
});
dialogBuilder.create().show();
But it's highly recommended to use original MaterialDialog
API for new usages.
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 for a drawable resource ID or attribute ID, which is recommended.
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();
You can also force the dialog to stack its buttons with the forceStacking()
method of the Builder
.
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();
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.
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 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.
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.
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.
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.
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 are very easy to implement.
boolean wrapInScrollView = true;
new MaterialDialog.Builder(this)
.title("Google Wifi")
.customView(R.layout.custom_view, wrapInScrollView)
.positiveText("Connect")
.positiveColor(Color.parseColor("#03a9f4"))
.build()
.show();
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.
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)
.titleGravity(Gravity.CENTER_HORIZONTAL)
.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
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.
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();
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();