On Thu, 2010-07-01 at 14:42 +0200, Patrick Ohly wrote:
> On Thu, 2010-07-01 at 08:58 +0200, Milan Crha wrote:
> > I'm working on a way to be able to report detailed errors from
> > addressbook/calendar backends to UI, so users will be able to see
> > something more sensible than just "Other error"
On Thu, 2010-07-01 at 12:43 -0400, Matthew Barnes wrote:
> If I understand all this correctly, it looks like what's being done here
> is allowing backends to report both an error code and a detailed error
> mesage to the client library, rather than having to set some generic and
> often less-than-h
On Thu, 2010-07-01 at 17:55 +0200, Patrick Ohly wrote:
> If this was about the synchronous APIs that SyncEvolution depends on,
> then I'd be really worried about this change. If those functions are not
> changed, SyncEvolution binaries from syncevolution.org will continue to
> work (full list of c
On Thu, 2010-07-01 at 14:57 +0200, Milan Crha wrote:
> for EBook it is, all the async API there uses 'status' as an indicator
> of the operation result in the async callback. I'm changing it to GError
> too. I'm still on ECalBackend, but it seems some similar change will be
> in ECal too, though I'
On Thu, 2010-07-01 at 14:57 +0200, Milan Crha wrote:
> On Thu, 2010-07-01 at 14:42 +0200, Patrick Ohly wrote:
> > Will that break libebook and libecal APIs? The issue only mentions
> > backends, but the subject of your emails includes "EBook" and "ECal".
>
> Hi,
> for EBook it is, all the as
On Thu, 2010-07-01 at 14:42 +0200, Patrick Ohly wrote:
> Will that break libebook and libecal APIs? The issue only mentions
> backends, but the subject of your emails includes "EBook" and "ECal".
Hi,
for EBook it is, all the async API there uses 'status' as an indicator
of the operation re
On Thu, 2010-07-01 at 08:58 +0200, Milan Crha wrote:
> I'm working on a way to be able to report detailed errors from
> addressbook/calendar backends to UI, so users will be able to see
> something more sensible than just "Other error" message in Evolution.
> This is bug report for this [1], which
On Thu, 2010-07-01 at 13:41 +0200, Christian Hilberg wrote:
> On Thursday 01 Juli 2010 at 08:58:32 Milan Crha wrote:
> > Hi all,
> > I'm working on a way to be able to report detailed errors from
> > addressbook/calendar backends to UI, so users will be able to see
> > something more sensible t
On Thursday 01 Juli 2010 at 08:58:32 Milan Crha wrote:
> Hi all,
> I'm working on a way to be able to report detailed errors from
> addressbook/calendar backends to UI, so users will be able to see
> something more sensible than just "Other error" message in Evolution.
> This is bug report fo
