Note that it can only decode database files that have been archived by a synchronization software. It does not implement a synchronization conduit, i.e. it cannot do synchronization on the fly. Implementing a conduit would have been much more difficult, because it would have required to integrate into an existing PDA synchronization framework such as KDE’s Kitchensync framework, etc.
To implement this module, I read the official Palm® file format documentation, and I looked at the implementation of p5-Palm, a collection of Perl5 modules for reading and writing Palm® database files. It must be noted that my rewriting into Erlang is much more concise and readable than the Perl implementation. Erlang’s binary pattern matching feature really makes a difference. Although Perl is unsurpassed when manipulating text, I believe that Erlang is the best programming language to manipulate binary data, even in small script-like modules like this one.
I have developed a small module that uses the
palm_db module for generating files for the GNU Emacs Diary application:
palm_datebook_to_diary.erl. This module is not complete: it does not support repeated entries, nor alarms, etc. Yet, it is still useful in practice.
To use it, you must first save your Datebook database using your synchronization software. For instance, when I use KDE’s Kpilot under GNU/Linux, that database is saved in file:
~/.kde/share/apps/kpilot/DBBackup/pda_profile_name/DatebookDB.pdb. To decode this file and generate an Emacs Diary file, execute:
> erl -noshell -run palm_datebook_to_diary start ~/.kde/share/apps/kpilot/DBBackup/pda_profile_name/DatebookDB.pdb -run init stop > ~/diary
Then, in Emacs, you can display the diary for the current date by executing the
M-x diary command.
The code of those modules is distributed under the GPL.