12-10-2010 05:35 AM
Hi there, don't hang me if the question seems stupid: is there any difference between building a MXML based application and using Sprite subclass?
Are all those kind of application are allowed for the Playbook offer?
Solved! Go to Solution.
12-10-2010 05:56 AM
no one gets hung around here so no worries and welcome to the forum! the difference between MXML and "using a sprite subclass" (im going to assume you mean actionscript 3) is the structure of the code.
in MXML the foundation of it looks a lot like HTML but it also incorporates actionscript 3 scripts. Your main application file will be in an .mxml format. There are some playbook specific classes you will not be able to access due to incompatibilty reasons. but there are work around if you look around the forums.
The other alternative is using just actionscript 3 code and structure. Here you dont use any MXML coding and you simply use OOP style coding to get what you want. here you will run into some missing classes such as the MX packages.
There are more differences but those are the basic ones. and according to the last webinar from yesterday, both format of coding are acceptable for the offer. hope that helps and good luck!
12-10-2010 07:45 AM
Early on, I did some tests between MXML vs. AS. File size and startup time in the simulator is about 40% larger and 2-3 seconds slower respectively. this is just having 1 button in the application to close it. Your application may vary. MXML (for me) is more productive in getting the layout correct and maintained, but since the GUI are a lot simplier than my normal AIR/Flex applications, that seem sto be less of an issue (but still would love to use MXML if the filesize issue would go away).
12-10-2010 10:15 AM
Yesterday, during the webcast, it was clearly stated that there is nothing "technical" that would prevent your app to be accepted and entitled to the free Playbook, which means that doesn't matter what resources/libraries you used to build your application, as long as it follows the terms and conditions.
12-10-2010 02:01 PM
You can use MXML with just QNX UI components and no Flex. This approach gives you a middle ground, but in the end choosing a framework or set of libraries has many factors to consider (productivity, content, modules, etc...).
Here is the forum post specificaly on using QNX components in MXML.
12-12-2010 10:58 AM
Thanks for the reply.
I now understand better the difference between those two approach and i prefere using AS3 approach as i'm coming from a iPhone/Android native app development.
I'm building basicaly a game which will require many custom graphics; i got those graphics in a PSD file.
What is the best approach to draw a game on screen and update the differents element!: PS: my game require detecting detecting user touch imput and i don't want to do complex computation of which element the user touched.
12-12-2010 11:18 AM
im not into really into the game development area but embedding graphics into your classes would probably make things easier. but again dont quote me on that because im not game developer. your best bet is probably doing a google search on adobe air games and tutorials. i've seen several online examples even some using the away3d libraries. good luck!
12-12-2010 12:16 PM
You can either load PNG files dynamically from local storage or embed them into the SWF file. Loading is fast, but not as fast as embedded images. Either case, they get set to the Image class (or Bitmap class if you need to manipulate the image in some low level way). Each image can listen for events (like mouse clicks). If you dont want to do that because of image movement, an alternative way is to place a transparent overlay over the whole sceen that will listen for events and then you can maniupate the image underneath.