Hi there,
I am wondering if something is possible with the Scheduler. I have thought about it myself and I am fairly sure of where to start and that it is indeed possible, but I am hoping others can confirm and share their experiences with doing something similar, or point out troubles I am likely to run in to.
I would like to use the Scheduler totally client-side, storing all appointment information on the client, and allowing the user to save changes by clicking a "Save" button. Only then will the changes be sent to the server, processed and database updated etc. I am reasonably familiar with the client-side javascript API, and can imagine storing appointment data client-side (hidden fields and/or cookies), or perhaps using AJAX calls to transmit data each time a change is made for batch processing later, but if someone can share their thoughts on this it would be greatly appreciated.
Is this possible?
Thanks,
Ryan.
I am wondering if something is possible with the Scheduler. I have thought about it myself and I am fairly sure of where to start and that it is indeed possible, but I am hoping others can confirm and share their experiences with doing something similar, or point out troubles I am likely to run in to.
I would like to use the Scheduler totally client-side, storing all appointment information on the client, and allowing the user to save changes by clicking a "Save" button. Only then will the changes be sent to the server, processed and database updated etc. I am reasonably familiar with the client-side javascript API, and can imagine storing appointment data client-side (hidden fields and/or cookies), or perhaps using AJAX calls to transmit data each time a change is made for batch processing later, but if someone can share their thoughts on this it would be greatly appreciated.
Is this possible?
Thanks,
Ryan.