> The logo change is a marketing thing and has a lot to do with corporate image
> etc. etc. But the test itself is being revamped for OS 4.0 and the focus will
> change a bit. Rather than try and pick out Palm Quality based on standard UI
> use, we will concentrate on system level compatibility with an eye looking
> forward to the eventual move to the ARM chip with OS 5.0. This is not to say
> that use of standard UI is not a good thing (that is an entirely different
> issue), but rather that judging that was very subjective and system level
> compatibility plays a strong role as we move on.
small question..
if the developer checks the existance of a particular CPU / hardware
before doing specific tweaking options (grayscale, blitting routines)
how does this validate the testing cycle.
for example, in all my games, if i detect a 328/EZ/VZ chip running
on a non-color display, i allow tweaking of the grayscale registers.
another example, is when i use custom assembler written graphics
routines for 160x160 displays specifically for m68k based CPU's.
if the CPU isn't known and the display is not 160x160, API routines
are used instead..
whats the limitations on this?
// az
[EMAIL PROTECTED]
http://www.ardiri.com/ <--- free games!
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
