What restrictions/workarounds are needed for third parties external swf?

The big nasty problem (and one we've dealt with a lot! ) is the fact that external SWFs simply can not be directly trusted. Ever.

This makes communicating between them and the base AIR application difficult at best.

The big nasty problem (and one we've dealt with a lot! ) is the fact that external SWFs simply can not be directly trusted. Ever.

This makes communicating between them and the base AIR application difficult at best. There is a hack around this based on loading the data of the SWF via a URLLoader and then taking the bytearray from it and pumping it into a Loader. However, I believe that hack was killed with AIR 1.5.1.

That being said, it is possible to communicate between the AIR app and the loaded SWF through what Adobe calls the sandbox bridge. However, setting up the sandbox bridge is a royal pain and any complex data (objects, even as simple as Arrays) get stripped down to generic objects on the other side of the bridge and can not be cast back to their original form. For our recent projects that needed to use the bridge we created a specialty class called AIRBridge that you use on both sides of the bridge and it facilitates setting everything up properly.

If you're interested, you can pull the current source from our Google Code project Automata-Tools.

Thx a lot Branden for the good info. This confirms what I had recently read about the air security model in the link posted in this answer: stackoverflow. Com/questions/697155/….

We are not currently doing any communication with the third party SWFs, but we will and I will definitely take a further look into that project when we get to it. Did you experience other type of issues with external content i.e. Using the stage, root and similar properties?(read recently those can introduce issues - but not sure on it) – eglasius Jun 20 '09 at 22:37 Yes, you have no access to the stage.

Any attempt to access it will result in an exception. This also means that certain components won't work in the child swf. I know comobox is one offender, and I'd suspect any of them that do a "popup" of anyone would cause problems.

Good luck and it was damn smart to ask here first - we had to discover these issues the painful way! – Branden Hall Jun 21 '09 at 4:05.

One we already addressed: Content outside of the external swf stage shows in the application, and when setting the size where it will be displayed the offstage elements are taken into account. Workaround: Add a mask on the main app so the external content is hidden. Use .content.

Width/height (full with offstage elements) and .content.loaderInfo. Width/height (original stage size) to calculate how much to scale content so the original stage matches the visible area.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.