[evolution-patches] Extend calendar plugin support



Hello, 
there are some patches that we created to support features in our
calendar system. 
Patches eds-* are meant to evolution data server and evo-* are for
evolution package. 
It was testedagainst 2.26 release, so i hope it will work with current
developement version of evolution. 

-- Jan Kratina
http://zonio.cz
jan kratina zonio cz
add CAL_STATIC_CAPABILITY_NO_SEND_IMIP calendar capability

From: Ondrej Jirman <ondrej jirman zonio net>

calendar/ChangeLog:

2008-04-06  Ondrej Jirman  <megous megous com>

	** Fix for bug #not yet submitted

	* libecal/e-cal-util.h:
	Add new capability CAL_STATIC_CAPABILITY_NO_SEND_IMIP to disable sending
	of iMIPs and conversion of attachment URLs to 'CID:...' by evolution.

	This is used by calendar backends that want to send iTIPs and upload
	attachments to a calendar server.
---

 calendar/libecal/e-cal-util.h |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)


diff --git a/calendar/libecal/e-cal-util.h b/calendar/libecal/e-cal-util.h
index 0be3bd4..8cf10f6 100644
--- a/calendar/libecal/e-cal-util.h
+++ b/calendar/libecal/e-cal-util.h
@@ -126,6 +126,7 @@ gboolean e_cal_util_event_dates_match (icalcomponent *icalcomp1, icalcomponent *
 #define CAL_STATIC_CAPABILITY_NO_ORGANIZER		 "no-organizer"
 #define CAL_STATIC_CAPABILITY_DELEGATE_TO_MANY		 "delegate-to-many"
 #define CAL_STATIC_CAPABILITY_HAS_UNACCEPTED_MEETING     "has-unaccepted-meeting"
+#define CAL_STATIC_CAPABILITY_NO_SEND_IMIP		 "no-send-imip"
 
 /* Recurrent events. Management for instances */
 icalcomponent *e_cal_util_construct_instance (icalcomponent *icalcomp,
always pass username/password to e_cal_open

From: Ondrej Jirman <ondrej jirman zonio net>


---

 calendar/libecal/e-cal.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)


diff --git a/calendar/libecal/e-cal.c b/calendar/libecal/e-cal.c
index 732b562..7034af9 100644
--- a/calendar/libecal/e-cal.c
+++ b/calendar/libecal/e-cal.c
@@ -1639,7 +1639,7 @@ open_calendar (ECal *ecal, gboolean only_if_exists, GError **error, ECalendarSta
 	g_mutex_unlock (priv->mutex);
 
 	/* see if the backend needs authentication */
-	if ( (priv->mode !=  CAL_MODE_LOCAL) && e_source_get_property (priv->source, "auth")) {
+	if (e_source_get_property (priv->source, "auth")) {
 		char *prompt, *key;
 		char *parent_user;
 
don't cache read only status in ECal

From: Ondrej Jirman <ondrej jirman zonio net>

calendar/ChangeLog:

2008-04-06  Ondrej Jirman  <megous megous com>

	** Fix for bug #525231

	* libecal/e-cal.c: (e_cal_is_read_only):
	Don't cache read_only flag on the client side. Always ask backend plugin
	for the current status of the read_only flag. Some calendar plugins
	allow for changes between read-only/read-write status of the calendar
	on the fly (for example because of change in the calendar ACL).
---

 calendar/libecal/e-cal.c |    7 +------
 1 files changed, 1 insertions(+), 6 deletions(-)


diff --git a/calendar/libecal/e-cal.c b/calendar/libecal/e-cal.c
index c429ff0..732b562 100644
--- a/calendar/libecal/e-cal.c
+++ b/calendar/libecal/e-cal.c
@@ -2114,15 +2114,10 @@ e_cal_get_local_attachment_store (ECal *ecal)
 gboolean
 e_cal_is_read_only (ECal *ecal, gboolean *read_only, GError **error)
 {
-	ECalPrivate *priv;
-
 	if (!(ecal && E_IS_CAL (ecal)))
 		E_CALENDAR_CHECK_STATUS (E_CALENDAR_STATUS_INVALID_ARG, error);
 
-	priv = ecal->priv;
-	*read_only = priv->read_only;
-
-	return TRUE;
+	return get_read_only (ecal, read_only, error);
 }
 
 static gboolean

Attachment: eds-eee-attach-store.patch
Description: application/mbox



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]