08-12-2011 07:34 AM
I developed a PlayBook app using the classes from the qnx packages qnx.ui.display.Image, qnx.ui.core.UIComponent, qnx.ui.buttons.Button and a few others.
Now I am planning to port my app to android, iPhone and desktop, for this I believe I need to revert the qnx packages to the standard flash packages.
I hope it will be enough to just change the imports, I'd appreciate if somebody could confirm this.
Now the question is if the classes are equivalent then why would we use the qnx packages at all instead of the flash packages, it only forces us to modify the code, I understand there would be specific classes for the PlayBook-specific things (bevel gestures for example) but why UIComponent, Buttons etc??
Is there some optimization? What do we gain using qnx instead of standard flash?
08-12-2011 07:37 AM
08-12-2011 11:22 AM
08-12-2011 03:07 PM - edited 08-12-2011 03:10 PM
90% of QNX components work fine on Android and iOS, they are simply pure AS3 components. If it compiles on desktop, it will compile on any AIR platform.
You just need to watch our for the ones with System hooks, ie PPSChannel dependnancies (but these will blow up when instanciated on desktop, so it's obvious)
Oh, and Peter is right, changing imports will never work, unless by some miracle the API is exactly the same as some other class.