On Oct 29, 2006, at 1:54 PM, Steve Hammond wrote:
>> just another app that uses it, and integrating a Newton device might
>> actually be counterproductive (unless telephone numbers are the only
>> thing one is interested in).
>> ----
>
> I'm not sure I'm getting your point here, can you elaborate?
Opps, yes. The Sync Services are part of the OS. You can sync any
(Sync Services based) application's data with any device simply by
requesting a class of data (Sync Schema) from the Truth Database. So
we could write an application that requests phone data, appointments,
etc from the truth database, but also provide all the other
maintenance and transfer needs (installing packages via dnd, etc.).
That way, there would be only a single app managing Newton transfers.
iSync does centralize the phone and appointment synching somewhat,
but it has no interface for all the other functionality. So we still
need a second app to install packages and handle data not part of
Sync Services.
On the other hand, allowing the above app to be started through iSync
shouldn't be too difficult either. I just have not found that
documentation yet.
BTW: Thanks for the initial links.
Matthias
---- http://robowerk.com/ -- This is the NewtonTalk list - http://www.newtontalk.net/ for all inquiries Official Newton FAQ: http://www.chuma.org/newton/faq/ WikiWikiNewt for all kinds of articles: http://tools.unna.org/wikiwikinewt/Received on Sun Oct 29 12:26:46 2006
This archive was generated by hypermail 2.1.8 : Sun Oct 29 2006 - 13:30:01 EST