Desktop AIR 2.5 application with transparency and embedded Flash with wmode transparency error

Question

I'm working on a desktop AIR project using the 2.5 SDK (ADT) to create an application that combines html and flash content. My application is using systemChrome none and transparent true. I have an swf element in my html file that I have set to wmode transparent. Instead of the swf rendering with a transparent background and showing the desktop like the html content does, I'm seeing a black box that fills the area where the Flash element is embedded.
Can someone please assist me in removing this black square so that my flash content is rendered within the html file with a transparent background instead of a black background?
When the AIR application is set to transparent, the Flash content must have it's wmode set to either transparent or opaque. Opaque gives it a white background (the stage background color), but transparent seems to just give it a black background.
Thanks!

Answer 1

Ok fellas,
It appears that I have indeed answered my own question. So thanks... uh, me As I've now figured out, the entire AIR application is basically still a Flash based Display Object, one that can render html using webkit. That means that even though my main application is written in HTML I can still load swf files into the display list of the root applications native window using the Loader class.
I had mentioned earlier that this didn't work, but actually it did work I was just having an error. In my flash file I had a reference error because I was referencing stage.stageWidth in actionscript. This produces a typeError in the AIR runtime when I add this to the root display list. I was able to finally see this error by add the -nodebug command to my adl testing script (adl app.xml -nodebug). For whatever reason my AIR 2.5 adl would not produce air.trace calls to the cmd console without that -nodebug command, which is extremely ironic. So adding in the -nodebug command actually gave me my debug traces! Welcome to the world we live in folks... I also found out that my traces in the swf also trace out to the console when you add this command in there.
In addition, the reason I was not able to get the Loader class to work from javascript was because I was not using the correct addEventListener call. If you are familiar with Actionscript 3.0 (which luckily I am) you will recall that you have to add the event listener to the "contentLoaderInfo" object of the Loader variable you instanciate.
Here's a snippet of how I was able to do this as well as another link that is buried in the documentation that's useful:
var loader;
loader = new air.Loader();
var file = air.File.applicationDirectory.resolvePath("test.swf");
loader.contentLoaderInfo.addEventListener(air.Event.COMPLETE, swfLoaded);
loader.load( new air.URLRequest(file.url) );
function swfLoaded(evt) {
     air.trace(" SWF LOADED! Woohoo! ");
     air.trace( loader.numChildren );
     loader.width = 1000;
     loader.height = 800;
     loader.x = 0;
     loader.y = 0;
     window.nativeWindow.stage.addChild(loader);
This is a very useful article on creating nativeWindows and other things, such as creating Flash based display objects and adding them to the stage:
http://help.adobe.com/en_US/air/html/dev/WS5b3ccc516d4fbf351e63e3d118666ade46-7e0a.html
Woohoo!