BeHotSync

Main Repository Page

Utilities

Miscellaneous

BeHotSync Download

Description:

A framework application that manages add-ons to synchronize data between a PalmPilot and the BeOS.

-----------------------

This version of BeHotSync includes Add-Ons to handle the Contacts (Address), ToDo, Notes and Calendar
databases of your Palm Pilot. Of these provided add-ons the currently most functional is the Contacts
add-on which will synchronise your Pilot and Be People databases. ToDo, and Notes will dump their data into text
files in /boot/home/todo & /boot/home/notes respectively but they will NOT synchronise the contents of these
directories. No data for these two databases will be transferred back to your Pilot. The Calendar add-on is
currently non-functional (it will not crash your machine), however the data it retrieves from your Pilot is simply
ignored.

The SDK tarball provides all that is needed to write your own add-ons for BeHotSync.
This should allow folks who wish to synchronise their Pilot to different applications to do so.
Whilst the documentation is (at this time) minimal source code is included for a sample add-on,
and I'm available via email (awk@awkward.org) if you have questions (check out the pilot-link for Unix source
code for hints and tips too).

CHANGES IN THIS VERSION
-----------------------
BeHotSync now supports being installed into the deskbar as a replicant (use BeHotSync -deskbar)
This has introduced a fairly major change to the function prototypes for instantiating an addon
and also to how an addon should send messages to its 'host'. Put simply you should not call
be_app->PostMessage() anywhere in your addon (be_app may point to the Deskbar if the app has been
run that way). Rather you should keep use the BLooper pointer that is passed during initialization
of the addon in place of be_app (ie fLooper->PostMessage()). Take a look at the sample addon if
you need more assistance (or email me at awk@awkward.org). Also currently if invoked to run as
a replicant BeHotSync expects to find add-ons in /boot/home/config/hotsync/add-ons, this may change
or be adjusted in a future release to be a little more friendly. If invoked as a regular application
then the behaviour is the same as previously add-ons are searched for in the 'add-on' subdirectory
of the directory containing the executable.

Submitted On:

26 Mar 2008

Submitted By: