E
egarcia
Guest
Hello, Support for the Scheduler widget / SchedulerDataSource is our the backlog. If it is critical, you can contact you sales person so they can contact product management to increase the priority. Here are suggestions on how to implement your own scheduler data source. A simple way would be to create a kendo.data.SchedulerDataSource and provide the data (via the data property or the data() method) to it by calling the JSDO directly to get the data (jsdo.getData()). Alternatively, you can create a kendo.data.DataSource for the JSDO and use the Kendo API instead. Here are some simple examples using the JSDO and Kendo UI that would show you how use some of the APIs and create a data source via code: oemobiledemo.progress.com/.../example001.html oemobiledemo.progress.com/.../example013.html oemobiledemo.progress.com/.../example014.html A more advanced approach to this would be to implement the transport methods: create, update, read and destroy. In the method implementation, you can code the access to the JSDO. Here is sample code showing how to implement the transport methods of the Scheduler DataSource: docs.telerik.com/.../schedulerdatasource Here is an old example that shows how to implement the transport methods for CRUD with a Kendo UI DataSource which calls the JSDO: oemobiledemo.progress.com/.../example013.html Please notice that this example was used prior to the integration between the JSDO and the Kendo UI DataSource and implementation of the CRUD transport methods is not needed now. I hope this helps.
Continue reading...
Continue reading...