Remove e_data_cal_register_gdbus_object().
authorMatthew Barnes <mbarnes@redhat.com>
Sun, 7 Oct 2012 22:23:56 +0000 (18:23 -0400)
committerMatthew Barnes <mbarnes@redhat.com>
Sun, 7 Oct 2012 22:36:08 +0000 (18:36 -0400)
commit36d0cef62397b9cde55f18c21d089b9510af6997
tree7348454fd23462a61463ebc14be6402c5777521f
parent18160b6a920d6f1d0dc66f830a3a8297fce35f05
Remove e_data_cal_register_gdbus_object().

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

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

This also introduces a couple accessor functions:

    e_data_cal_get_connection()
    e_data_cal_get_object_path()
calendar/libedata-cal/e-data-cal-factory.c
calendar/libedata-cal/e-data-cal.c
calendar/libedata-cal/e-data-cal.h
docs/reference/calendar/libedata-cal/libedata-cal-sections.txt