Want to discuss the use case before the demo like who creates these reports.
*MVP design pattern is useful if you have app that runs on web and device. Code is reusable *Date visualization: GTML: SAS framework to render graphs Bandwidth detection No API to detect in which network you are. Might want to use service monitoring mechanism to detect when you are in network.
*MVP design pattern is useful if you have app that runs on web and device. Code is reusable * Some one is going to talk about MVP
For skinning you can switch to device and might want to show the folder crumb trail. Flash builder: Easy to use tool for packaging device specific application with various configuration Issue with creating debug token for playbook
Show where the debug tokens are installed on the device. Some controls used in playbook are not available for development.
*Event bubbling: - If you don’t need touch interaction with a display object, consider disabling its mouse input to save on event bubbling. To do so, set its mouseChildren and mouseEnabled properties to false. *Avoid filtering: As tempting as they may be to use, they double the size required to render a display object. FXG: Flash xml graphics. * Cache: cacheAsBitmap, cacheAsSurface, cacheAsBitmapMatrix * Framerate: WindowsApplication.frameRate
*Event bubbling: - If you don’t need touch interaction with a display object, consider disabling its mouse input to save on event bubbling. To do so, set its mouseChildren and mouseEnabled properties to false. *Avoid filtering: As tempting as they may be to use, they double the size required to render a display object. FXG: Flash xml graphics. * Cache: cacheAsBitmap, cacheAsSurface, cacheAsBitmapMatrix * Auto orientation:StageOrientationEvent