>>>>> "David" == David A Desrosiers <[EMAIL PROTECTED]> writes:

Jack> Here is where we have a more difficult time than the Windows
Jack> folks. They have a single operating system to work with.  In the
Jack> Palm Desktop application, there is a way to enable "Local USB"
Jack> separately from "Local Serial".

David> *COUGH* and API documentation and vendor assistance *COUGH*

And a zillion other little things that don't quite make up for the
fact that they have to deal with Windows. ;-)

Jack> I suggest that pilot-xfer do something like what coldsync has
Jack> done, which is to add a command-line argument defining what type
Jack> of physical interface is in use.

David> Note: Latest bleeding edge ColdSync won't even work with IR on
David> my machine, and definately doesn't support the m505 over USB,
David> nor does it currently support the m505 when the password is set
David> on the device.

You're ahead of me.  The last two are things I had hoped to try with
the stock coldsync as supplied by FreeBSD's ports.

Jack> That allows for other forms of expansion as necessary and still
Jack> maintains a simple interface.  Yes, it'll require the user to
Jack> know the difference between usb and serial, but I don't feel
Jack> that's a significant hurdle.

David> I'm considering quite a large architecture change to
David> pilot-link, to decouple the actual device-conversation logic
David> from the data-conversation logic. Need to flush out the bugs in
David> the soup first.

Exciting stuff.  Can't wait to see it, especially if it just 'does the
right thing' with respect to fast and slow syncing for addresses. :-)

Jack.
(so I've got a one-track mind today.)
-- 
Jack Twilley
jmt at twilley dot org
http colon slash slash www dot twilley dot org slash tilde jmt slash
_______________________________________________
Pilot-unix mailing list
[EMAIL PROTECTED]
http://hcirisc.cs.binghamton.edu/mailman/listinfo/pilot-unix

Reply via email to