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.
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. Curtis On Oct 1, 2014, at 6:32 AM, Erik de Bruin <e...@ixsoftware.nl> wrote: >> 'Best' would be to add Mustella tests for the new components. >> > > Agreed. But I think a lot of people are missing out on the excellent > components that were contributed to the project since the move to Apache. > Even at 360|Flex most people weren’t aware of the existence of these > components. > > A higher visibility, even at the cost of some reliability, will benefit > users - and therefor the project - and it might even motivate others to > create/donate more components. > > EdB > > > > -- > Ix Multimedia Software > > Jan Luykenstraat 27 > 3521 VB Utrecht > > T. 06-51952295 > I. www.ixsoftware.nl
