Flash components
- Started
- Last post
- 11 Responses
- brozilla
can anyone tell me how effecient the flash components are in mx 04 - in terms of file size?
I've heard that the components in earlier versions (mx, 5) use more code than neccesary, thereby increasing file size. Good example is the tree component or scroll bar
anyone know anything about this or am i just getting bad info?
- imakedesign0
its very marginal, you will be able to code more efficient but its not worth the extra effort.
- a-train0
The components are also locked. So you cant edit them in any way.
Sucks that macromedia did that.
- brozilla0
huh, interesting. I know some of the components are huge, like the node tree component. but I would never attempt to create that myself.
came across this on moock's blog about skinning components:
http://moock.org/asdg/technotes/…
havent tried it but seems like a good one.
- contra0
File size is way bigger on the new ones, if you have MX2004 it's worth downloading the old Flash MX component set from the Macromedia website.
- brozilla0
you can use the mx set in 2004?
guess so, didnt know that.
- imakedesign0
nice link.
- contra0
Find em here... http://www.macromedia.com/cfusio…
I think the 2004 set are ok if you're using a few in one movie, they share a lot of common elements so that can help with file size.
If you just need to use one I find the old set a better option.
- brozilla0
thanks contra
- contra0
No problem, just doing my job, or something like that.
- lucyGeneric0
The 2004 component set are marginally bigger, but reuse a lot of assets across different components, so in the long run if you are using a bunch they are much smaller.
Personally I h8 them all :) but yer, coding them would suck . .
- jkosoy0
Its beating a dead horse, but here's a good comparison for you:
MediaDisplay component: 50kb
Custom FLV player: 2kbOf course the custom one requires coding it all. So it really depends on your expertise.