Hey guys,

Few notes I took from the Yakov Fain lecture that took place last week:

When loading modules: you don’t have to load RSL in the main app, only link it as such to the module itself

Merge into Code – Yakov reminded us that in this linkage option, only classes I used will be compiled into the swf

Fonts slow the compilation – so always compile your css which embed the fonts as a separate SWF file, and load it dynamically.

Preloader as a flash content  – In his book “Enterprise flex application” he gives and example of using a flash preloader swf who looks like the initial login page in your application, and on the background he loads the rsls while the user verify his details.

Now that Flex SDK 4 was released, I thought I'd do a series of posts on the differences between Flex 3 and Flex 4 SDKs that will hopefully help migrate your Flex 3 app to Flex 4 or make the transition from SDK 3 to SDK 4 easier. I will be assuming you already know Flex 3 and will concentrate on the new in Flex 4 compared to Flex 3.

This post will serve as the index of the series, and I will be adding links to the different posts to this one as they become available, so come back from time to time to get updated.

I was asked to find a way for separating our localization resources out of the application swf, so that different locales can be loaded at runtime.
Pretty quickly I found the "Using resource modules" help subject, which explains how to create, compile and load resource modules,  which are SWF files, separated from your application SWF, that contain resources bundles for a single locale.
While trying to set up a demo application (didn't found one) using the instructions in the help files, I bumped into several issues which I will explain here in hopes that it will save you the time, and added the sample app as well.