johnm, you know I don’t want to bicker about things like this, especially here. I don’t have the time, patience, or resolve to argue with you about the issues regarding pilot-link. In short, the reason I said it’s a mandatory upgrade is that the sync code that was in 0.9.3 is “questionable” and was removed because of potential GPL concerns.
Also, 0.9.3 will not work with most of the supporting applications that might continue to use it, such as Evolution,
gnome-pilot, and possibly others such as PilotManager, JPilot, etc. If people want to continue to use 0.9.3, and ignore some of the licensing issues, and an occasional corrupted record here or there, that’s fine. I’m not forcing anyone to upgrade, just that compatibility will break if they choose to use 0.9.3 with some of the newer GUI-based apps.
Maybe “mandatory” was bad phrasing. Let’s call it “necessary”, or “critical” or something else then.
As for the layout at tool launch time, that silly splash, reminder: It does say -pre5 on it, no? Any code can be added removed for a final release. It’s my intention to move all of the argument parsing out (probably using popt or getopt() in a proper lib), and make it uniform between binaries. Until I do, some will act different than others.
Speaking of patches… the only message I’ve received from you directly or on the list regarding pilot-link referencing patches (not general webpage or SourceForge banter) was on Thu, 19 Oct 2000 15:31:55 -0700 (PDT), referencing the PILOT_LINK_PATCH stuff. I’ve already fixed that (and screwed up the branch, which jpr had to resurrect).
If there are other patches I haven’t received, if you could email them to me, I will include them. Other than that, I haven’t seen anything, and you already know that I’ve been / including / patches, so you’re not being ignored.
I await your patches and suggestions to improve the package.