Primarily, I'm working to provide an abstraction layer by which
plug-ins can get a Newton soup cursor in Cocoa. I'm also providing a
framework to provide interface feedback and custom settings panels. The
plug-ins can also execute NewtonScript code on the Newton. As for
Java... my goal is to provide a world-class Mac OS X application, and
for this case, Cocoa is hands-down the best way to go. I get access to
all of the Mac OS X interface goodies, and I can develop a faster
application with a smaller memory footprint with a lot less development
effort.
I've worked on a couple of Java servlets and think that Java is a
hard-to-beat platform for web apps, but I'm not sold on the language
for this particular solution. That being said, my software will
eventually be open-source, at which point some enterprising developer
could port it. :-)
John
> If the interface between the sync app and the plug-ins was both
> public and complete, then it would encourage people writing new sync
> apps to use it. In the case of Unix and OSX, for instance, you could
> use
> the same sync program on both OSes. You'd probably use different
> plug-ins for each, since each OS supports a different collection of
> PIMs
> & such, but the sync program would be the same.
-- Read the List FAQ/Etiquette: http://www.newtontalk.net/faq.html Read the Newton FAQ: http://www.chuma.org/newton/faq/ This is the NewtonTalk mailing list - http://www.newtontalk.net/
This archive was generated by hypermail 2.1.2 : Thu Oct 31 2002 - 12:02:19 EST