MX components and file sizes.

[skalie]

I've been playing around on a very basic level with components, but it is becoming apparent that the load time for a site even using the most basic of them is going to be too heavy to inflict on people using a modem.

Take the FTree, from Macromedia's second set of components, for example. Although the .swf is only 36 KB, it takes a download of 89 KB, or 19 seconds on a 56 K modem, and that is in it's "virgin" state.

Quite a lot of waiting time for only the navigation.

Have these components been designed for the days when everyone has broadband?

And where does the extra 53 KB come from in the above example, the (Action) scripting?

TIA

[the sherrif]

you cant code the components level of functionallity into a smaller file. most of the file is AS. if you want smaller file sizes, youll have to get rid of most of the components global methods, and any private methods associated with them. - which would reduce functionality as a result.

the average connection speed these days is well over 128k

you could try compressing the .swf (from publish options)

increasing file sizes? that just isnt possible. maybe your getting some packet loss or your connection isnt 56k (on normal tephone wires its rarely over 50-51k)

[skalie]

Originally posted by the sherrif
increasing file sizes? that just isnt possible. maybe your getting some packet loss or your connection isnt 56k (on normal tephone wires its rarely over 50-51k)

Thanks for the reply.

What I meant though was if you drag a Ftree component onto the main stage and then view the publish preview, although the original .swf file is 36 KB, the total amount to load is 89 KB (according to the bandwidth profiler).

This is without adding any bells and whistles whatsoever.

Either the bandwidth profiler is giving a false reading, or those extra 53 KB's are something like the components' action script going around in circles.