Alex, you were right. Including the system manager does not add any bytes in
the project...
The problematic bit that adds ~400KBs is casting the application to its ...
class:
the offending line is the following: - IT ADDS 400KBs to the release build
!!!
((event.currentTarget.parent as SystemManager).application as
Main).customPreloader = this ;
This line is in a custom preloader (used in Main (which is the Application
entry point)).
What i do not understand is why it is adding 400 KBs as Main is the default
application - everything should already be included...
Any ideas?
On Wed, May 12, 2010 at 9:46 AM, Fotis Chatzinikos <
[email protected]> wrote:
> Nope, no custom loading classes at all.
>
> That is strange then... Is there a way to see what gets included in an swf
> (appart from decompiling it)?
>
> The link report is not very helpful here...
>
> Thanks,
> Fotis
>
>
> On Tue, May 11, 2010 at 8:04 PM, Alex Harui <[email protected]> wrote:
>
>>
>>
>> SystemManager and its dependencies are always in the SWF because it is
>> their code that loads the RSLs. However, importing it should not change the
>> size of your SWF since it should already be in the SWF. Unless you’ve built
>> out a completely different loading class.
>>
>>
>>
>> On 5/11/10 2:59 AM, "fotis.chatzinikos" <[email protected]>
>> wrote:
>>
>>
>>
>>
>>
>>
>> I am building my flex 3 project using the external RSL support.
>>
>> What confuses me is that when I try to use the SystemManager (and thus
>> import it) my swf increases in size (~250KBs).
>>
>> Why is that? Is not SystemManager included in the RSL?
>> Can somebody explain?
>> Any ideas on what classes are included in the RSL?
>>
>> TIA,
>> Fotis
>>
>>
>>
>>
>>
>>
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe System, Inc.
>> http://blogs.adobe.com/aharui
>>
>>
>
>
>
>
