>>>>> In article <[EMAIL PROTECTED]>, Arnd Kohrs <[EMAIL PROTECTED]> writes:
>>>>> "Thomas" == Thomas E Deweese <[EMAIL PROTECTED]> writes:
>>>>> "AK" == Arnd Kohrs <[EMAIL PROTECTED]> writes:
>>>>> "Thomas" == Thomas E Deweese <[EMAIL PROTECTED]> writes:
[Did I miss the beginning of this ?]
Arnd> Oops sorry, I assumed that Palms are always shipped with the Windows
Arnd> HotSync manager.
They are. I used it to set up my Palm, and to set up and sync with
Avantgo until I got MALsync for PilotManager up and running properly.
I do not use it now as I do not use Windows; nor do the majority of
Emacs/BBDB users.
Do I take it you do use Windows and use Emacs/BBDB with Windows ?
I have a UNIX workstation on my desk (hmm actually it's got a
PC-on-a-card in it as well, but I only use it if I have to and I'd
have to keep switching the serial cable around), so PilotManager and
its conduits work fine for me.
Arnd> AFAIK, and I might be wrong, each synchronization manager (HotSync in my
Arnd> case) has proprietary interface and conduits for one synchronization
Arnd> manager are incompatible with other synchronization managers. Please
Arnd> tell me that I am wrong, because I am tempted to plug syncBBDB into
Arnd> HotSync.
That seems (regrettably) to be the case. There are Windows and Mac
hotsync tools available from Palm, that Palm provide an SDK for.
You'd need to compile a separate mac and windows binary for your
conduit. There's a Java SDK as well, but I don't know if it's
portable or Windows only (which seems to defy the point to me).
The other hotsync tool I've used is the one shipped with Solaris 8.
It's Java based, but seems to have its own, undocumented, conduit
interface and very few conduits available.
PilotManager, OTOH, is written in Perl, which is cross platform and
has documented conduit interfaces and many example conduits. It
shouldn't be that hard for a competent programmer to code up a new
conduit to replace one that's missing (in your case perhaps a
DateBook<->some Windows calendar app conduit ?)
Arnd> Well, I can't really argue with you on this point, since You have
Arnd> written a conduit already and made your experience. Unfortunately, I
Arnd> cannot use the synchronization functionality of syncBBDB at all because
Arnd> it requires me to install a new operating system and a new
Arnd> synchronization manager and abandon all conduits which don't exist for
Arnd> the PilotManager.
IIRC SyncBBDB comes with a minimal harness for running it without
PilotManager. Of course you'd have to run it separately from your
regular hotsyncs; I managed that for a while to get AvantGo, but I
only needed to do it once a day.
Arnd> for me) - or even better somebody knowledgeable of HotSync could use
Arnd> those tools to build a conduit for HotSync manager.
I suggest it might not be impossible for someone to use Palm's (Java?)
conduit SDK to write a wrapper which would fire up Perl to run a
PilotManager conduit. Might be of limited use, though, as I can't see
any of the other conduits being very useful on Windows (with the
possible exception of SyncCM if you bought CDE for Windows).
I suspect that demand for a BBDB conduit that runs on Windows with
Palm's HotSync manager is likely to be very small., though perhaps
the majority of Windows Emacs users are likely to be hacker types who
ought to be able to write such a conduit...
--
Kevin Davidson Decisionhouse Systems Group
Quadstone Limited 16 Chester Street, Edinburgh, Scotland, EH3 7RA
Tel: +44 (0)131 220 4491 Fax: +44 (0)131 220 4492
_______________________________________________
bbdb-info mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/bbdb-info
