Yes, I know, but it's protected. I figured you'd see that :)
I have to override datepicker to get at its view to disable dates I don't want selected in the calendar. Maybe ideally it would be better to open up extending the view and model to the datepicker which are both protected too. I'd love to extend either the DefaultView and add some logic to it for our app. I think the original intention for the view was for its extension from the comments I've read but it's been some time it would seem its more mature.
CalendarView.class - comments at the top:
/**
* Simple calendar view. Not extensible as we wish to evolve it freely over
* time.
*/
Basically everything is protected for overriding functions. I can see why it's protected to improve the the methods before allowing for it to be extended and for use.
Also do you see any harm in making the 'CalendarView getView()' a public method? because I don't :)
Thanks for taking a look at this Patrick.
Brandon