I have just started to experiment with this component and really like the work that has been started. I am contemplating using it in our application but there are a couple of observations which would increase its utility for us.
[1] The mode property is set on the underlying model rather than the JSF control. This departs from the MVC and requires the backing beans interact with the model rather than just the page. Could the mode property be moved to the Schedule tag?
[2] Similar to [1] the selected date (I assume this is used to set the view day/week/month etc. is also on the model rather than the tag. Again, moving this property to the tag would provide better seperation of view and model.
[3] The date format for the date headers could be better set using a dateConverter which provides for locale etc. rather than using date format strings.
These are just some simple suggestions. I can have a crack at these changes if there is support for it from the community :)
[1] The mode property is set on the underlying model rather than the JSF control. This departs from the MVC and requires the backing beans interact with the model rather than just the page. Could the mode property be moved to the Schedule tag?
[2] Similar to [1] the selected date (I assume this is used to set the view day/week/month etc. is also on the model rather than the tag. Again, moving this property to the tag would provide better seperation of view and model.
[3] The date format for the date headers could be better set using a dateConverter which provides for locale etc. rather than using date format strings.
These are just some simple suggestions. I can have a crack at these changes if there is support for it from the community :)
