recurringException - Represents the exceptions of a recurring event, when specific dates need to be skipped from the rule. recurring - Configures the recurring rules for the event.allDay - Configures the event as a full-day event.The same formats are supported as for start end - Sets the end date and time for the event.It can be a js date object, ISO date string or moment.js object. start - Sets the start date and time for the event.If not specified, it will show the title and the start/end times of the event. tooltip - Defines the text for the tooltip which appears on mouse hover. If not specified a unique id will be generated Besides the base properties you can add any custom property, like location, description. The event data structure for the timeline is straightforward with a couple of base properties that the component understands and uses to render the UI. This means if you would like to add opacity, override the mouse cursor or apply any other CSS override, you can add it to this class. The mbsc-event-readonly CSS class will be added to the events. This turns delete, drag & drop move and resize off for the event. Use the dragTimeStep option (defaults to 15 minutes) to set the snap resolution of all drag actions.Įvents can be marked as fixed by setting their editable property to false. You have granular control over features through the clickToCreate,ĭragToResize and eventDelete options, which are false by default. Delete events - pressing the Delete or Backspace keys on the keyboard will delete the focused event.Resize events - change the length of an event, grab it from either end and resize it.Move events - grab an event and move it wherever needed.Drag to create events - tap/click to start creating an event and drag to the desired length.This can be turned off or set to single click Click to create events - double click to create events.Rolling three months - use type: 'month' and size: 3ĭrag & drop is a core feature of the event calendar and it is composed of four sub-features:.Quarter view, starting from January - use type: 'month' and size: 3 with refDate: ''.Two weeks (starting with Sun/Mon) - use type: 'week' and size: 2.Rolling two weeks - use type: 'day' and size: 14.From that point on you can navigate forward and backward. The refDate serves as the start of the reference range. Is today by default, but it can be set to any date, like the first day of the month, or the first day of the year. The reference date, controlled through the refDate option, If set to 'day', the days will be rendered on the vertical axis, while the hours of the day will be displayed on the horizontal axis. Use the resolutionVertical property of the configuration object to set the vertical unit of a timeline rows, it can be TimeCellStep and timeLabelStep properties. In case of hourly resolution, the columns can be split to minutes (1, 5, 15, 20, 30) or merged into multiple hours (2, 3, 4, 6, 8, 12) using the Use the resolutionHorizontal property of the configuration object to set the horizontal unit of a timeline column, it can be Use the size property of the configuration object to set the length of the view or page size. There are four types of timeline views: day, week, month and year. Learn how to create a custom event template. In the custom template/render function we can account for the offsets and print the times in the team members timezone instead of the base timezone (UTC in this example). The last thing that needed to be done is to override the event rendering with a custom template. On how to work with disabled times and how to override them take a look at this example. Besides the colored backgrounds we've also set "time off" to invalid for validation purposes. For that we are setting colored backgrounds with time labels that show the "working hours", "flex hours" and "time off". That's why we need to somehow communicate the work hours with the correct offsets so that the person doing the scheduling can easily find the best times for the meeting. To learn more about timezone management take a look at this example.īecause all resources are part of the same calendar they operate in the same timezone. This also means that the scheduler operates in this timezone set through the dataTimezone and displayTimezone options. Each team member can be in separate timezones which means we need to account for the various offsets.įirst we need to set a base timezone, which for the sake of simplicity is UTC and it is the timezone of the first resource, the meeting organizer. In this example, built with the Mobiscroll scheduler we've laid out a timeline with multiple resources that represent the teammates. Setting up meetings across multiple timezones is messy and hard task.
0 Comments
Leave a Reply. |