James, On Thu, 14 Dec 2006, James Youngman wrote: > I recently upgraded from a Treo 600 to a Treo 650. I'm happy with the > result, but have noticed that the new fields in the Contacts > application aren't supported. For example, the Birthday field. I > understand that the same goes for other fields like additional > address, but I haven't used those. > So, when I edited a contact entry in JPilot and resynced, the birthday > attribute was essentially deleted (since JPilot somehow didn't > preserve the unsupported fields of the updated record). This surprises me, I'd expect your jpilot to sync against the backwards-compatibility layer AddressDB, and persist any such fields. > Is there any plan to update JPilot to support the new fields? If not, > is there any plan to have it warn the user that they would be about to > update a record containing unsupported fields? I believe Judd is well under way with a GUI to support these fields in jpilot proper. Judd originally wrote the backend support that Jppy uses (in pilot-link), in fact. > I saw the post at > http://www.jpilot.org/pipermail/jpilot/2006-February/005806.html but > that's really old now. I was hoping the situation might have > progressed a bit. > I also understand that Jppy might fix this (web page at > http://jppy.zanu.org.uk/Wiki). I didn't see any source packages for > it. Is it essential to just pull a SVN source tree and build it that > way? Yeah, there is no source package (yet?). As others suggest, you should be able to build from an svn export easily enough. If you really do need a source package, then I'll see what I can organise. It'll need doing for when it goes into Debian anyway. (Unless you mean a source-rpm, which is unlikely to happen I'm afraid.) Nick -- Nick Piper, Developer, LogicaCMG http://www.nickpiper.co.uk/ GPG Encrypted mail welcome! 1024D/3ED8B27F Choose life. Be Vegan :-) Please reduce needless cruelty + suffering !
More information about the jpilot mailing list