Menu
▾
▴
#12 Evolution support broken
Hi all.
Apparently, python evolution bindings are broken, which breaks evolution support in gbirthday.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707843
I could easily drop evolution from gbirthday backends, but before doing so, I'd like to be sure it is absolutely useless to anyone.
I found scarce information.
AFAIU, evolution has gone Gtk3 and old python bindings don't work anymore. New bindings should be made using gobject-introspection.
https://lists.fedoraproject.org/pipermail/desktop/2013-November/008476.html
http://koji.fedoraproject.org/koji/buildinfo?buildID=465567
If no such binding has been made already, I guess there is no way to interact with evolution from python.
Anyway, we could drop evolution support and put it back the day we identify a working set of bindings.
Does anybody have any info about this?
Is my understanding correct?
Does anybody have any objection to dropping evolution support from gbirthday?
Thanks.
Related links
https://answers.launchpad.net/gtg/+question/240070
https://bugzilla.gnome.org/show_bug.cgi?id=668787
I think it says that there are bindings that would work, but they are GTK3-based.
I don't see why GTK is involved, here. Is it because the bindings provide much more functions than we use in gbirthday, some of them being graphical?
Maybe gbirthday should be ported to GTK3, anyway, for the future, but I don't feel like doing it. (Since I'm working with Qt, I'd rather port it to PyQt...)
From here (in French): https://linuxfr.org/forums/programmation-python/posts/bindings-python-pour-evolution
We'd need EDataServer from GObject Introspection, which is not GTK.
See here for an example:
http://askubuntu.com/questions/193954/coding-own-applicaion-for-gnome-shell-calendar
Judging by the current code of the Evolution backend, it shouldn't be too difficult, but I didn't find any documented example. I don't think I'll take the time to do this. I don't even use Evolution.
What I suggest is to remove now obsolete Evolution backend, and to put it back the day someone codes it with GObject Introspection. Ideally, making the dependency to gi.repository optional for those who don't use Evolution backend.
Anybody interested in this development is welcome to take part.
Evolution support was dropped in v0.6.8.
"Evolution" still appears in the config file. It is just ignored. The day someone develops a new backend for Evolution, it will be picked up for users with "Evolution" in their config file.