The Palm sync is made of several layers. These are documented on the Palm
web site. Take a look at
http://oasis.palm.com/dev/kb/manuals/article.cfm?id=1770#925615. This
documents the lowest part of the protocol. The other layers are there as well.
By writing a Newton app that follows this protocol and the layers above it,
we'd have it cracked!. There would be no need for any external conversion
at either end, you'd just run the new syncer on the Newt, your chosen Palm
sync app and Bingo!
At 17:06 30/04/2002 -0400, you wrote:
>That's brilliant! I can't believe I didn't see that before. There's almos=
>t
>always a Palm sync option on the programs I use cause Palm is so universal.
>If only we could trick the application to think we are using a Palm. Or
>convert Newt syncing data to a Palm format. I'd bet that's pretty difficul=
>t
>to do, but man would it solve our problem!
>
>Steps:
>1) Determine how a Newton sends/recieves sync information
>2) Determine how a Palm sends/recieves sync information
>3) Compare and Contrast between the two
>4) Develop a conversion program
>5) Um... Develop an I/0? Is this necessary?
>6) Anything else I'm forgetting?
>
>We already have Newt developers (and a Newt dev list.) Now we just have to
>study Palms closer.
-- Read the List FAQ/Etiquette: http://www.newtontalk.net/faq.html Read the Newton FAQ: http://www.guns-media.com/mirrors/newton/faq/ This is the NewtonTalk mailing list - http://www.newtontalk.net
This archive was generated by hypermail 2.1.2 : Wed Jun 12 2002 - 20:01:35 EDT