@ardi-n suggested that the calendar must allow multiple models.
Also the calendar interface can be transformed to a Doctrine_Template. I, myself, don't know enough about doctrine templates. Haven't extended them much.
I've used interfaces because they allow to implement a custom getter even for non-existent field which is often the case with calendar data where the field value may be extracted from a record's relation?
So , does Doctrine_Template allows defining required getters - just as the interface does?
I would define an interface for eventable models. With Doctrine_Template you could define additional fields and methods mutual for all eventable models. So for now, interface is sufficient in my opinion.
@ardi-n suggested that the calendar must allow multiple models.
Also the calendar interface can be transformed to a Doctrine_Template. I, myself, don't know enough about doctrine templates. Haven't extended them much.
I've used interfaces because they allow to implement a custom getter even for non-existent field which is often the case with calendar data where the field value may be extracted from a record's relation?
So , does Doctrine_Template allows defining required getters - just as the interface does?