next »

[Kekskiller]

Well, I found a way to cope with actionscript3 and wrote a little music player. I can load graphics files and such, but loading files using an URLLoader doesn't work cause of flash's policy system. What I'm working on is an audioplayer that reads it's playlist from an external XML file in the same folder as the swf file. I'm loading the sound files specified in the playlist using the Sound class and will then, while playing compute the Spectrum of it using computeSpectrum. So all three things (urrloader, sound, spectrum) require policy thing I just can't adjust to the right way. Loading sounds works, the rest not.

I'm using the mxmlc command line compiler on linux.

What I tried so far:
- using Security.allowDomain("*");
- making a crossdomain.xml in the folder I'm loading from (on dropbox)
- using "-use-network=true/false" in all variants

Without commandline options, it works locally on the filesystem but not uploaded to dropbox. Sandbox type varies between localWithFilesystem and localWithNetwork.

So yeah, I'm out of ideas. Though I definitely need to get this working til sunday

[Draknek]

If you're loading files from a website, crossdomain.xml must be in the top-level directory for that website, e.g. http://www.dropbox.com/crossdomain.xml

You can't do that on Dropbox, so if you want to load files from a website you'll need a different host (possibly you'll need to get your own hosting).

[Kekskiller]

Ah, ok. Thanks for that. And what is if I want to load it from the files domain? Guess I just need to specify the filename as URL. Shouldnt it work if I use "-use-network=false" and just upload it to Dropbox and thus it's the file's domain with crossdomain.xml-less access?

[agj]

I don't know what -use-network is, but if the SWF and the file you're loading are in the same domain there's no problem.

[Kekskiller]

-use-network is a command line option for mxmlc, the Flex command line compiler (I feel geeky saying this). It all worked well this way, using -use-network I mean. I somehow screwed up the policy stuff by mixing all kinds of policy settings here and the result was some pretty weird allow/disallow stuff. Problem solved.