Your choices are framework caching or modules. The framework is big but remember that it only gets downloaded once and then everyone saves in their subsequent downloads. Those very same people already downloaded a rather large Flash Player 9 which is required to utilize this feature. It isn't too much different than forcing a player upgrade. Like a player upgrade, the problem is that someone does have to take that first "hit" and so the user's experience of their very first Flex app that uses the framework cache is not as nice especially on slow networks.
I've been thinking about sneaky ways to get folks to download the framework cache like a hidden SWF on an HTML page if your site is such that you don't go immediately to the Flex app. Maybe some banner ads on Yahoo and Google or other places where users have significant "dwell" time. I've also wanted to prototype a template for a slide-show to use as a download progress bar so folks have something interesting to read while the framework is downloaded. If a significant number of my users had slow networks (I can name at least 3 people still on dialup), and I really felt there was no way to hide the initial framework download, I might go with modules. ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of danielvlopes Sent: Monday, October 15, 2007 12:14 PM To: [email protected] Subject: [flexcoders] Re: Flex is becoming unviable Thanks for video, now the file had 300kb and not 400kb, i still thinking this is a big file... I thinking adobe need take a look in ways to optimize the size of swfs... I really love flex and what can be done with him, but the size of swfs is your worst problem. Some one know other way to optimize swfs without framework caching? --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "danielvlopes" <[EMAIL PROTECTED]> wrote: > > The terminology is framework caching and this generate a huge file > with 500kb and all this giant file must be load before your swf. > > --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "Brendan Meutzner" <bmeutzner@> > wrote: > > > > I can't remember the exact terminology for it, but one of the goals > > for Flex generated swfs involves caching the common framework files on > > client machines, to avoid repeated download, thus cutting the swf size > > drastically. I'm sure Ales or Matt can speak more to this feature. > > > > Brendan > > > > > > On 10/15/07, Douglas Knudsen <douglasknudsen@> wrote: > > > ugh take a look at the release notes for FB3 Beta 2 and be sure > you are > > > looking at the released version of your SWFs, not the debug > versions that > > > are generated by default only now. > > > > > > DK > > > > > > On 10/15/07, danielvlopes <danielvlopes@> wrote: > > > > > > > > Hello, i create a big project in flex using modules, RSLs and > etc... > > > > This project is real client, and he accept test flex in you website. > > > > Everything works fine (ignoring the 500kb framework file it is > > > > necessary for users to access the site.) > > > > > > > > Now i thinking use flex in small projects like simple websites, > in old > > > > versions of flex, like 3beta 1 or flex 2 swf files are smaller, like > > > > 200kb or 130kb (not really small but acceptable). But now, with > beta 2 > > > > simple files came to 400kb. > > > > > > > > I becoming thinking i waste my time learning flex and waste the > money > > > > of my client testing flex in your app, I am already thinking about > > > > redo the whole project in ruby on rails and ajax. > > > > > > > > If adobe and flex team does not begin to worry about the size of > swfs > > > > believe deeply that the flex will not last for a long time .... And > > > > certainly I will have wasted time and money. > > > > > > > > :( > > > > > > > > This is the code i use for test size of swf: > > > > > > > > <?xml version="1.0" encoding="utf-8"?> > > > > <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml <http://www.adobe.com/2006/mxml> " > > > > layout="absolute"> > > > > <mx:DataGrid/> > > > > <mx:TileList/> > > > > <mx:TextInput/> > > > > <mx:TextArea/> > > > > <mx:Form/> > > > > <mx:FormItem/> > > > > <mx:Button/> > > > > <mx:ViewStack/> > > > > <mx:Image/> > > > > </mx:Application> > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Douglas Knudsen > > > http://www.cubicleman.com <http://www.cubicleman.com> > > > this is my signature, like it? > > > > > > > > > -- > > Brendan Meutzner > > http://www.meutzner.com/blog/ <http://www.meutzner.com/blog/> > > >
