Remove e_data_cal_view_register_gdbus_object().
authorMatthew Barnes <mbarnes@redhat.com>
Fri, 12 Oct 2012 23:15:44 +0000 (19:15 -0400)
committerMatthew Barnes <mbarnes@redhat.com>
Sat, 13 Oct 2012 12:41:15 +0000 (08:41 -0400)
commit8bdefa87db7d0ec3f113273fbccfd864391d40f4
treeeace62326204e6b43b1d28370472e6c33cca3a07
parentb10547a3cb41fcfd3c6ba469049e39396e6e6baf
Remove e_data_cal_view_register_gdbus_object().

Similar to EDataCal, the first thing we do after creating a new
EDataCalView is export its D-Bus interface.  This was a separate and
failable operation.  If the export fails, the EDataCalView is useless.
Perfect use case for GInitable.

Now we pass the GDBusConnection and object path directly to
e_data_cal_view_new(), and if exporting fails the function sets a
GError and returns NULL.

This also introduces a couple accessor functions:

    e_data_cal_view_get_connection()
    e_data_cal_view_get_object_path()
calendar/libedata-cal/e-data-cal-view.c
calendar/libedata-cal/e-data-cal-view.h
calendar/libedata-cal/e-data-cal.c
docs/reference/calendar/libedata-cal/libedata-cal-sections.txt