On 02/01/2013 05:08 AM, Matthew Barnes wrote:
On Thu, 2013-01-31 at 20:47 +0100, Milan Crha wrote:
I vote for Tristan's 2), basically because it's the right approach in
client-server architecture, also used in evo-mapi (and maybe in evo-ews,
I do not know). Basically, if client doesn't have anyt
On Thu, 2013-01-31 at 20:47 +0100, Milan Crha wrote:
> I vote for Tristan's 2), basically because it's the right approach in
> client-server architecture, also used in evo-mapi (and maybe in evo-ews,
> I do not know). Basically, if client doesn't have anything it was asked
> for, then it doesn't me
On Thu, 2013-01-31 at 08:11 -0500, Matthew Barnes wrote:
> On Thu, 2013-01-31 at 18:25 +0900, Tristan Van Berkom wrote:
> > I'm not sure what the solution should be exactly, but we
> > should discuss this a bit because the problem space is
> > a little bigger than just the source existing in the
>
On Thu, 2013-01-31 at 18:25 +0900, Tristan Van Berkom wrote:
> I'm not sure what the solution should be exactly, but we
> should discuss this a bit because the problem space is
> a little bigger than just the source existing in the
> client-side before e_source_registry_commit_source_sync()
> retur
On 10/06/2012 09:01 AM, Matthew Barnes wrote:
On Fri, 2012-10-05 at 22:19 +0900, Tristan Van Berkom wrote:
a.) e_source_registry_commit_source_sync() seems not exactly
very sync. I haven't looked into that in detail but
surely the registry server needs to block on something e
On Fri, 2012-10-05 at 22:19 +0900, Tristan Van Berkom wrote:
>a.) e_source_registry_commit_source_sync() seems not exactly
>very sync. I haven't looked into that in detail but
>surely the registry server needs to block on something else
>before sending the reply.
The is
On 10/05/2012 09:00 PM, Matthew Barnes wrote:
On Tue, 2012-10-02 at 20:35 +0900, Tristan Van Berkom wrote:
Ah, this is gold.
I'll be able to readjust things with this.
I've added a new section to the migration guide which covers the basics
of creating a new local address book or calendar:
ht
On Tue, 2012-10-02 at 20:35 +0900, Tristan Van Berkom wrote:
> Ah, this is gold.
>
> I'll be able to readjust things with this.
I've added a new section to the migration guide which covers the basics
of creating a new local address book or calendar:
https://live.gnome.org/Evolution/ESourceMigrat
On 10/02/2012 08:29 PM, Patrick Ohly wrote:
On Tue, 2012-10-02 at 13:30 +0900, Tristan Van Berkom wrote:
I'm still trying to find my footing here, the migration guide
and new documentation on ESourceRegistry don't seem to outline
how a new addressbook is actually created.
i.e. if I wanted to te
On 10/02/2012 01:30 PM, Tristan Van Berkom wrote:
On 10/01/2012 09:08 PM, Dan Vrátil wrote:
On Monday 01 of October 2012 20:41:07 Tristan Van Berkom wrote:
Hi,
It's recently come to my attention that a vast API break[0] has
been introduced in the last (3.6) cycle of EDS.
Unfortunately thi
On Tue, 2012-10-02 at 13:30 +0900, Tristan Van Berkom wrote:
> I'm still trying to find my footing here, the migration guide
> and new documentation on ESourceRegistry don't seem to outline
> how a new addressbook is actually created.
>
> i.e. if I wanted to test a specific addressbook backend,
>
On 10/01/2012 09:08 PM, Dan Vrátil wrote:
On Monday 01 of October 2012 20:41:07 Tristan Van Berkom wrote:
Hi,
It's recently come to my attention that a vast API break[0] has
been introduced in the last (3.6) cycle of EDS.
Unfortunately this also breaks the vast majority of the test cases
i
On Monday 01 of October 2012 20:41:07 Tristan Van Berkom wrote:
> Hi,
> It's recently come to my attention that a vast API break[0] has
> been introduced in the last (3.6) cycle of EDS.
>
> Unfortunately this also breaks the vast majority of the test cases
> in EDS proper as well as the benchm
Hi,
It's recently come to my attention that a vast API break[0] has
been introduced in the last (3.6) cycle of EDS.
Unfortunately this also breaks the vast majority of the test cases
in EDS proper as well as the benchmarking tests[1] we've been using
to track EDS performance over releases.
Af
14 matches
Mail list logo