that's 566k of code... the code is mostly the networking layer, and facebook interface controllers.
The 3 mb of assets load with the preloader and are broken into 2 modules so we can push art changes w/o pushing a whole new client. The preloader is 33% of the main loading screen - what happens is you don't see the transition between preloader and application because I designed it that way, so it looks like a single process. Basically I am already late loading the assets, but it is a requirement that the app be ready for interaction the moment the "startup" is done. unfortunately, most of the assets are required. for instance at least 1.5 to 2 mb is consumed by the game icons which the user must see instantly, and the game order is dynamic so we can't separate them into multiple pages to lower the load. Some minor optimizations can be made, and believe me, every few weeks I'm shaving a few K here or there. But not enough to add hundreds of K in statically linked libs. when i build (in debug) with static linking the size is 2,749,998 bytes vs 1,262,589 bytes in release there is a similar proportion: 1,225,769 bytes vs 609,402 bytes. (with Ant builds these numbers are slightly smaller, which is where i get the 566K for our upcoming release). basically the main file contains all the networking etc... this is because the game must be "instant-on" users often claim gifts and enter the game in a flow which leads them directly to a popup or a slot, which means that the moment load is done, the app must be in gear ready to go. is it possible to combine the framework rsls into a single file, and load it instead of the "standard" framework rsl's? So instead of loading 5 different rsls, I load a single optimized file that has only the classes needed for the app and its modules? The standard rsls come to 1.41MB and the difference in release is 0.58 MB... obviously I'm not using the majority of the flex code base... can I strip this down somehow? > From: aha...@adobe.com > To: dev@flex.apache.org > Date: Tue, 3 Dec 2013 10:20:07 -0800 > Subject: Re: SharedLibrary not works with SDK 4.11 > > Hi David, > > So you are saying that there is 566K in non-Flex code and assets to > generate the first screen (after the preloader)? How much of that is > assets and how much is code? And what Flex classes are used in that first > screen? Usually, folks take a second after seeing the first screen before > they act on it, and you can often do a bunch of downloading and > initializing in that time. If you move everything not required for the > first screen to a late-loaded module, you might find that the total > framework load goes down and static linking becomes possible. That > wouldn't be true for some app that has a DataGrid on the first screen, but > I don't think I'm seeing heavyweight components on your first screen. > > -Alex > > On 12/3/13 6:41 AM, "David Coleman" <david_coleman_...@hotmail.com> wrote: > > >http://apps.facebook.com/houseoffun/?fb_source=bookmark_apps&ref=bookmarks > >&count=18&fb_bmpos=3_18 > > > > > > > > > > > >the main file (for the upcoming version) is 566k, currently it is > >slightly over 600K, the assets are ~3 mb and i have implemented most > >popups as external modules, to ensure that they load from cdn only one > >time per session. > > > > > > > > > > > >The main application is a spark application. I use only simple objects, > > Group, List etc... nothing uber fancy. Most of the heavy lifting is > >done with AS3 for speed. > > > > > > > > > > > >We have a very large number of users. I can't statically link the libs > >because ppl expect the blinding fast load that I have achieved. 566K > >loads in the blink of an eye on even mediocre systems/connections. > > > > > > > > > > > >Personally I would prefer to statically link the framework because RSL's > > are yet another hit the browser has to make, but we need the users to > >get into the game and play as fast as possible. I have maintained the > >fastest load in our category on facebook for > >nearly a year now. :) I intend/need to keep it that way. > > > > > > > > > > > >so your short answer is "a very big, yet very, very SMALL and optimized > >facebook app" which is exactly why i have to use them :) > > > > > > > > > > > >Any way around this limitation would open the door for me to promote and > > fast-track the adoption of Apache Flex. I need small and I need fast. > > The rest is academic. Once I have the tools, I'll make it happen, and > >we will migrate to Apache Flex. Our target > >Flash Player version is 10.3 for maximum penetration. > > > > > > > > > > > >If there is any glimmer of hope to accomplish this... tell me, and let > >me know how I can help. > > > >> From: aha...@adobe.com > >> To: dev@flex.apache.org > >> Date: Mon, 2 Dec 2013 11:22:26 -0800 > >> Subject: Re: SharedLibrary not works with SDK 4.11 > >> > >> > >> > >> On 12/2/13 10:13 AM, "David Coleman" <david_coleman_...@hotmail.com> > >>wrote: > >> > >> >Having not tried this solution myself, this is pure speculation... but > >> >couldn't local storage store this? set domain to be "*" and retrieve > >>it > >> >from the public svn repo. if not present the RSL manager can load it > >>up > >> >and in this way we can sign it with our own Cert and validate that cert > >> >independent of Adobe? Would this be workable? > >> I think you'd hit local storage limits. > >> > >> >RSL's are the only reason that I hesitate to migrate our Facebook app > >>to > >> >apache. it will kill our CDN. > >> > > >> Just curious: Have you actually measured the difference without RSLs? > >>How > >> big a Facebook app is this? > >> > >> -Alex > >> > > >
