I have found that if you have one good SWC build in your library it will make all other custom components appear. So as a workaround I always start a new project by placing a good SWC in the projects “libs” folder. Oddly enough I have only been able to build one good SWC from 3 full days straight of building and testing, uninstalling, re-installing, using multiple workstations. After all that testing I gave up and just use the good SWC build workaround.

I also noticed that all tutorials out there in books and the internet never mention that you can access the custom components from the Component Library in Flex. They always declare custom components programmatically through custom name-spaces. That makes me wonder if this is a widespread problem…

I’m experiencing the exact same behavior as you. I can’t figure out what’s wrong for the life of me. I’ve reinstalled Flex Builder 3, Flash CS3, and the Flash Component Kit, both on mac and PC. I’ve followed every tutorial I could find to the letter. And still, Flex doesn’t seem to “see” the components in the SWC I added. Code hinting don’t show the compoenents, and if I try to instantiate them anyway I just a compilation error.

The really frustrating thing is that maybe 1 time out of 20 or so, it actually does work. Then, when I go back into Flash to make some edits to my component and republish the SWC, Flex goes back to its normal behavior of not recognizing it.

This is seriously the only issue preventing us from launching our Flex based website and its making me bang my head against the wall.

Anyone have any suggestions?

I have to say that the FCK acronym has led to some very amusing and memorable email subject lines over the past year. :)

Peter

Good catch! The MXP files were removed from the Flex SDK and are now available as a separate download. For more information, see http://blogs.adobe.com/pdehaan/2008/03/installing_the_flex_skin_desig.html

I’ll update these instructions and point to the new URL, thanks.

Peter

I’ve downloaded the Flex 3 SDK (flex_sdk_3.0.0.866), however I don’t seem to have a folder ‘flash-integration’ under frameworks. Am I missing something? Do I need to build something?

Wiebe

Command made the following changes to the FLA:
Turned on Permit Debugging
Turned on Export SWC
Set frame rate to 24
Imported FlexComponentBase component to library
Symbol “BallComponent” can be used as a Flex component.
Select File > Publish to create the SWC file for use in Flex.

This appears to be correct but after adding the SWC to the flex library, my flex application does not seem to “see” the new component. I’ve managed to pull in components that others have made with Flash AS3 and the component kit so I don’t think I’m doing anything wrong on the flex side.

I noticed that in Flash, FlexComponentBase does not show up in my library after converting my symbol to a flex component. Additionally, nothing happens when I drag FlexComponentBase into my library. It just doesn’t show up. When I go to the properties dialog for my exported component and try to validate mx.flash.UIMovieClip, I get the following message:

A definition for the base class could not be found in the classpath. Please enter the name of a class that is defined in the classpath, or enter the default base class ‘flash.display.MovieClip’.

I suspected there was something wrong with my installation of Flash CS3 or the Component Kit so I just uninstalled and reinstalled Flash CS3, Flex Builder, and the component kit with the same results.

I’ve now seen the same behavior with Flash CS3 9.0.2, Flex Builder 3 (tried both beta 2 and beta 3), and component kit 1.1.2.

Has anyone seen this behavior before?

Thanks in advance,
Jake

I haven’t gotten to the examples in detail yet. You can see one other related entry here, http://blog.flexexamples.com/tag/flex-component-kit/. In fact, I’ll try and tag each skinning/styling entry with “flex-component-kit”, so it should show up in the same listing.

Peter