Antique blog of a software dev company :-)
Posts tagged Adobe
Air (Flex) Mobile and Nexus 4 – debug and release issues
Mar 22nd
Problem 1:
Debug launcher claims that “Device appears to be offline. Restarting the device may fix the problem.”. Update of couple of android libraries helps…. but wait…
Problem 2:
Next, while building a release we get “SDK componentat air/android/device/Runtime.apk is out of date”. Putting the old android libraries back helps.
Not quite ideal, but let’s hope that a new Runtime.apk is on the way – one that will work both for debug and release.
copylocale and Windows 7
Dec 20th
Copylocale runs like magic and tells you that it has copied everything just fine. Great. But the files are not there. Ah, you’re running W7, an extremely secure system. Duh, you have to enable admin mode on your command prompt before you run evil stuff like copylocale.
Pain with ArrayCollection addItemAt
Jun 29th
ArrayCollection has some nifty functionality, but it isn’t always a smooth sailing.
Gotcha 1: addItemAt doesn’t work if the ArrayCollection is sorted. Well, it does make sense, but there are situations when we could take advantage of the fact that sorting doesn’t happen before a refresh() call. Anyway, something that IMHO should be mentioned in the docs rather than only in ListCollectionView source: “if we’re sorted addItemAt is meaningless, just add to the end”.
Gotcha 2: Well, say, that we insist of using our collection, and so we try to remove the sorting to be able to do a meaningfull addItemAt. We set ac.sort=null; but instead of a great success, things explode on addItemAt. Well, the internal logic of ListCollectionView requires you to do a ac.refresh() after setting sort to null; if you don’t do that, it’s internal vars are out of whack and null references creep in. IMHO ArrayCollection should be smart enough to handle removal of sort without a subsequent refresh call.
Gotcha 3: Well, we call the ac.refresh() after setting ac.sort=null but now our item order is all screwed up. Epic phail. So, let’s just give up and copy the collection instead, shall we?
1 | var ac1:ArrayCollection = new ArrayCollection(ac0.toArray()); |
Flex SDK bug: The first color in ColorPicker (black) cannot be selected
May 21st
Ha, I found a bug in the SDK! (Well, OK, I didn’t find it, one of the testers did 
. Let’s be very nice; let’s put it in Adobe’s Bug System, describe it and suggest a workaround 
.
More of Apple vs. Adobe…
May 2nd
New wave of articles has been sparked after by Jobs’ Thoughts on Flash – Ars published an IMHO bit lame comentary by a guy from Free Software Foundation; there is an interesting prophecy about the world 5 years from now by Charlie Stross… well and here are a few words from none other than my humble self:
Competition is good. HTML5 might be the uber great way of the future – but competition can only make it better. For example on Android phones, HTML5, Flash and native SDK pimp themselves to developers – and I trust the devs will pick the hottest one for their project. They will be forever comparing and throwing simple but rock solid complaints at the SDK makers – “Why SDK ‘A’ can do ‘X’ so well but you can’t?”.
I can promise that I’ll be very quick to give up on mobile Flash if it failed to prove itself against other solutions; but as well I’ll be quick to defend Flash if deserved. Interesting times lie ahead.
Apple, in the long term, you loose (again)
Apr 27th
Just in case you haven’t heard, Apple has decided to kill Adobe’s Publisher for iPhone. They waited and waited and just as Adobe was unveiling CS5 (and the public version of the publisher), they pulled the plug and changed T&C for the AppStore. They indeed did hurt Adobe (a bit), but more importantly they hurt the developers who were counting on that tool to become available. The devs won’t forget, dear Apple.
Nice article appeared on Ars Technica and here.
