Good choice starting with MultiCore.
I am working on a somewhat complex AIR app at the moment and have just made some key changes to the StateMachine utility, which will result in a 1.1 verson being released shortly. As a result, I would suggest not even venturing there yet (or at least not don't beat your head against it much).
The StopWatch demo actually still works as written, but its not representative of real world use.
Since you're working with AIR, one piece of junk you almost certainly want in your PureMVC box is the DesktopCitizen util.
When you open your app, you want it to be a good desktop citizen, and behave like most native apps; namely to restore its size and position info as well as whether it was maximized.
In AIR, you have to do this yourself. Its not hard, but its a pain to write for every app.
Check out the RSS Headlines and CodePeek AIR demos to see how its done.
An AIR app comes up in the same location. At the same location and default (or configured) size every time. Instead, if you resize it, or move it it should come up as you left it. Further, if you move and resize, then maximize and close, when you bring it up, it should appear maximized when you bring it up, and then when you click restore, it should go back to the size and position you moved it to before you maximized. We subconciously expect this behavior and when an app doesn't behave it shows. Anybody ever use the old school WS-FTP client that acted like an out of box AIR app? So annoying
DesktopCitizem will give you all this with only 3 or 4 lines of code.
-=Cliff>