11-03-2010 07:02 PM
11-03-2010 07:36 PM
Any AS3 libraries can be used on the PlayBook. The Flex framework is just a bunch of AS classes, even MXML classes are turned into ActionScript classes by the mxmlc compiler. As mentioned in this thread it is not optimized for mobile/tablet devices. Flex "Hero" sdk is a preview in to the Flex framework being optimized for mobile/tablet devices.
If you want your application to look like native PlayBook applications then the QNX UI is perfect as the applications on the PlayBook are written with those classes. As time goes a long you will see more support for Flex mobile ready sdk's but for right now its really up to the content you build and if it performs well enough.
As for Spark or MX, Spark with the new Flex Hero mobile theme will give you the best chance at performance.
11-04-2010 03:28 AM
Yes. Indeed, I managed to work with Spark/MX controls AND QNX controls. I created an UIComponent wrapper for the qnx controls I whished to use, and it worked.
My question is: How should we develop for tablet os ?
- Only with QNX controls.
- We can use Spark/MX controls AND QNX controls.
- We can even wait the Hero SDK to be supported.
11-04-2010 05:29 AM
The Flex Framework (and thereby all the Spark/MX components) is currently not supported. So you will have to write your app in pure AS3.
Here is to hoping that they are going to support the Flex Framework soon
This is surprising because they use mxml here :
Note that that Adobe article describes how to make their current (Flex Hero SDK and Flash Builder Burrito) Android simulator simulate a BlackBerry Playbook, the solution does NOT (appear to) run on the BlackBerry PlayBook VMWare based Simulator
11-04-2010 06:57 AM
Flash Builder Burrito uses "adl" to emulate the screen resolutions of different devices. And along with AIR's profiles you get the ability to roughly check on the desktop what your AIR applicaiton might look like and behave like. Flash Builder Burrito preview was baked before Tablet OS platform was announced so the only platform in the UI is Android. There will be more integration with Tablet OS in the future. The article just shows how to us the new device emulator UI to set it to PlayBook dimensions, which then allows for the rough emulation, using adl, on the desktop.
The article then goes on to show that you can take a Spark application and run it on the PlayBook simulator just fine, thus leveraging Flash Builder Burrito's newer Flex Hero integration features.
As for the question about mixing Spark and QNX. I would think the best/easier development approach at the current time is to do one or the other and not try and mix the two UI frameworks. That could change in the future.