Matthew,
I feel your pain. Setting up an optimized application is tricky. but is well worth the time and effort. http://www.onflex.org/ted/2007/06/flex-3-thursday-dramatically-smaller.php http://soenkerohde.com/2008/04/using-the-flash-player-cache-for-the-flex-fra mework/ A couple of other items to consider when trying to cut down on application size is the option of using the ActionScript project type. If you have a whole bunch of code that is strictly ActionScript (no UI involved) using that project type can help shave some bits off as well. If you run into any road blocks contact me off list and I'd be happy to help work up a config with optimized targets. Rick Winscot From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Harui Sent: Friday, June 13, 2008 4:46 PM To: [email protected] Subject: RE: [flexcoders] RSL hell I think you use: -compiler.external-library-path framework.swc to prevent classes in that swc from being linked into your RSL _____ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of matthew.painter Sent: Friday, June 13, 2008 1:36 PM To: [email protected] Subject: [flexcoders] RSL hell Hi guys, I'm trying to use RSLs for my application. Now some of the RSLs depend upon the flex framework - you know, things like Canvas. So the RSL can use the framework RSL, same as the main app right? Wrong! Seemingly... This means that my RSLs are mostly >500k, while the main app is < 100k. Surely there is a way to stop downloading about 300-400k of the same code for each RSL? I'm worried that the whole advantage of RSLs, i.e. caching, is gonna be blown away by the initial download time (which is looking like being 5-10x as big for an app). Help! (Please :o) Matt
