New edit mode: When events are retrieved, those models should always be as lightweight as possible (id, start, end, title), and not include all the other properties required to edit an event. If you have hundreds of events with lots of properties, your control does not scale well. When you then edit one of these lightweight events, it should make an ajax request to go fetch the "full" model used to populate the edit popup window. For the create, it may not have to make an ajax request, but the "full" schema needs to be defined still, so it has a model to bind, and it would be nice to have a way to dynamically specify that schema, in case you have different event model types. In my case, I have three different types of appointments the user can create/edit. Ideally, these "full" models would either get sent via ajax when the popup is closed, or when the datasource is synced, they get trimmed down to the lightweight version. Hopefully this all makes sense...it's all about having tiny models for speed, but larger models for editing. Anyone that has used your control to show tons of appointments (especially with many properties each) will likely get where I am going with this.