Trinition
Member
Registered: Oct 1999
Location: Cincinnati, OH
Posts: 109 |
Two important points have been brought up in this thread that I'd like to expand on:
1: Higher Resolution
Most WinCE/PPC PDAs do 320x240. Now, I feel they do this so they can have fancier looking widets, etc. and sharper fonts. I don't think either of those is a bad idea.
But there of course would be the bacwards compatability problem. You certainly don't want an old program showing up in the upper-left quarter of your screen. I suggest making the new PalmOS which supports such reslutions to default into a double-pixel mode (everything is lit up in 2x2 chunks). If a newer program is written, it could take advantage of a system call which puts it into that higher-resolution mode where pixels are indivually addressable again.
Other people have suggested a 320x240 resultion, but I suggest 320x320. 320x240 has the advantage of being quarter-VGA resolution. But on the PalmOS, we have no legacy reason to use that. The advantage of 320x320 is that it would make emulating 160x160 extremely simple. Furthermore, PalmOS devices already use a screen with a 1:1 aspect ratio. If we swtiched to 320x240 either the aspect ratio of the pixels or the screen as a whole would have to change. At 320x320, a 1:1 aspect ratio is maintained for both.
With higher resoltuions, we could have better graphics, a sharper UI, more readable fonts, etc.
2: Visor OS support for 16-grays
I'm vexed again and again that most programs only support 4 grays on the Visor since that's all the OS supports. The hardware, however, can do more. Fireviewer, for example, takes advantage of the hardware on the Visor directly and shows 16 grays. However, it is the exception to the rule.
Is it even possible for Handspring to come up with a patch to support new OS features, even if its only this one?
Personally, I'd like to see OS3.5-level graphics support so kAWT's KVM would run in true gray-scale on my Visor.
Just my $0.02
------------------
--
Trinition ([email protected])
|