Wow, I just found out about this decision at the same time as the rest of the community. Our product manager, Matt Chotin just posted this to the Adobe Forums:
Subject: Kittens saved, Fx prefix will go away
A new discussion was started by Matt Chotin in
Kittens saved, Fx prefix will go away
Thanks everyone for your extended feedback. We will plan on removing the Fx prefix and implementing the multiple namespace solution. The details will need to be worked out (and specs will be posted) over the next few weeks.
Our goal is to have this all implemented by the time of our first beta which is planned for mid-May. The high-level plan (which is subject-to-change based on further spec and investigation and re-reading of all the posts plus requests for additional feedback) is:
– 3 namespaces for MXML, the MXML 2009 language namespace, the Halo namespace, the Spark namespace
– We will not turn on the option for merging namespaces as a) most customers are actually saying that they don’t mind the separation and b) this is what ends up causing all the future headaches with tooling, source portability, and future issues. We can consider the namespace merging/importing a future feature.
– CSS will need to support namespaces which means that FB will need to support CSS with namespaces. Work needs to be scoped/spec’d.
There are obviously lots of details to be worked out, and rather than getting your immediate input I’d ask that you hold off on detailed suggestions until we can get the right engineers assigned who can then start asking for feedback on specific issues. We will also probably roll this work into our normal API scrub class refactoring that often happens before a beta. So please do not expect to see instant turnaround on this change, but it will happen.
We certainly needed our team to have thick skins over the last few weeks but this also served to remind us just how passionate and great the community is. It’s nice working on a product that so many people care about!
Enjoy the weekend!
I really thought we’d closed the discussion, so, this goes to show that we do listen to the community. I’m glad to see it! Cheers to Adobe. On the other hand, I’m not looking forward to all the havoc this will cause us in testing land for the Flex SDK… but, its all for you guys 🙂 Have a great weekend!