I would like to voice my opinion for an ASP.NET Scheduling Component based on the requested feedback from the following post:http://www.telerik.com/community/forums/thread/b311D-tbdhb.aspx
We are currently researching components for use in a custom developed company internal scheduling tool that will be used by multiple business units. Based on this we have come up with the feedback listed below.Key Requirements
- AJAX support
- Robust client-side object model
- Solid drag and drop support
- Recurring tasks/appointments
- Task/Appointment alerts
- Style look and feel via CSS
- Cross browser compatible (IE -- 6 & 7, Firefox -- PC & Mac)
- Concise HTML markup
- Not ViewState dependent.
- Support for database storage a must (other storage types a nice to have)
- Day, Week, Month views.
- Ability to show tasks/appointments for multiple resources on the same view.
- Drag tasks/appointments within a day and use drag to change start/end times.
- Drag tasks/appointments between days.
- Show multiple taks/appointments with varying colors.
- Have tasks/appointments with multiple states (e.g. published - viewable by all and planned - viewable only by some).
Since we are currently evaluating other controls we do have any real world experience with these, but here are some initial thoughts after looking at the following.Other Controls
- WebPlanner by TMSSoftware
- Lacks AJAX support (beta with ajax available 4/2007)
- Have focused attention on being lightweight.
- WebSchedule by Infragistics
- Extensible data provider model.
- Runs with enableviewstate='false'.
- Lacks drag and drop across days in a week or month view.
- WebSchedule by ComponentOne
- Lacks drag and drop
- Not sure it supports displaying multiple resource schedules at one time.
Please let me know if you would like additional information from me.
- Paige Cook