Don't know what all this noise about. I believe that any developer creating a commercial Palm program should try to make it compatible to at least OS 3.5 Think about all those people who still have a M100 or M105
LionScribe "Chris Tutty" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > From: "Marvin Bellamy" <[EMAIL PROTECTED]> >> I'm going to need to port a Palm OS 4 application back to 3.5, > specifically m105 handhelds. I have a few questions about setting up my > development environment since most 3.5 links I've found on Palm's site > seem > to be dead: >> >> Where can I get the 3.5 SDK and can it be dropped into PODS? >> > You don't need to change SDK's. They're all backwards compatible, > in the sense that you target an older Palm OS version by limiting the > API calls you make. More recent SDK's can still be useful because > (possibly) the Glue functions might have improved to provide support > for functions that 3.5 doesn't support. > >> Are there any significant SDK changes between 3.5 and 4.0 that I >> should look out for? >> > Depends on your app since many of the changes were hardware > driven. Connectivity APIs were added, extended and broken in > different ways. I don't remember whether the colour and hi-res > stuff came in at 3.5 or 4 but I seem to remember changes to the > way forms drew themselves. The features documentation is a > good indication of what OS version things were introduced. > > PalmSource don't document a lot of the API faults version-by- > -version (this is, IMHO, the most significant deficiency in otherwise > excellent documentation) so you've really got to test carefully and > google for any strange results. It's generally OK if you're targeting > a specific device, but becomes a lot more complicated if you have > to support a range of devices across 3.5 and 4. Been there, done > that, got the scars. > > Chris Tutty > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
