Our swf is a template that can be loaded into an edit mode, where clicking on UILoader triggers a JS function that pops up a HTML image selector. The selected image is then loaded into the UILoader. Then, when the swf is loaded for presentation, the image source paths are pulled from a DB and the correct images are loaded. This enables the end-user to quickly change the image in the swf from any image in our extensive DB.
It would be easy to replace UILoader with LoaderMax for this, were it not that we need UILoader because the component needs to be placed/manipulated in the Flash editor GUI, as our designer cannot code.
Furthermore, putting the UILoader in a MC will send the wrong instance name to the JS, which will cause the swf to try and load the image into MC.source instead of MC.UILoader.source. Of course, it would be possible to rewrite the code to do just that, except that when designing in the GUI this will make things quite a hassle.
The point is, currently we have a system that enables our designer to create templates with minimal knowledge of AS3 or coding. I want to keep it that way.
Could you elaborate on extending the UILoader class?