Wow, thanks for figuring this out!
I don't know which approach would be better. It would be better if we did
not rely on the mx.* classes if we
can avoid it, but it looks like your method of adding a new base app class
with the RSL bootstrap frame works well so maybe that is the simplest
approach to begin with.
On Sun, Nov 23, 2008 at 12:52 PM, André Bargull <[EMAIL PROTECTED]>wrote:
> Ok, that's the lesson:
> RSL is a flex-only feature and it involves certain base-classes of the
> mx.core package. So we've got two possibilities to use that feature:
> - either use the flex classes (that'd be "mx.core.FlexModuleFactory" resp.
> "mx.core.FlexApplicationBootstrap")
> - or re-implement the flex-feature to fit our needs (by loading the rsl-swf
> through "flash.display.Loader")
>
> I've attached a working example, especially pay attention the
> auto-generated file in the "generated" subdirectory
> ("SimpleMain_mx_core_FlexApplicationBootstrap-generated.as"). This shows how
> mxmlc transfers the RSL-info into the application.
>
>
>
>
> On 11/23/2008 5:19 AM, Henry Minsky wrote:
>
>> I have been unable to successfully build a flash 9 app which uses the
>> runtime shared library feature.
>>
>> I tried linking to the LFC using the instructions from the flex
>> documentation (
>> http://labs.adobe.com/wiki/index.php/Flex_3:Feature_Introductions:Flex_3_RSLs),
>> and
>> I keep getting an error that LFC classes are not found. I produced a
>> simple standalone
>> test case, attached, that has the same error.
>> When I run the app, main.swf, I do not see any network request made for
>> the runtime shared
>> library (library.swf) using
>> Firebug or using the Firefox LiveHTTPHeaders plugin.
>> If anyone can figure out what I'm doing wrong in building this app, that
>> would be a big help.
>> Thanks
>>
>>
>>
>> --
>> Henry Minsky
>> Software Architect
>> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>>
>>
>>
--
Henry Minsky
Software Architect
[EMAIL PROTECTED]
