[Evolution-hackers] EDataCal API change for 3.3.3

[Milan Crha <mcrha redhat com>]

	Hi all,
I just want to let you know that I made another API changes in EDataCal,
namely with functions:
   e_data_cal_view_get_component_string
   e_data_cal_view_notify_components_added
   e_data_cal_view_notify_components_added_1
   e_data_cal_view_notify_components_modified
   e_data_cal_view_notify_components_modified_1
   e_data_cal_respond_create_object
   e_data_cal_respond_modify_object
   e_data_cal_respond_remove_object
   e_cal_backend_notify_component_created
   e_cal_backend_notify_component_modified
   e_cal_backend_notify_component_removed

Tristan added/changed these functions for 3.3.2 [1], and even he
initially proposed to use ECalComponent-s, I convinced him to change it
to icalcomponent-s. When I begun to use this new API I realized that my
decision was plain wrong, thus I changed these functions to use
ECalComponent instead [2].

The change touched also ECalBackendSync API, unfortunately.

I also deprecated below functions in favor of new API:
   e_cal_backend_notify_object_created
   e_cal_backend_notify_objects_added
   e_cal_backend_notify_object_modified
   e_cal_backend_notify_objects_modified
   e_cal_backend_notify_object_removed
   e_cal_backend_notify_objects_removed
   e_data_cal_view_notify_objects_added
   e_data_cal_view_notify_objects_added_1
   e_data_cal_view_notify_objects_modified
   e_data_cal_view_notify_objects_modified_1

I made necessary changes in evolution-data-server, evolution-exchange,
evolution-groupwise, evolution-mapi and evolution-ews calendar backends,
to both API changes and replaced usage of the newly deprecated stuff.

I also added a new function
   e_cal_component_new_from_icalcomponent
which seemed to be useful to me.

I'm sorry for the inconvenience I caused, but this is hopefully the last
API change in EDataCal for 3.3.x.
	Bye,
	Milan

[1] https://bugzilla.gnome.org/show_bug.cgi?id=652180
[2] https://bugzilla.gnome.org/show_bug.cgi?id=664572