I’ve been hearing a few “where did my components go?” questions from people working with Flash CS3 Professional. Just in case anyone is in that boat, don’t worry, they are still there!
If you set an FLA to export for ActionScript 1, or ActionScript 2, the components panel will automatically refresh with the components that you are familiar with from Flash 8 Professional. If you change the file to export for ActionScript 3.0, you will see the new components. Flash will always show you all the components that you are able to use given your export target.
In Flash CS3, the Flash team added a number of light-weight, easily skinnable components that are written in AS 3.0. However, since they are built to use the new ActionScript Virtual Machine (AVM2), they are only going to work in SWFs that are exported for Flash Player 9 or higher and for ActionScript 3.0.
For those that haven’t started working with Flash CS3 Professional yet, these components are hot! I have to admit that I have never liked components. I prefer to build things from the ground up myself and have complete design control. Also, my days of working on advertiser-related projects has left me with an obsession for small file sizes that has never let me use the AS2 components.
When I first started at Adobe and got to see behind the curtain, I was really shocked by the new components. The team had really listened to all of the objections about the components and done something about them.
Now, the components work off shared classes which means incremental growth in SWF size per additional component. The base component class is under 10K and is screaming fast. Grant Skinner showed an example of a data grid with ONE MILLION entries with text and images that scrolled smoothly, efficiently, and without spiking the processor.
Beyond the geek factor though, the components are skinnable in a way that makes sense to designers. Shifting sides of the brain for a moment, the way I edit a symbol in Flash is to double click on it, make my changes, and go back out to the parent of the instance I was editing. It allows me to see the object in the context of what I am creating. This was probably the most valuable feature among some pretty heavy hitting features in Flash 5.
In Flash CS3, the same is now true for components. If you double click on a components, something happens now! You will see all of the states and elements that make up the component as symbols laid out on the stage. They are nicely labeled in their custom layout, and all you have to do to change the styling is to double click again on the state you want to modify, make your changes and….. well, there is no more and. that’s it.
Back on the developer side though, you also have APIs to style the components at runtime if you happen to prefer things that way. You can also target all of the instances of a components, or just a single one. I’m pretty amazed by the many ways the new components keep demonstrating their flexibility.
Any word on the future of Adobe supplied data component classes for Flash CS3? Specifically the dataset, and RDBMSResolver classes? I’m sticking with Flash 8 for the time being, as I’m aware they aren’t available in the new Flash…
Grant Skinner gave a presentation on the subject that you can find here :
http://gskinner.com/talks/cs3components/
Apparently the data components were not part of the first release.. you can read for yourself.
Pingback: WebService //Flash :: АЗ2 и АЗ3 компоненты во Flash CS3 Professional
Interesting to hear that the AS3 data grid can host as many as one million entries. I’m working on some applications that involve, on the one hand, large data sets (dictionaries of up to one million+ entries), BUT they need to be self-contained. Hence, no server-side scripts to query databases or the like are allowed. I guess the data grid could be an answer. However… how do you get that many entries in there in the first place?? I’ve tried to run an XML file with one million + nodes and it just makes my system crash. Any suggestions??
Thanks,
Tine.
Hey thanks for the great article! Vik
Pingback: Unique Custom Design Resources
I have lost a LOT of time migrating to AS3. Not only do we have to create a number of missing components when using Flash CS3 with AS3, but I have to rewrite the custom components created with Flash 8 (AS2 SWCs).
Developers are honestly getting weary of Flash due to the the dramatic component changes that has to be endured with every new release. How about some stability? Then there would not be as many bugs such as this one:
Create a blank Flash File (CS3 using AS3) and drop a RadioButton control in the library. Then copy this code in the first keyframe:
/*** Begin sample code ***/
import fl.controls.RadioButton;
var myRadioButton:RadioButton;
trace(“Height Before:”+this.height);
myRadioButton = new RadioButton();
addChild(myRadioButton);
trace(“Height After:”+this.height+”, myRadioButton Height:”+myRadioButton.height);
/*** End sample code ***/
Take a look at the output:
Height Before:0
Height After:100, myRadioButton Height:22
The height of the clip is 100 pixels even though it only contains one item that is 22 pixels high! Yet another Flash nightmare.
VERY GOOD
Now we know why it’s called Flash.
Сompletely agree. Flash CS3 is the real cool. I even cant suggest what we’ll see in the next versions…
oerdepgf xsgfg
perde ve perd
net mefrudaş
http://www.stor oerde
I agree that the new cs3 components are cool, but I’m having a really hard time figuring out how to skin them beyond the visual elements, eg. changing text font and color in a List component. The components don’t seem to have any applicable public properties, and none of the Flash forums have given me any insight. Any ideas on how to go about this?
I’m plugin-version-confused. Using cs3, as 3.0 and ExternalInterface (button- and slidercomponents and communicating to and from HTML-page) it works in my browsers. Trying on other computers download plugin needs but the current version, 9.0.115.0, doesn’t do the work.
I guess the cs3-plugin on 43mb does it, but I can’t expect such a download for the visitors. Right?
Anyone have a clue
Thanks …!!!!
thanks for nice work..
Thanks for the nice read
thank u ………….
it’s Flash!!! but thx for this post!
This is not because we think that it is not useful but rather that it had tended to be over used
These handy little posts are certainly making using Flash that little bit easier…
do you if i would be able to seamlessly work between CS3 and Pro 8, or would there be problems?
thanks great stuff..
you can use that Flex Component Kit for Flash CS3
thanks alot
hello
so did you find a fix for the radio button height of 100 issue? I’ve been tearing it apart for a day now and still can’t find a fix.
Thanks dear ..
thanks…
Thanks dear ….
thanks…
thank you
thanks.
thx.
thank you
thanx.
wow
thnks
good work
Thank You
So has anyone fixed the 100 pixel high issue with Radio buttons?
I also am having an issue with the height property being incorrect. has anyone found a fix yet?