Style modules are another possibility. On 4/15/16, 12:05 PM, "[email protected] on behalf of OmPrakash Muppirala" <[email protected] on behalf of [email protected]> wrote:
>Do you know what assets would be used during compile time? Or will it be >determined at runtime. > >If you know it in compile time, you can just reference them in code like a >normal class and the compiler will include it in the swf/mobile app. > > >On Fri, Apr 15, 2016 at 11:21 AM, chris_d_k <[email protected]> wrote: > >> Hi, >> >> I have a flex mobile app. >> >> I want to compile it to different apps which should use a lot of >>different >> embedded fxg-Files. >> When I put all the fxg files the app would be really huge and full of >> assets >> it does not need... >> >> What is the best way to achive this? Is there an article on this topic I >> haven't found? >> >> I have read the flex team created an FXG-Runtume-Parser but haven't >>found >> it... with this I think I could store the fxg-Files in locales... >> >> Or would it be better to create an asset-swc for every app with >>different >> assets and some methods to acces them (f.e. >> getTYPEAImages():SpriteVisualElement, >>getTYPEBImages():SpriteVisualElement, >> ...)? >> >> >> >> >> >> -- >> View this message in context: >> >>http://apache-flex-users.2333346.n4.nabble.com/Build-Flex-Mobile-Apps-wit >>h-different-Assets-tp12471.html >> Sent from the Apache Flex Users mailing list archive at Nabble.com. >>
