ResonanceDesign

I keep finding myself with some trouble whenever I work on a standalone application and finally test it as a mProjector render. There still seem to be some quirks with it’s difference to how your app will run on or as a Flash Player app. As I am using many external files (images,xml, flv, etc.) this makes large parts of my app become ‘buggy’.

Latest example: I need swfs to be loaded from a folder and some flvs, too. I am using mFile.listFiles().
After developing the app and testing it inside flash, everything is working fine. My video recorder records, and plays the video files afterwards and the swf interstitials play.

I render the swf out to mProjector and BAM, no swf is loaded. Now generally there seems to be a difference between Flash Player and mProjector, which is that mProjector likes absolute file paths.
Knowing this from a previous app, I developed a MProjectorPath class, which checks the path and makes it an absolute one. I also have to consider both Mac and PC as I develop for both systems. On top of that, I like to sometimes use backwards relative paths (../). Combining these with everything else is a bit of a heckle, so I spend some time today to write a class taking care of this.

- it checks if the path is a web path or not (http:, etc.)

- it adjusts non-web paths to the OS it’s running on (changin / to \, to cover windows and osx)

- it turns relative into absolute paths

- it takes into account ../../, etc. paths when creating absolute paths

- it doesn’t turn absolute into application relative paths (to come when I really need it)

- I thought I share it

You can download the class (pretty static, AS2, zipped) here.

To use:

 
 
import mProjClasses.MProjectorPath;
 
var tPath:String = MProjectorPath.relativeToMPath(myRelativeFolder);

Have fun and let me know in case I missed something. I tested this one on mac laptop and tower and a windows xp machine and they all worked fine.