On 8/13/06, Luc Le Blanc <[EMAIL PROTECTED]> wrote:
This sounds like negligence to me.
How are you supposed to test a device-specific behavior in your app when
it pokes the device ID and doesn't get the right one?
the palmos emulator reported the correct device/company id - because
it emulated a 68k based rom image which you had to provide to test on.
with the introduction of ARM, palmsource allowed the "testing" of applications
on simulators - but, since they can never 100% represent how a device
works; they were normally given an alternative set of device/company id's.
for example; you cannot run ARM code on a simulator - so, how does
this let me test if my application runs on a Tungsten T? even with the
x86 DLL approach; it doesn't ensure that the ARM binary isn't compiled
incorrectly.
emulator = represents device accurately
simulator = is to be used as a guide, since - its even different architecture
what needs to be released; is the palmos ARM emulator - i know its
available to some members of the plugged in program; but, it allows you
to test like we used to do with POSE.
forget the simulators; you need the real hardware to truely test stuff now.
microsoft release their version of an ARM emulator - and, you can even
install programs direct to the devices and test them. no x86 binaries;
just pure ARM. these programs can be slow - but, they do accurately
represent the devices.
palmsource needs to release that ARM emulator publically. boycott the
simulators and demand the emulator.
--
// Aaron Ardiri
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
