Alain Hufkens
Yesterday Adobe decided to remove the Fx prefix from the new Flex 4 (aka Gumbo) components. The debate was whether components in the next version of Flex should all start with the letters “Fx” or use namespaces to resolve possible conflicts with legacy components like Button, Panel and ScrollBar. After playing around with the new Flex components, it felt a little strange to use for example a FxButton for the new stuff because in the end it just a button. In other language has been be solved using namespaces so why not keep it clean and use a specific namespace for one architecture and another one for the new.
The Flex SDK team has decided and is going for the multiple namespace solution. Read more about this in this topic: “Kittens saved, Fx prefix will go away“. The cool thing is that when the topic came up for debate Adobe asked the community for input in this forum post. So now that’s out of the way I can’t wait using Flex 4.
If you enjoyed this article, please consider sharing it!
[...] lateley about the pro’s and cons of Flex namespaces. I was in the pro camp as you can see in this post I made some time ago. But enough about this [...]