This is a migrated thread and some comments may be shown as answers.

Why does IAppointment NOT implement Category, Importance, TimeMarker?

1 Answer 70 Views
ScheduleView
This is a migrated thread and some comments may be shown as answers.
Simon
Top achievements
Rank 1
Simon asked on 26 Sep 2011, 11:38 PM
Hi,

We make extensive use of the ScheduleView control within our app.
As such we have implemented IAppointment to extend our own appointment object.

However it seems strange that Category, Importance and TimeMarker are not part of the IAppointment interface - only AppointmentBase! Our object inherits from Entity - so can't inherit from AppointmentBase also.

We really need the EditAppointmentDialog ViewModel to work fully against our Appointment object and the exclusion of these is bewildering. 

Perhaps this can be included in future releases? Was there a specific reason for excluding it?

Thanks
Simon

1 Answer, 1 is accepted

Sort by
0
George
Telerik team
answered on 29 Sep 2011, 07:23 AM
Hi Simon,

 
Thank you for contacting us.

The TimeMarker, Category and Importance properties are moved to the IExtendedAppointment interface. In other word, the entity object could implement IAppointment, IExtendedAppointment and IObjectGenerator<IRecurrenceRule>.

I hope this helps.

All the best,
George
the Telerik team

Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>

Tags
ScheduleView
Asked by
Simon
Top achievements
Rank 1
Answers by
George
Telerik team
Share this question
or