There's no reason at all why manager should be a property inside the
views. It won't benefit of bindings or anything else inherent to GObject
property system.
This is more of a semantic change than anything else. GcalSubscriber
will gradually take on GcalView interface and that's why I'm adding the
View suffix.
By making GcalMonthView a descendat of GcalSubscriber it gets
implementation for each of the methods on ECalDataModel subscriber and
utomatically gains the functionality of adding and removing events widgets
As explained before, this is only intended to keep a reference to the
GcalManager instance of the application.
Misc: fixed some documentation and whitespace issues
Implemented set_date method, moving update of ::date attribute to another call
outside the construction process. The method can be used to set or update the
GcalView::active-date property
Implemented changes from GcalView API
Integrated GcalWeekView into application flow.
Added gcal_view_add_event method GcalView interface.
Fixed size_allocate implementation in GcalMonthView to allocate children events.
There's still work to be done here.
