11-28-2010 11:20 AM
I'm a little surprised that the Playbook team chose to create a separate namespace for the BB implementations of UI controls. It would have been simpler for app developers if Adobe and RIM had cooperated so that using a spark.components.Label or some other control) created an optimized QNX implementation under the hood. Or, if BBUI skins were created for all components so that your app could look native (I guess this only applies to spark, which isn't supported).
11-28-2010 11:57 AM - edited 11-28-2010 11:57 AM
There were two paths they could have taken. Do what you suggested in having the implementation different with the same SDK interface or have their own framework. The own framework route makes more sense since there are and will be a lot more controls that use platform specific functionality that current controls donet have. Plus if they came across an exsiting Spark control that needed new behavior, it would be more diffilcult to have Adove change their base interface then for them to just do their own.
But I do find it frustrating some times that style of the framework is different that MX and Spark in how the SDK interfacees were implemented (eg. using Vector Numbers instead of a simple Array). I feel, under the BB SDK, I am writing a lot more lines of code to do some basic stuff that the MX and Spark frameworks do for you out of the box. Maybe it is just at a earlier stage of maturity.