Question
IMPORTANT: Dropping the Fx Prefix - dealing with XML libraries
Hi folks — we’re running into a few more roadblocks in our plans to drop the Fx prefix, that we need some fast input from the community on.
It turns out there’s a lot of poorly written XML library code out there. After doing the work to drop the prefixes from all the spark components, we’re discovering that a large number of XML libraries — both open source and 3rd party libraries used in the Flex compiler, as well as those used by other community tools that process MXML, simply cannot handle having multiple tags with the same leaf name. Silly, given that’s exactly the reason XML namespaces exist, but it’s a fact of life.
So simply dropping the prefix off of the new components doesn’t fly. But we’ve heard loud and clear from the community that adding a prefix is also a non-starter. We’ve got a proposal up on the wiki for alternate ways to avoid duplicate names that don’t require unsightly prefixes or too much extra typing.
You can read the details, and comment, here:
http://opensource.adobe.com/wiki/display/flexsdk/Updated+plan+for+dropping+the+FxPrefix
Please comment by EOD today, 4/1/2009, as we are trying to get this work wrapped up as soon as possible.
Ely.
