you can look at it in a couple of ways .
1. If you have flex framework preloaded (framework caching for example
or some other mechahism) there is no overhead at all or at least no more
then you would in flash since only your custom classes will be loaded
2. You can compile your application to use only the components and the
parts of the framework that your app uses this will minimise your load
significantly
3. In our case explained in the article we needed the entire framework
because there are a lot of modules that are loaded later and new modules
being developed and we do not wanted them to include any framework
information
So you have plenty of choices
R.A. Williamson wrote:
> I've seen that -- but the extra bloat of the framework still affects
> my PLT measurements, even if it's preloaded. What's the combined
> weight of Flex/Gugga?
>
> On Wed, Apr 1, 2009 at 12:59 AM, Svetoslav Sotirov
> <
sotirov....@gmail.com <mailto:
sotirov....@gmail.com>> wrote:
>
>
> Please take a look at the dev net Article that Branimir quoted
> yesterday. There is a way to inject flash module in the first frame of
> the app and this way create an experience where you control when
> and how
> to load the Flex framework.
>
> R.A. Williamson wrote:
> > How are you mitigating the initial overhead the Flex framework
> itself
> > requires? That up-front 200k or so really kills my PLT numbers.
> >
> > On Tue, Mar 31, 2009 at 5:41 AM, Svetoslav Sotirov
> > <
sotirov....@gmail.com
> <mailto:
sotirov....@gmail.com>
> <mailto:
sotirov....@gmail.com