![]() |
2006-04-19
, 01:24
|
Posts: 160 |
Thanked: 1 time |
Joined on Mar 2006
|
#2
|
![]() |
2006-04-19
, 03:48
|
|
Posts: 1,245 |
Thanked: 421 times |
Joined on Dec 2005
|
#3
|
That would be great. But since Jpilot already runs on the desktop and 770, would it be easier to do the sync with some sort of an rsync script? Perhaps wirelessly? I started to write a script, but it seems the data files are encoded differently between the 770 and the desktop version of jpilot.
![]() |
2006-04-20
, 01:10
|
Posts: 160 |
Thanked: 1 time |
Joined on Mar 2006
|
#4
|
I noticed the same thing when trying to transfer all my old Palm PIM data from my PDA to JPilot (on the desktop) to JPilot (on the Nokia 770). The Dates database was the one I had most trouble with, but the Notes were the only things that transferred smoothly. Now I'm focusing on sync'ing with the Exchange server at my workplace (through Evolution and its evolution-exchange capability), which will probably be more useful to me in the end.
![]() |
2006-04-20
, 14:33
|
|
Posts: 1,245 |
Thanked: 421 times |
Joined on Dec 2005
|
#5
|
I have been trying for quite a while to get the DatebookDB to transfer, but I am getting nowhere. No matter what changes I make, Jpilot on the Nokia will not see any Date data, or crash. I compared DatebookDB.pdb and Datebook.pc3 files created on the Nokia to those created on the desktop and think I have them in same encoding, but still no joy. Did you ever get your dates to transfer? If so what did you do? I was able to get Address and Notes to transfer. My versions of Jpilot are the same on both devices (0.99.8) so you would think the data files would be interchangeable. I really would prefer not to use .csv import as I would like to get a wireless sync set up.
![]() |
2006-04-20
, 14:56
|
Posts: 160 |
Thanked: 1 time |
Joined on Mar 2006
|
#6
|
I was unable to transfer dates in any useful format at all... even the .csv import messed up the data beyond usefulness. It must be some bug introduced in the Nokia 770 version of JPilot, although I can't imagine why that code would have been changed.
Anyway, I personally am not considering a direct JPilot-JPilot sync, simply because I don't really like JPilot on the desktop, and it can't sync with an exchange server. Evolution w/ exchange support is nice, so if I can get Evolution to sync with JPilot on the Nokia 770, I'll be all set.
If I could modify gnome-pilot or pilot-link to understand and synchronize with USB-based file systems (e.g. mounted to /media/whatever), I could potentially utilize the existing gnome-pilot Evolution plugin (with perhaps a bit of modification) to synchronize between Evolution and a directory structure on the Nokia 770.
At first, I was considering JPilot as the target PIM application on the Nokia 770 (or possibly DejaDesktop), but the work on eds-dbus (the "Embedded Evolution Data Server") being done by the folk at openedhand.com could make the whole concept a lot easier. I'm wondering whether to even bother trying to hack up something else.
Assuming, however, that I'm an impatient person that can never wait for anything, does my proposal sound like a reasonable approach? A few caveats that I can already see:
These are hardly serious issues, though. One bonus of using gnome-pilot/pilot-link is that the functionality can be initiated via the command-line instead of requiring Evolution. I'm not sure how much of gnome-pilot/pilot-link I can actually reuse, though, since my impression is that they're very Palm-oriented, though maybe that's a good thing since JPilot (and it's data back end) is also Palm-oriented.
Any thoughts or suggestions?