aboutsummaryrefslogtreecommitdiffstats
path: root/camel
diff options
context:
space:
mode:
authorFederico Mena Quintero <federico@helixcode.com>2000-01-19 11:32:45 +0800
committerArturo Espinosa <unammx@src.gnome.org>2000-01-19 11:32:45 +0800
commitbd4e64bd780fc0e39832f5c5abf1a15522fa6076 (patch)
tree927a0247d1a123aef71d576d84e71dd9d9cbfd39 /camel
parenta943a5c706c2dcf6956129838c8b4e5f95de93f4 (diff)
downloadgsoc2013-evolution-bd4e64bd780fc0e39832f5c5abf1a15522fa6076.tar.gz
gsoc2013-evolution-bd4e64bd780fc0e39832f5c5abf1a15522fa6076.tar.zst
gsoc2013-evolution-bd4e64bd780fc0e39832f5c5abf1a15522fa6076.zip
Moved the calendar backend here. This is the actual calendar-handling
2000-01-18 Federico Mena Quintero <federico@helixcode.com> * cal-backend.c cal-backend.h: Moved the calendar backend here. This is the actual calendar-handling object. (load_from_vobject): Moved over from calendar.c. Modified to use a CalBackend instead of the old Calendar structure. (add_object): Likewise. * cal.c: Now the Cal object is just a calendar client interface object; we use it as a "viewport" onto a CalBackend. This also lets us do correct resource management. * cal-common.h: New file with common forward declarations; we can't have circular dependencies between headers. 2000-01-18 Federico Mena Quintero <federico@helixcode.com> * cal-factory.c (cal_factory_load): Queue a load job. (load_fn): Load job handler. Lookup the calendar by URI, load it if it is not loaded, or just report it to the new listener if it is. * job.c job.h: New files with a simple job queue manager. * gnome-calendar.idl (Listener::cal_loaded): Do not return the whole calendar object string. The client will be able to query the calendar for the events it needs. * cal-listener.c (Listener_cal_loaded): Ref the calendar GNOME object. We unref it when the listener is destroyed. 2000-01-17 Federico Mena Quintero <federico@helixcode.com> The files from the gncal directory of the gnome-pim module on CVS were moved here, to evolution/calendar, in preparation for the Evolution work. The calendar is being split into a model/view architecture. The model is a personal calendar server (PAS): it provides storage, notification, and event generation; the views/controllers are the calendar user agents and things like Pilot synchronizers. svn path=/trunk/; revision=1591
Diffstat (limited to 'camel')
0 files changed, 0 insertions, 0 deletions