1 person found this helpful
Hopefully I'm not missing the target.... urls written in the form you showed are not absolute, they are relative. An absolute address includes the entire path information including the http:// portion of the address, and can sometimes be more reliable to use.
When you load an swf into a web page, the web page's folder becomes the loading reference for how the swf needs to target any files it loads. If you were to have the swf in the same folder as the html page, then ou would not need to adjust any file targeting. It is only when you store the swf in a different folder on the server than where the html page is that you need to adjust the targeting of files loaded by the swf.
One way to be able to work between the two different environments (online versus the IDE) using relative urls is to include a variable in all your url targeting that you adjust depending on where the file is being played.
var imgPath = "test1/"; // change to "" when testing in the IDE, for example
var url = imgPath + "test2.png";
Thank you for your answer.
The flash movie also uses external classes / components which rely directly on absolute urls.
Here I cannot use an extra variable which is then prepended to the urls.
So the best way would be to change the baseUrl of the current movie.
With best regards
Any classes/components the swf file uses are not needed for the server. If you are loading them to the server it is unnecessary. They only matter when creating an swf. All the code/information they contain is absorbed into the swf when you publish.