compatibility

[Ftrooper93]

So the big question really should be, what compatibility problems should we expect with existing software (even OS 5) on the UX?


The HUGE advantage Palm has over PPC is really two: PPC is not entirely stable (lots of reboots) and the giant existing palm software base.

What if that software base doesn't work on the UX?

[Cliepro]

The UX has Palm 5.2 much cleaner running Palm OS

[Ftrooper93]

but it only displays in lnadscape mode. Screw the cleaner OS, the issue is whether the diffenrence in layout will prevent you from running existing apps.

[Cliepro]

Originally posted by Ftrooper93
but it only displays in lnadscape mode. Screw the cleaner OS, the issue is whether the diffenrence in layout will prevent you from running existing apps.


In Palm OS 5.2 in a Palm it's seting for normal but thanks to Sony's wisdom and the UX model it's set for Landscape -- Every App I tried works fine on the UX in my testing of the unit

[sonicboy]

I have noticed something VERY INTERESTING..

insaniquarium (HiResPlus version) runs in portrait orientation..

the silk is still present but hey...

PORTRAIT MODE BABY! its been done already!!!! (admitadly by accident but still...)

PORTRAIT MODE BABY!

[lmame]

Oh, you already realized?
I guess that's why Insaniquarium was with the UX software package...

[sonicboy]

it was???

[lmame]

indeed ;)

[EdFrmBrighthand]

Sony said from the beginning that just about every existing application will run fine on the UX series. However, unless they have been specially modified, apps won't be able to close the virtual Graffiti area.

And since the VG area is on the side, rather than the bottom, the UX series uses a different API from the one that handles the VG on the NX series.

Even worse, it is a different API from the ones on the upcoming Tapwave Zodiac and Tungsten T3. How said it was easy developing apps for the Palm OS?

[jamesgood72]

Ed, yes, and probably different from the Garmin PDA too, I guess...

When are PalmSource going to implement a 'reference' API for soft graffitii? Maybe when the T3 comes out, it'll be the 'standard', and everyone will eventually use that. Like Sony switching to the Palm sound API recently.

-James.

[lmame]

Come on ... It doesn't seem to be that hard...
See the softwares already modified (Acid Image, Crs Launcher, ZLauncher, Table Tennis 3D, Mc File, Filez) and the software "to come":
Repligo, Iambic, Splash...

[jamesgood72]

That's not really the point, lmame. It's pretty bad for developers to have to produce six or seven different versions of a program. I would rather they could concentrate on adding functionality to the software...

-James.

[EdFrmBrighthand]

PalmSource does have a standard for virtual graffiti, which it is including in Palm OS 5.3. But this covers just VG areas at the bottom of the screen, not on the side.

PalmSource's policy is to allow its licensees to create their own APIs necessary to support new features. This allows the licensees to develop, with PalmSource's advice, APIs based on "real world" experience, rather than PalmSource developing an API based on theory. Later, PalmSource will create a standard API based on the experiences of all its licensees.

So when several companies decided they wanted dynamic input areas on the side, rather than the bottom, they each had to make up a new system to handle it, and therefore each has a different API.

lmame, I know it's possible. Developers have been very good about adding support for all the different APIs. I just wish it was easier.

If you missed the article about what else it in Palm OS 5.3, you can read about it here:
www.brighthand.com/article/PalmOS_5_3_Seeded_to_Developers

[lmame]

I don't say SONY did a good thing not using "standards" API...

I suffered a lot not to have some softwares on my NX (MMPlay, Pocket Tunes or Aero Player) because of the "selfish sound SONY API"...
Same thing when SONY doesn't allow access to CF port on NX70V...

Then they do a CF Driver for the "new" NX, but Software don't handle it (Audio Player, Movie Player and so on...)

The thing I appreciate on the UX is that I can use MMPlay and other sound softwares because SONY included the PALM sound API (at least)...
The other thing I see is that, on the Screen API thing, that even the Palm OS 5.3 SDK does not handle the 480*320 resolution... So I guess that is a good excuse for SONY still to have their API :)

Now, don't get me wrong, I'm a coder too... I wish things were easy ;)