Passing Arguments to an Air Application

[Ricardinho]

Ive been doing some work on Passing Arguments to an Air Application on Install and everything works fine if the a user downloading the package opens it directly from the browser Air installer instead of saving the package. If the user saves the package directly to their machine the arguments cant pass.

I basically need a way to have Air Packages unique to individual downloads whether Saved or Opened from the browser??

Is there some way i could automate the packaging process server side so i can insert arguments at a creation level?

Or is there a way i could inject arguments into a pre-package white label version of the app?(this will propbably cause massive security issues)

Any idea would be great. Thanks

[kukoc]

you can use Shared Objects, simply create one while user browse the webpage, or click "download" button and then you propably can use it in your air app.

i thought it will be imposible becouse of security reasons but i found this link (air browser of shared objects):
http://blog.coursevector.com/minerva

so i think this is a solution for you, pretty simple to implement.
chears!

[Ricardinho]

Ok, so what you're suggesting is that when a user browses or clicks to download the Air app they also get a LSO placed onto their machine. After the user installs the air app it then seeks the LSO to get any vars necessary to style/brand the white label app?