A Material design back port of Android's CalendarView. The goal is to have a Material look and feel, rather than 100% parity with the platform's implementation.
Step 1. Add the JitPack repository to your build file
allprojects {
repositories {
...
maven { url 'https://jitpack.io' }
}
}
Step 2. Add this to your app/module level build.gradle
android {
compileOptions {
// Flag to enable support for the new language APIs
coreLibraryDesugaringEnabled true
// Sets Java compatibility to Java 8
sourceCompatibility JavaVersion.VERSION_1_8
targetCompatibility JavaVersion.VERSION_1_8
}
}
dependencies {
// enable desugaring
coreLibraryDesugaring 'com.android.tools:desugar_jdk_libs:<latest-version>'
// the actual library
implementation 'com.github.goemic:material-calendarview:3.0.0'
}
- Add
MaterialCalendarView
into your layouts or view hierarchy. - Set a
OnDateSelectedListener
or callMaterialCalendarView.getSelectedDates()
when you need it.
Example:
<com.prolificinteractive.materialcalendarview.MaterialCalendarView
xmlns:app="http://schemas.android.com/apk/res-auto"
android:id="@+id/calendarView"
android:layout_width="match_parent"
android:layout_height="wrap_content"
app:mcv_showOtherDates="all"
app:mcv_selectionColor="#00F"
/>
Make sure to check all the documentation available here.
One of the aims of this library is to be customizable. The many options include:
- Define the view's width and height in terms of tile size
- Single or Multiple date selection, or disabling selection entirely
- Showing dates from other months or those out of range
- Setting the first day of the week
- Show only a range of dates
- Customize the top bar
- Custom labels for the header, weekdays, or individual days
All of this and more can be done via the decorator api. Please check out the decorator documentation.
Material CalendarView uses now java.time instead of ThreeTen Android Backport. Therefore, Java 8+ API desugaring is enabled. Furthermore, the library is migrated to androidx.
Material CalendarView 2.0 comes in with a major change into the core of it's API, we transitioned from using java.util.Calendar
to java.time.LocalDate
. Also that should not impact the public api (we are still using CalendarDay
), both Calendar
and LocalDate
function a little bit differently.
One example of that: Months are now indexed from 1 (January) to 12 (December). You can access from the LocalDate
from CalendarDay
using getDate()
.
Also this release doesn't have any break changes, it provides significant improvements to the widget. More customization have been added for the user (custom fonts, long click listener, show/hide weekdays) as well as various fixes, improvements to the sample app, and general cleanup. Make sure to check the CHANGELOG and the release section for more details.
We recently updated to the latest gradle and decided to move over our libraries to the hosting service Jitpack. Please refer to the installation section for more details.
-
Breaking Change:
setFirstDayOfWeek
,setMin/MaxDate
, andsetCalendarDisplayMode
are moved to aState
object. This was necessary because it was unclear that these were not simple setters--individually, they were side effecting and triggered full adapter/date range recalculations. Typical usage of the view involves setting all these invariants up front duringonCreate
and it was unknown to the user that setting all 4 of these would create a lot of waste. Not to mention certain things were side effecting--some would reset the current day or selected date. As a result, the same 4 methods called in a different order could result in a different state, which is bad.For most cases you will simply need to replace setting those invariants with:
mcv.state().edit() .setFirstDayOfWeek(Calendar.WEDNESDAY) .setMinimumDate(CalendarDay.from(2016, 4, 3)) .setMaximumDate(CalendarDay.from(2016, 5, 12)) .setCalendarDisplayMode(CalendarMode.WEEKS) .commit();
mcv.state().edit()
will retain previously set values;mcv.newState()
will create a new state using default values. Callingcommit
will trigger the rebuild of adapters and date ranges. It is recommended these state changes occur as the first modification to MCV (before configuring anything else like current date or selected date); we make no guarantee those modifications will be retained when the state is modified.See CUSTOMIZATION_BUILDER for usage details.
-
New:
setSelectionMode(SELECTION_MODE_RANGE)
was added to allow 2 dates to be selected and have the entire range of dates selected. Much thanks to papageorgiouk for his work on this feature.
See other changes in the CHANGELOG.
Would you like to contribute? Fork us and send a pull request! Be sure to checkout our issues first.
Material Calendar View is Copyright (c) 2018 Prolific Interactive. It may be redistributed under the terms specified in the LICENSE file.
Material Calendar View is maintained and funded by Prolific Interactive. The names and logos are trademarks of Prolific Interactive.