Reducing compilation time of Starling & Feathers projects


When using Starling together with Feathers I always use the source files instead of precompiled SWCs. Using the source files has a few benefits thanks to which you can:

  • Look under the hood to get an idea of how things work
  • Use the latest version from the GitHub (as the SWCs are not rebuilt after every fix)
  • Make changes to some of the APIs very quickly

None of this is possible if you’re using the precompiled SWCs. On the other hand, project compilation takes a little bit longer. Luckily, if you’re one of the many Starling/Feathers developers who use IntelliJ IDEA then there’s an easy way to achieve faster compilation times while having the ability to browse and edit the sources.

Read More…

Using AIRFacebook listener interfaces


In previous versions of the AIRFacebook ANE (v1.0.3 and older), the only way to retrieve results of various async requests was with the use of the standard Flash event model. You added your desired event to the dispatcher, created corresponding handler, made the request, removed the event from the dispatcher and played around with the event object that you received. After all, that is what AS3 devs have been doing for years, until signals happened. All in all, nothing too wrong with that; except, it creates room for errors which in turn make the development slower. You have to know what event will be dispatched before making the request and you have to remove the event from the dispatcher so that your handler doesn’t receive result from a request you make later in other scope of your app.

Read More…