At 9:20 AM +0100 2001/12/24, Thomas Maeder wrote: >David Fedor wrote: >> >> Yes. We talked about this at last year's PalmSource. > >Do you suggest that I consider PalmSource talks as technical documentation >to base my development on?
All sources of information should be used to gain knowledge of upcoming Palm developments! This includes information discussed in this forum, our http://www.palmos.com web site, videotaped archives of PalmSource events, developer sync-up events, special announcements and press releases (to name a few). >How can you >imagine that software be developed for the PalmOS if you remove >functionality without notice - and the only place where such notice can be >placed is the SDK. That's simply not true. As but one example, these issues have been discussed in this forum many times over the last year. > > We certainly see the value of having a system that can be extended in >> these sorts of interesting ways, never fear. But it would be a mistake >> to assume that the system will always behave exactly as it does today, >> including all of its undocumented internal structures, particularly when >> you're talking about a different processor and endianness and so forth. >> Not to mention new capabilities and great fundamental improvements. > >I am *not* writing about "undocumented internal structures". True, but you're talking about using functionality that *cannot* be supported in a future version of the Palm OS. See the forum archives for discussions of why. This is software evolution... nothing more, nothing less. We're very sorry if the upcoming API changes to Palm OS have caught you by surprise. However, we've been warning developers against the use of trap patching for years now, and providing information and tools well in advance of any actual shipping product. Best Regards, Jim Schram Palm Incorporated Partner Engineering -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
