Simply download the Playbook SDK and simulator package, install it and use the following command line to package to the simulator substituting the arguments with your project specific values. RIM has a great Playbook simulator which works a treat. However, with Flash Develop, the device support is not so integrated. Of course, if you are using Flex Builder, then this may seem a little more obvious. So what can we use in the development stages? Use the Playbook Simulator Of course, you should always test on the actual hardware if you can. I now use the android emulators when I want to test the application actually works on specific devices before I submit to the marketplace. This page will introduce all versions of LDPlayer, including LDPlayer 3 (32bit), LDPlayer 4 (32bit), and LDPlayer 4 (64bit). To be honest, they are so slow I think they are the wrong tool for doing intermediate development testing. So we know the Android Emulators are slow. Of course, most of the time, you will be able to get away with using the ADL desktop player, but testing on a device simulator is necessary to test gestures work as you would expect for your application. At least in the development stages anyway. So if I am developing an application for an Android tablet I can probably get away with testing the app on any tablet OS that supports the Air runtime. The cool thing about developing on the Air platform is that the end result should be device independent.
0 kommentar(er)
