Syncing with J-Pilot via Bluetooth

Probably I am a little bit old-fashioned, but I still use J-Pilot on my PC and my Tungsten T5 and sync them. It mostly serves as a kind of backup so I have my valuable address and datebook data on separate media. So in case my PC gets inaccessible then I have my data on this device at least.

These are the commands I use.

echo 1 > /proc/sys/net/ipv4/ip_forward
/usr/bin/dund --listen --channel 1 --pppd /usr/sbin/pppd call dun
hciconfig hci0 piscan

File /etc/ppp/peers/dun is

debug
115200
noauth
nopersist
local
passive
netmask 255.255.255.0
192.168.178.118:192.168.178.119
ms-dns 192.168.178.1

Continue reading

Advertisements

Possible Enhancements to J-Pilot

Here are some thoughts about possible enhancements for J-Pilot.

  1. Convert pdb’s and pc3’s to sqlite. This makes it easier to analyze data according some criteria, e.g., find how many addresses have the same telephone numbers, how may entries in datebook contain the same substring, etc.
  2. Convert and transform pdb’s and pc3’s to Google GData. The Google id, which is returned after transmitting data, is then possibly stored in pdb/pc3.
  3. Use mmap() instead of all its fread() and malloc()‘s inside pilot-link and J-Pilot.
  4. When J-Pilot searches for strings in the case-insensitive case, then it copies all elements and uses malloc() for each element. Instead, just use a home-brewed strstr() which takes care of case.
  5. Provide ncurses interfaces instead of Gtk. See for example calcurse.