I wonder if rather than having a whitelist of things that you pass to the run time to load, you should go the opposite way. If the thing is _not_ a <resource> then just pass it to the runtime and hope for the best? This would allow more flexibility and let people experiment with protocols that we can't predict.
On 2010-09-09, at 19:42, Henry Minsky wrote: > Change hqm-20100909-XK7 by [email protected] on 2010-09-09 17:37:47 EDT > in /Users/hqm/openlaszlo/android > for http://svn.openlaszlo.org/openlaszlo/trunk > > Summary: add support for AIR resources syntax > > New Features: > > Bugs Fixed: LPP-9362 > > Technical Reviewer: max > QA Reviewer: raju > Doc Reviewer: (pending) > > Documentation: > > Release Notes: > > Overview: > > support the "app:" syntax for embedded resources, for AIR applications > > Details: > > LzSprite.setResource check for 'app:' prefix on url, and treat it like a > dynamic > load, so that asset can be loaded by runtime from an AIR package > > Tests: > > mobile-openlaszlo/proof-of-concept/adobe-air-2.5/air-resource/airtest.lzx > > Files: > M WEB-INF/lps/lfc/kernel/swf9/LzSprite.as > > Changeset: http://svn.openlaszlo.org/openlaszlo/patches/hqm-20100909-XK7.tar >
