here's a concrete example of, ' the loaded content problem '
I received a U.S.patent on this Flash 4 based 'invention', it's an interface navigation tool system: http://www.google.com/search?hl=en&q=patent+matthews+data+objects+6943811+&btnG=Search The complete Flash 4 code is published in the docs, but a working example has been on the net since the patent was granted: http://2goto.com/ Top buttons+scroll bars trigger to visible on roll over (zoom bar = window/left). It actually runs on the earliest FlashLite player. The 'zoomer' is completely object oriented. Any internal window can 'loadMovie' any .swf on the net/local that is not relying on a root.call to function. I've had it still operating with 50 independent feeds.swf from 30 different host URL's. The patent explains how the 3k zoomer.swf invention is designed to display a huge number of dataObjects.swf or other data like .jpg's and HTML pages for example. When the cursor is outside of a window, we switch off = unload the content (load a blank.swf into the parent), and reload it when the cursor returns. This allows the interface to appear to hold vast quantities of information and interactive animations, tools.swf, etc. I rebuilt the zoomer code in AS3, it works fine. The newest player's domain permissions may make loading independent Flash.swf's more complex than loading text.txt docs and .jpg's - we'll see. Now, with AIR the browser can be a child object in an .swf - Flash wraps around the billions of HTML based web pages - even those containing content.swf ! We could be developing a fly through universe of videos, interactive video phones, live camera feeds, the whole GoogleEarth tile map system, galleries seas of HTML.pages etc. Inside Flash! ...Except, there is no way for us to unload any of that independently hosted work.swf from the Flash based zoomer interface - even when we unload/replace the parent 'internalWindow.swf' containing the other guys.swf. bummer, Dave Matthews http://www.2GoTo.com p.s. The zoomer could not be invented without Flash, because bitmaps can't scale like vector graphics. The bandwidth/hardware differences between what Flash's vector engines have been able to do for years compared to Micro$oft's WPF/sliverlite are substantial! Flash is exponentially more effecient. thanks folks, good thread... :) Dave _________________________________________________________________ Going green? See the top 12 foods to eat organic. http://green.msn.com/galleries/photos/photos.aspx?gid=164&ocid=T003MSN51N1653A_______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
