You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs-aspnet/html-helpers/scheduling/scheduler/adaptive-rendering.md
+47-46Lines changed: 47 additions & 46 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,16 +9,16 @@ position: 6
9
9
10
10
# Adaptive Rendering
11
11
12
-
The Scheduler supports adaptive enhancements such as changes in styling and behavior in order to remain consistent with the specific user device experience.
12
+
The Scheduler provides adaptive enhancements that adjust its styling and behavior to suit the viewing device.
13
13
14
-
For example, when editing on a mobile device, the edit container will slide in a new screen for the user, which is a departure from the more desktop-like popup behaviors.
14
+
For example, when editing on a mobile device, the edit container slides in on full screen instead of appearing as a popup—providing a more mobile-friendly experience.
15
15
16
16
To enable the adaptive rendering feature, set the [`Mobile`](https://docs.telerik.com/{{ site.platform }}/api/kendo.mvc.ui.fluent/schedulerbuilder#mobile) property to `MobileMode.Auto` or `MobileMode.Phone`:
17
17
18
-
* If set to `MobileMode.Auto`, the component will use adaptive rendering when viewed on a mobile browser.
19
-
* If set to `MobileMode.Phone`, the component will be forced to use adaptive rendering regardless of the browser type.
18
+
* If set to `MobileMode.Auto`, the component uses adaptive rendering when viewed in a mobile browser.
19
+
* If set to `MobileMode.Phone`, the component always uses adaptive rendering, regardless of the browser type.
20
20
21
-
> Important: With the mobile rendering, we recommend to set up `height` as well. Without setting an explicit height, every view of the scheduler might have a different height.
21
+
> When using mobile rendering, set the `Height` explicitly. Otherwise, each Scheduler view might render with a different height.
22
22
23
23
The following example demonstrates how to configure the adaptive rendering mode of the Scheduler.
24
24
@@ -50,49 +50,50 @@ The following example demonstrates how to configure the adaptive rendering mode
|`Id`| Yes | none | The unique model identifier of the Scheduler event. Required for creating, editing, and deleting records. |
97
+
|`Title`| Yes | none | The title or subject of the event. |
98
+
|`Start`| Yes | none | The starting date and time of the event. |
99
+
|`End`| Yes | none | The ending date and time of the event. Must be later than Start. |
100
+
|`RecurrenceRule`| No | null | The rule that defines the recurrence pattern. If not provided or set to null, the event is not treated as a recurring event. |
101
+
|`RecurrenceID`| No | null | Links an exception or occurrence to its recurring master event. |
102
+
|`RecurrenceException`| No | null | A comma-separated list of dates when the recurring event will be skipped. |
103
+
|`IsAllDay`| No | false | Indicates whether the event spans the entire day. |
104
+
|`Description`| No | empty string ("") | Optional text description of the event. |
105
+
106
+
When using HtmlHelper Scheduler, the model properties are automatically mapped to camelCase fields on the client.
107
+
108
+
{% if site.core %}
109
+
110
+
When using TagHelper Scheduler, you need to set the "name" and "from" attributes manually in the schema configuration of the DataSource.
111
+
112
+
The following example shows how to set the properties of the DataSource for the TagHelper:
0 commit comments