I'll think I'll manage to get most of the critical parts of the media player running in native code without much effort. (I developped a dynamic ELF loader in 68K that enables me to use globals in my arm code, so actually I won't have to change that much) Of course, it will be easier with the next release of the OS.
David "Ben Combee" <[EMAIL PROTECTED]> wrote in message news:111126@palm-dev-forum... > > At 18:24 2003-1-29 +0100, you wrote: > >Thanks for the explanation. > >(But what I don't understand is how licensees can build native apps then. > >And if they can, what is the reason (be it technical or commercial) that > >regular developpers can't). > > The reasons are business related. > > PalmSource doesn't want a ARM-native API available that will cause > applications to be tied to the specifics of Palm OS 5. The don't want two > breaks where developers have to learn new APIs, just the one big one that > will happen with the next big Palm OS release. They also don't want > developers to have to change tool sets twice. OS 5 was originally intended > to be a stopgap OS release, to be quickly followed by their new ARM-native > OS, and because of this, going and documenting the internals of something > that wouldn't be around long didn't make sense. > > If you really are doing a radical media player for the Palm OS, you ought > to try to get sponsorship from Sony or Palm or another licensee. The only > way to do fully native OS 5 apps is with their cooperation. > > -- > Ben Combee <[EMAIL PROTECTED]> > CodeWarrior for Palm OS technical lead > Palm OS programming help @ www.palmoswerks.com > > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
