When you bind the Scheduler to data, note the following specifics:
- When the data is received from an asynchronous source, pipe it through the
Dateobject which ensures their correct handling and formatting.
kendoSchedulerBinding directive filters events that are out of range and expands the recurring series in-memory.
All included events need to have their recurring rules set in the data set. Determining whether an event occurs in the current time period requires the evaluation of the recurrence rule. In practice, events with set recurring rules must be supplied unless it can be - be what????.....
You can bind events by directly using the
events attribute of the Scheduler. This binding mode is useful for skipping the built-in recurrence engine and using an alternative—for example, a server-side solution.
dateChange event fires each time the current date range changes which allows the supply of the event data in smaller chunks that cover only the currently visible time period.
dateChangeevent does not necessarily fire when the views get switched—for example, an Agenda and a Week view may cover the same date range.
An event can have one or more "resources" assigned to it—for example, a meeting room or a guest list. To configure the Scheduler to display each resource as a sub-view, refer to the section on grouping by resource.
As a minimum, you have to define the following fields:
field—The field name of the event that contains the resource value.
data—The resource data array.
valueField—The field name from the data that contains the value of the resource.
textField—The field name from the data that contains the text of the resource.