> In Flash Builder (with Flex 4.13), when I start typing the name of an > experimental component (such as ColorPicker) in mxml, Flash Builder > suggests the experimental component. If I select it, it automatically > imports the experimental namespace. Might be different with FlashDevelop. I > haven't tried. >
You are right, of course. I’m concerned with discoverability more than availability. You have to know “ColorPicker” exists for your method to work. Equally, if you know that the default namespace prefix for these components is ’ns’, you can start typing that to get a list of all of them in the autocomplete dialog. If however the prefix was part of the file “header”, it would make referencing it that much easier and it would raise awareness and visibility. As for more exposure to these components, I would lean more toward keeping > with the best practice of writing Mustella tests. I could just see > neglecting to write them becoming a slippery slope. I agree that higher > visibility is important though. I could look it to writing one. I don't > really know what's involved but I could maybe give it a shot. If we wrote a > few per release, it wouldn't take long before they were all promoted. > A good primer on writing Mustella tests can be found here [1]. It’s a tough read, but taken together with the contents of the ‘mustella’ directory of the ‘flex-sdk’ repo it should get you started. Thanks, EdB 1: https://cwiki.apache.org/confluence/display/FLEX/Mustella+Overview -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
