09-12-2012 03:23 PM
09-12-2012 03:47 PM - edited 09-12-2012 03:47 PM
Wow this is so overdue, why keep us in the dark for no reason.... but hey better late then never.
Thanks tneil!
09-13-2012 04:22 AM
Reading the devblog makes clear that they did not leave us out by accident. There was a reason. And without our feedback nothing would have been changed. I would really like to know what happened behind the scene.
But its past now ... lets try to meet the criteria.
09-14-2012 05:33 AM
Yes! It is so good news. Now let us proof that Air rocks!
10-02-2012 09:35 AM
STUPID AIR, STUPID RIM DEVs
LOOKED, EVERYTIME I UDDATED AIR SDK, I got a lot of issues AND I have to re-write code.
10-02-2012 09:48 AM
10-02-2012 09:57 AM
That is not true, I have stable app run fine on AIR SDK 1.0, then got issue with 1.1, re-write some code with 2.0, and few month ago 3.0. Now new build of 3.0 release out. I fall into another problem with SkinAssets, some class not found like ContainAlign, Spacer, also setSkin does not work, etc. We as devs very upset with RIM. Looked, iOS, Android, they always care about back compatibility.
RIM, its time for devs think about forgeting you!!!!!
10-02-2012 11:13 AM
10-02-2012 01:25 PM
Its very easy to migrate from AIR to Cascades. I post free code snippets regularly. Either way, you can still use AIR for your BB10 apps.
![]()