Just tried this thursday. I used Flash Builder instead of FlashDevelop, but the problem which kept me banging my head against stuff, was that you need playerglobal.swc and the flex sdk. Well that's what's advertised, but it didn't work for me.

On the Starling site I read that you need to copy over the Air SDK over the Flex SDK and you already have the right playerglobal.swc. This didn't work for me either. The Stage3D and other classes weren't available. In the end I copied the playerglobal.swc over the one in the combined sdk and finally it worked. No idea why, but I'm using Stage3D via Starling.

Now Pazil, isn't it that you need to set the wmode to direct to really do anything with the Stage3D object? I haven't tried a standalone ActionScript test yet, but a Flex one works just fine with Starling.

Also on that wmode thing. Starling detects which version of wmode is running and displays an error message if it's not direct. This may be something to look into (it's opensource), as probably not all portals will have the ability to set wmode to anything non-standard. You could show a nice splash screen to tell the user this isn't the HD, Turbo or Turbo Alhpa 3 version. And more importantly, to let the portal now that it's users could be enjoying that HD version. You may also think about a fallback way of rendering, like blitting. However creating two views for your game does sound like an awfull lot of extra work on nonfunctionality.