This addon is an integration of the FullCalendar (v3.9.0) as Flow component for Vaadin Platform / Vaadin 10+.
For information about the FullCalendar (functionality, features, license information, etc.) visit https://fullcalendar.io/
If you want to use the Scheduler, please have a look here: https://vaadin.com/directory/component/full-calendar-scheduler-extension
The following functions are implemented and available to use from server side:
-
adding / updating / removing calendar items,
-
switching between shown intervals (next month, previous month, etc.),
-
goto a specific date or today,
-
switch the calendar view (month, basic views for days and weeks, agenda views for days and weeks, list views for day to year),
-
setting a locale to be used for displaying week days, formatting values, calculating the first day of the week, etc. (supported locales are provided as constant list)
-
setting the first day of week to be shown (overrides the locale setting),
-
setting the height of the calendar instance (calculated by parent, aspect ratio or fixed pixel size)
-
show of week numbers
-
limit max shown entries per day (except basic views)
-
showing now indicator
-
activating day / week numbers / names to be links
-
styles are overridable via custom properties
-
setting a eventRender JS function from server side
-
setting business hours (multiple instances possible)
-
timezone support
-
Event handling for
- clicking an empty time spot in the calendar,
- selecting a block of empty time spots in the calendar,
- clicking an entry,
- moving an entry via drag and drop (event is fired on drop + changed time),
- resizing an entry (event is fired after resize + changed time),
- view rendered (i. e. to update a label of the shown interval)
- clicking on limited entries link "+ X more"
- clicking on a day's or week's number link (when activated)
-
Model supports setting
- title,
- start / end / all day flag,
- color (html colors, like "#f00" or "red"),
- description (not shown via FC),
- editable / read only
- rendering mode (normal, background, inversed background)
Starting with 1.6.0 FC supports setting timezones. From this version, entries and some events work with Instant to represent the time based on UTC. You may set a custom timezone to display events for a user's timezone while the entries themselves still work with UTC based times.
If there are bugs or you need more features (and I'm not fast enough) feel free to contribute on GitHub. :) I'm also happy for feedback or suggestions about improvements.
// Create a new calendar instance and attach it to our layout
FullCalendar calendar = FullCalendarBuilder.create().build();
container.add(calendar);
container.setFlexGrow(1, calendar);
// Create a initial sample entry
Entry entry = new Entry();
entry.setTitle("Some event");
entry.setStart(LocalDate.now().withDayOfMonth(3).atTime(10, 0));
entry.setEnd(entry.getStart().plusHours(2));
entry.setColor("#ff3333");
calendar.add(entry);
/*
* The day click event listener is called when a user clicks in an empty space inside of the
* calendar. Depending of if the clicked point was a day or time slot the event will provide the
* time details of the clicked point. With this info you can show a dialog to create a new entry.
*/
calendar.addTimeslotClickedListener(event -> {
Entry entry = new Entry();
LocalDateTime start = event.getClickedDateTime();
entry.setStart(start);
boolean allDay = event.isAllDay();
entry.setAllDay(allDay);
entry.setEnd(allDay ? start.plusDays(FullCalendar.DEFAULT_DAY_EVENT_DURATION) : start.plusHours(FullCalendar.DEFAULT_TIMED_EVENT_DURATION));
entry.setColor("dodgerblue");
// ... open a dialog or other view to edit details
});
/*
* The entry click event listener is called when the user clicks on an existing entry.
* The event provides the clicked event which might be then opened in a dialog.
*/
calendar.addEntryClickListener(event ->
new DemoDialog(calendar, event.getEntry(), false).open());
// ... create a form and binder to provide editable components to the user
HorizontalLayout buttons = new HorizontalLayout();
Button buttonSave;
if (newInstance) {
buttonSave = new Button("Create", e -> {
if (binder.validate().isOk()) {
// add the entry to the calendar instance
calendar.addEntry(entry);
}
});
} else {
buttonSave = new Button("Save", e -> {
if (binder.validate().isOk()) {
// update an existing entry in the client side
calendar.updateEntry(entry);
}
});
}
buttons.add(buttonSave);
if (!newInstance) {
Button buttonRemove = new Button("Remove", e -> calendar.removeEntry(entry));
buttons.add(buttonRemove);
}
private void init() {
// The element that should show the current interval.
HasText intervalLabel = new Span();
// combo box to select a view for the calendar, like "monthly", "weekly", ...
ComboBox<CalendarView> viewBox = new ComboBox<>("", CalendarViewImpl.values());
viewBox.addValueChangeListener(e -> {
CalendarView value = e.getValue();
calendar.changeView(value == null ? CalendarViewImpl.MONTH : value);
});
viewBox.setValue(CalendarViewImpl.MONTH);
/*
* The view rendered listener is called when the view has been rendererd on client side
* and FC is aware of the current shown interval. Might be accessible more directly in
* future.
*/
calendar.addViewRenderedListener(event ->
LocalDate intervalStart = event.getIntervalStart();
CalendarView cView = viewBox.getValue();
String formattedInterval = ... // format the intervalStart based on cView
intervalLabel.setText(formattedInterval);
});
}
// #1 setting a fixed height
calendar.setHeight(500);
// #2 setting a auto height - this is calculated by the w-h-ratio of the calendar
calendar.setHeightAuto();
// #3 calculate height by parent. parent is a block container.
calendar.setHeightByParent();
calendar.setSizeFull();
// #4 calculate height by parent + usage of css calc(). parent is a block container.
calendar.setHeightByParent();
calendar.getElement().getStyle().set("height", "calc(100vh - 450px)");
// #5 calculate height by parent. parent is a flex container.
calendar.setHeightByParent();
calendar.getElement().getStyle().set("flex-grow", "1");
- Copy the styles.html from the github demo or create your own custom style file and place it in your applications webapp/frontend folder (e. g. webapp/frontend/styles/styles/my-custom-full-calendar-styles.html)
The github demo file can be obtained from here: https://github.com/stefanuebe/vaadin_fullcalendar/blob/master/demo/src/main/webapp/frontend/styles.html
- Modify the styles as needed.
<custom-style>
<style>
html{
/* light blue to be used instead of default light yellow*/
--fc-unthemed_tdfc-today-background: #81DAF5 !important;
/* and some fancy border */
--fc_td-border-style: dotted !important;
--fc_td-border-width: 2px !important;
}
</style>
</custom-style>
- Use the styles file in your application.
@HtmlImport("frontend://styles/full-calendar-styles.html")
public class FullCalendarApplication extends Div {
// ...
}
Create a custom component, that extends FullCalendar or FullCalendarScheduler. Add a style element and your custom css stylings. Override the static template method and let it insert your template with the style node into the parents template DOM.
The example my-full-calendar.html sets a beautiful green background for empty lists (.fc-list-empty).
Please note, that the id of your component inside of the template method needs to be updated to your component's id.
<link rel="import" href="bower_components/fullcalendar/full-calendar-scheduler.html">
<dom-module id="my-full-calendar">
<template>
<style id="styles">
.fc-list-empty {
background-color: green !important;
}
</style>
</template>
<script>
class MyFullCalendar extends FullCalendarScheduler {
static get is() {
return 'my-full-calendar';
}
// example of adding / overriding styles
static get template() {
const parentTemplate = FullCalendarScheduler.template.cloneNode(true);
const childTemplate = Polymer.DomModule.import('my-full-calendar', 'template');
parentTemplate.content.insertBefore(childTemplate.content, parentTemplate.content.firstChild);
return parentTemplate;
}
}
customElements.define(MyFullCalendar.is, MyFullCalendar);
</script>
</dom-module>
// The given string will be interpreted as js function on client side // and attached as eventRender callback. // Make sure, that it does not contain any harmful code.
calendar.setEntryRenderCallback("" + "function(event, element) {" + " console.log(event.title + 'X');" + " element.css('color', 'red');" + " return element; " + "}");
- Create a new polymer template (e.g. webapp/frontend/my-full-calendar.html):
_createInitOptions() {
var options = super._createInitOptions();
options.eventRender = function (event, element) {
element.css('color', 'red');
return element;
};
return options;
}
}
customElements.define(MyFullCalendar.is, MyFullCalendar);
</script>
- Create a subclass of FullCalendar
import com.vaadin.flow.component.Tag; import com.vaadin.flow.component.dependency.HtmlImport; import org.vaadin.stefan.fullcalendar.FullCalendar;
@Tag("my-full-calendar") @HtmlImport("frontend://my-full-calendar.html") public class MyFullCalendar extends FullCalendar { MyFullCalendar(int entryLimit) { super(entryLimit); } }
- Use this class in your code
calendar = new MyFullCalendar(5);
Entry entry = new Entry(); // ... setup entry details
entry.setRenderingMode(Entry.RenderingMode.BACKGROUND); calendar.addEntry(entry);
// Single instance for "normal" business week (mo-fr) calendar.setBusinessHours(new BusinessHours(LocalTime.of(9, 0), LocalTime.of(17, 0),BusinessHours.DEFAULT_BUSINESS_WEEK));
// Multiple instances calendar.setBusinessHours( new BusinessHours(LocalTime.of(9, 0), LocalTime.of(17, 0),BusinessHours.DEFAULT_BUSINESS_WEEK), new BusinessHours(LocalTime.of(12, 0), LocalTime.of(15, 0), DayOfWeek.SATURDAY) );
// Single instance for "each day from 9am to midnight" calendar.setBusinessHours(new BusinessHours(LocalTime.of(9, 0)));
// Per default, our FC works with UTC. You can set a custom timezone to be shown for the user. // This will automatically update all entries on the client side. Timezone tzBerlinGermany = new Timezone("Europe/Berlin"); calendar.setTimezone(tzBerlinGermany);
// We can also reset the timezone to default. calendar.setTimezone(Timezone.UTC);
// We can also read the browsers timezone, after the component has been attached to the client side. // There are other ways to obtain the browser's timezone, so you are not obliged to use the listener. calendar.addBrowserTimezoneObtainedListener(event -> calendar.setTimezone(event.getTimezone()));
// When using timezones, entries can calculate their start and end in different ways. entry.setStart(Instant.now()); // UTC entry.setStart(LocalDateTime.now(), tzBerlinGermany); // timezone is used to calculate the UTC value
entry.setCalendar(calendar); // is done automatically, when using calendar.addEntry(entry); entry.setStart(LocalDateTime.now()); // Uses the calendars timezone (or UTC as fallback)
// Timezone provides some convenient methods to work with the two different temporal types tzBerlinGermany.convertToUTC(LocalDateTime.of(2018, 10, 1, 10, 0, 0)) // Standard time, returns Instant for 9:00 UTC this day. tzBerlinGermany.convertToUTC(LocalDateTime.of(2018, 8, 1, 10, 0, 0)) // Summer time, returns Instant for 8:00 UTC this day. tzBerlinGermany.convertToLocalDateTime(Instant.now()) // returns a date time with +1/+2 hours (depending on summer time).
This addon extends the FullCalendar integration addon with the FullCalendar Scheduler (v1.9.4) as Flow component for Vaadin Platform / Vaadin 10+.
It needs the FC integration addon (1.9.0+) as basis (https://vaadin.com/directory/component/full-calendar-web-component). Since this addon is not always updated when the basis gets an update, I would suggest, that you add both dependencies (basis and extension) to always use the latest version of basis. This extension is compatible as long as the readme does not tells anything else.
For information about the Schedular (functionality, features, license information, etc.) visit https://fullcalendar.io/scheduler.
Please be aware, that the Scheduler has a different license model then the FullCalendar. For details of when to use which license, visit https://fullcalendar.io/scheduler/license.
This addon does not provide any commercial license for the Scheduler. The license model of MIT does only affect the additional files of this addon, not the used original files.
By default the scheduler is not active, when you use a FullCalendar instance. To have an instance with scheduler
activated, use the withScheduler() method of the FullCalendarBuilder.
This method will throw an exception, if the scheduler extension is not on the class path.
To link a resource with entries, use the Entry subclass ResourceEntry.
- Activation of the Scheduler by method in the FullCalendarBuilder.
- Adding resources to a calendar (hierarchies of resources are not yet supported).
- Link one or multiple resources with entries.
- List of possible Scheduler based views (timeline).
Info: Entries are linked to calendar internally. The calendar instance is used to resolve resources by after updating an entry on the client side.
If there are bugs or you need more features (and I'm not fast enough) feel free to contribute on GitHub. :) I'm also happy for feedback or suggestions about improvements.
FullCalendar calendar = FullCalendarBuilder.create().withScheduler().build();
// scheduler options
((Scheduler) calendar).setSchedulerLicenseKey(...);
Resource resource = new Resource(null, s, color);
calendar.addResource(resource);
// When we want to link an entry with a resource, we need to use ResourceEntry
// (a subclass of Entry)
ResourceEntry entry = new ResourceEntry(null, title, start.atStartOfDay(), start.plusDays(days).atStartOfDay(), true, true, color, "Some description...");
entry.setResource(resource);
calendar.addEntry(entry);
calendar.addEntryDroppedListener(event -> {
event.applyChangesOnEntry();
Entry entry = event.getEntry();
if(entry instanceof ResourceEntry) {
Set<Resource> resources = ((ResourceEntry) entry).getResources();
if(!resources.isEmpty()) {
// do something with the resource info
}
}
});
calendar.changeView(SchedulerView.TIMELINE_DAY);
calendar.setGroupEntriesBy(GroupEntriesBy.RESOURCE_DATE);
- Copy the styles_scheduler.html from the github demo or create your own custom style file and place it in your applications webapp/frontend folder (e. g. webapp/frontend/styles/styles/my-custom-full-calendar-styles.html)
The github demo file can be obtained from here: https://github.com/stefanuebe/vaadin_fullcalendar/blob/master/demo/src/main/webapp/frontend/styles_scheduler.html
- Modify the styles as needed.
<custom-style>
<style>
html{
--fc-timeline_fc-divider-border-style: dashed;
--fc-timeline_fc-divider-width: 2px;
}
</style>
</custom-style>
- Use the styles file in your application.
@HtmlImport("frontend://styles/full-calendar-styles-scheduler.html")
public class FullCalendarApplication extends Div {
// ...
}
- Create a new polymer template (e.g. webapp/frontend/my-full-calendar.html):
_createInitOptions() {
var options = super._createInitOptions();
options.eventRender = function (event, element) {
element.css('color', 'red');
return element;
};
return options;
}
}
customElements.define(MyFullCalendar.is, MyFullCalendar);
</script>
- Create a subclass of FullCalendarScheduler
import com.vaadin.flow.component.Tag; import com.vaadin.flow.component.dependency.HtmlImport; import org.vaadin.stefan.fullcalendar.FullCalendarScheduler;
@Tag("my-full-calendar") @HtmlImport("frontend://my-full-calendar.html") public class MyFullCalendar extends FullCalendarScheduler { MyFullCalendar(int entryLimit) { super(entryLimit); } }
- Use this class in your code
calendar = new MyFullCalendar(5);
ResourceEntry entry = new ResourceEntry(); // ... setup entry details, including addResource()
entry.setRenderingMode(Entry.RenderingMode.BACKGROUND); calendar.addEntry(entry);