The google addressbook backends only allows writes while online, and I
need to reliably detect this and display the editable state in
Gnome Contacts. The addressbook readonly property is propagated via
folks, so theoretically this should be doable. However, a series of
failures is causing problems
Hi everyone.
In evolution-kolab [1], we use an IMAPX derivative for accessing
the Kolab groupware server via IMAP.
Since
(a) Camel does not expose IMAPX directly and
(b) IMAPX is not yet cleanly subclassable in all aspects and
I need to keep a copy of upstream IMAPX in the evolution-kolab
On Fri, 2012-02-03 at 15:53 +0100, Christian Hilberg wrote:
I need to replicate some code paths of IMAPX (e.g. all paths that
lead from the Store to imapx_untagged, so I can extend this one
for ANNOTATEMORE and later IMAP ACL). Hence, there is some IMAPX
code duplication I cannot avoid at
On Fri, 2012-02-03 at 11:38 +0100, Alexander Larsson wrote:
IMHO we should implement actual network availibility tracking in
EDataFactory (using NM or ConnMan) to get the real state inside the
backends (i.e. if there is no network the backends should always be
offline).
Alex and I talked
Hi Matt,
Am Freitag 03 Februar 2012, um 16:46:50 schrieb Matthew Barnes:
On Fri, 2012-02-03 at 15:53 +0100, Christian Hilberg wrote:
I need to replicate some code paths of IMAPX (e.g. all paths that
lead from the Store to imapx_untagged, so I can extend this one
for ANNOTATEMORE and later
On Fri, 2012-02-03 at 11:13 -0500, Matthew Barnes wrote:
On Fri, 2012-02-03 at 11:38 +0100, Alexander Larsson wrote:
IMHO we should implement actual network availibility tracking in
EDataFactory (using NM or ConnMan) to get the real state inside the
backends (i.e. if there is no network
On Fri, 2012-02-03 at 21:27 +, Philip Withnall wrote:
This sounds good. Do I have to make any fixes to the Google Contacts
address book backend, or will it all be handled centrally? (i.e. With
this GNetworkMonitor change, will there be any bugs left in the Google
backend’s handling of
