On Thu, 2010-12-09 at 11:00 -0500, Matthew Barnes wrote:
> Overall the changes are having a simplifying effect on the code base,
> but it will introduce an API break of some kind to almost every library
> in E-D-S.  That's what I wanted to talk about here.

Couple more API breaks to mention which turned out to be happy
accidents: we no longer need e_book_remove() or e_cal_remove(),
nor the corresponding D-Bus methods.

Both the e-addressbook-factory and e-calendar-factory processes will
have their own ESourceRegistry instance, and ESourceRegistry monitors
your "sources" directory for changes and emits "source-added" and
"source-removed" signals in response to new or deleted key files.

Since removing an address book or calendar source will be as simple as
deleting its key file, in theory the backend process should be notified
of the file deletion event by its ESourceRegistry and can then clean up
after itself on its own without being told to by the client.

I should get far enough to actually verify that today or tomorrow.

evolution-hackers mailing list
To change your list options or unsubscribe, visit ...

Reply via email to