Extend Appointment possibility

[GoogleCodeExporter]

Description of the new feature:
Ability to extend an Appointment and use the extended Appointment in 
the Calendar.

Use Case:
If you want to add more fields to an Appointment, this can be done by extending 
the Appointment but the extend Appointment isn't accepted by the handlers. So 
you're now limited to the fields in the Appointment.   

Assumptions:
1.
2.
3.

Exceptions:
1.
2.
3.

Code / psuedo-code:
Change all the <Appointment> generics to <? extends Appointment> 

Original issue reported on code.google.com by bfis...@gmail.com on 14 Sep 2011 at 8:07

[GoogleCodeExporter]

Sounds great! This is really something I would use

Original comment by style2...@gmail.com on 24 Apr 2012 at 7:45

[GoogleCodeExporter]

Hmmmm....  Is this something that's been fixed?  With v0.9.3, I'm doing exactly 
this.  I have my own CalendarAppointment class that extends gwt-cal's 
Appointment class.  I'm able to pass into the gwt-cal infrastructure an 
ArrayList<CalendarAppointment> without problems and it all works (except for 
the serialization issues I mentioned in a separate report.)

In the event handlers, ..., I simply cast the Appointment I get from the event 
handler to a CalendarAppointment (i.e., my extension class) and am then able to 
freely access my appointment extensions.

Note that I do the same thing with the Attendee class.

Original comment by drfoste...@gmail.com on 7 Jun 2012 at 5:36

[GoogleCodeExporter]

AFAIK it's an unconfirmed problem. It's something I want to test and fix if 
needed before the next release.

Original comment by ctasada on 11 Jun 2012 at 8:57