The body of createAutoLoader() can simply be:

return function():Loader {
    var loader:Loader = new Loader();
    loader.load(new URLRequest(url), context);
    return loader;
};

One behavioral difference between this and an embedded asset is the dreaded one-frame minimum wait for the remotely loaded image, even when the image is already in the browser cache.
There are workarounds for it. Ely Greenfield has a Flex SuperImage component that gets the general idea right.
To deal with multiple loads of the same asset, you’d want to cache the BitmapData object, and associates that with the url. Further attempts to instanciate the AutoLoader would just create a new Bitmap with that BitmapData.

When you need to create a new class, make a copy of the bytearray and patch the data in the bytearray containing the string to the string you’re interested in. This clearly will require some hacking around with the SWF file format to make this work. Finally, load from the bytearray and use getDefinition to get the class object.

This is clearly way overkill for the case at hand, though. But it does illuminate thte possibility of generating classes at run-time. It’s just very, very difficult.

Too bad actionscript doesn’t have eval().

It’s maddening. Did you get any further than you describe here?

Ian

Trust me, I tried many possible approaches over a period of a few days, including what you’ve suggested.

BTW: __proto__ was there since SWF5;)

I’ve used this technique before, great way to keep classes from knowing about each other.

Feel free to contact me if anything is unclear.