On Tue, 2004-05-11 at 14:44, Stewart Heitmann wrote:
> On Tue, 11 May 2004 09:02 pm, Armin Bauer wrote:
> > > I suggest a change to the plugin design to make them easier to develop:
> > > Relax the requirements of the get_changes() function so it simply has to
> > > return a verbatim copy of al
> My feeling is that there aren't enough devices in this specific category
> of "dumb" to make it worthwhile :)
OK, I understand.
The idea could always be incoprorated at a latter date if you have a change of
heart.
I must be unlucky because the two devices I want to sync (KDE Addressbook and
On Tue, 11 May 2004, Stewart Heitmann wrote:
> On Tue, 11 May 2004 09:02 pm, Armin Bauer wrote:
> > > I suggest a change to the plugin design to make them easier to develop:
> > > Relax the requirements of the get_changes() function so it simply has to
> > > return a verbatim copy of all items
On Tue, 11 May 2004 09:02 pm, Armin Bauer wrote:
> > I suggest a change to the plugin design to make them easier to develop:
> > Relax the requirements of the get_changes() function so it simply has to
> > return a verbatim copy of all items held in the device (regardless of
> > state).
>
>
On Tue, 2004-05-11 at 12:45, Stewart Heitmann wrote:
> Good, I'm pleased you find my contributions useful.
>
> However you only partially answered my question.
> You explained that some devices natively support ADD/MODIFY/DELETE status,
> and other devices only support ADD/MODIFY (indirectly via
Good, I'm pleased you find my contributions useful.
However you only partially answered my question.
You explained that some devices natively support ADD/MODIFY/DELETE status,
and other devices only support ADD/MODIFY (indirectly via timestamps) and
yet others support none. But that is not my que
The plugin doc is up at:
http://www.multisync.org/developer/plugin_howto.html
It looks pretty good. I need to review a few of the details (memory
management, etc.) and give it some more review before giving it to a wider
audience. This should be a very useful document, so thanks for getting it
Hi Armin,
Yes it will be good for multisync to bridge the Gnome-KDE divide.
No, you shouldnt have to do anything special to test the KDE plugin,
except you may have to edit some include file paths in the src/Makefile
to suit your installation.
Of course, it would be wise to backup your KDE addres
Hi,
thanks for you work! There are actually quite some people how want to
use applications besides evolution, so i guess your plugin will help
multisync great time
On Wed, 2004-05-05 at 05:15, Stewart Heitmann wrote:
> Here is the first draft of KDE plugin code as promised.
>
> I have tested it
Hi,
thanks for you work! There are actually quite some people how want to
use applications besides evolution, so i guess your plugin will help
multisync great time
On Wed, 2004-05-05 at 05:15, Stewart Heitmann wrote:
> Here is the first draft of KDE plugin code as promised.
>
> I have tested it
Stewart,
Just wanted you to take the lack of a response so far as me being very
busy and not a lack of interest :)
I will review the document you sent last Sunday and the KDE plugin code
this weekend, and get the code into CVS if it looks ready. If you would
like to maintain this I will talk to B
Here is the first draft of KDE plugin code as promised.
I have tested it against the backup plugin and another
test plugin I wrote myself. It seems to work OK but definitely needs
more extensive testing. Any volunteers?
BTW my machine is FreeBSD 4.9-STABLE with multisync 0.81 and 0.82 and KDE 3.2
12 matches
Mail list logo
