Comments on: Flex 4 CSS Namespaces: Annoying Migration Issues http://www.hempton.com/2009/11/flex-4-css-namespaces-annoying-migration-issues/ Thoughts and rants from a Seattle entrepreneur. Fri, 18 Jun 2010 21:03:03 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Ruben Swieringa http://www.hempton.com/2009/11/flex-4-css-namespaces-annoying-migration-issues/comment-page-1/#comment-124 Ruben Swieringa Fri, 11 Jun 2010 17:45:06 +0000 http://www.hempton.com/?p=71#comment-124 if you're frustrated with having to make a namespace for each class-package you should look into manifest files, it'll allow you to map a range of components under a certain url (that you define). ..pretty much the way Adobe does it with Flex native classes.<br><br><a href="http://www.adobe.com/livedocs/flex/201/html/wwhelp/wwhimpl/common/html/wwhelp.htm?context=LiveDocs_Book_Parts&file=compilers_123_43.html" rel="nofollow">http://www.adobe.com/livedocs/flex/201/html/wwh...</a> if you're frustrated with having to make a namespace for each class-package you should look into manifest files, it'll allow you to map a range of components under a certain url (that you define). ..pretty much the way Adobe does it with Flex native classes.

http://www.adobe.com/livedocs/flex/201/html/wwh...

]]> By: Sebastian Bernstein http://www.hempton.com/2009/11/flex-4-css-namespaces-annoying-migration-issues/comment-page-1/#comment-120 Sebastian Bernstein Sat, 06 Mar 2010 05:26:42 +0000 http://www.hempton.com/?p=71#comment-120 It might sound like a problem, in fact I also noticed that also changed the way you register CSS Styles into the CSSManager since what use to be "UserView" now is "com.mypackage.view.UserView" forcing you to rewrite a lot of code if you use the way Adobe recommended to define the default styles to a class.<br><br>Still don't be to hasty to complain, this is just a minor change compare to what it takes to go from hallo to spark on a program including the way some stuff has been changed from the core like the way text is processed.<br><br>If you've been a flash programmer since the beginning all this should not be a surprise to you.Every mayor version of flash (this is every 2 years) comes with vast changes on the programming architecture that force you to learn all over again, I still remember what it was to go from the first version of FLASH to when they make it actionscript emacs4 compliant, or when they went from FLASH to Flex.<br><br>I think they are moving in the right direction, and even I've just started my learning process of Flex 4, I've already realized that there are some mayor changes on how things has been rethinked and probably I'll have to rewrite most o what I have to take advantages of this changes, in the end of course I'll end up with a program that is a lot more up to date to programming trends :).<br><br>Still there is a point on what you are saying, as actionscript becomes more powerful and applications get more complex, Adobe should restrain itself of doing this huge changes on the way the code is written since each time the overhaul gets a lot harder. It might sound like a problem, in fact I also noticed that also changed the way you register CSS Styles into the CSSManager since what use to be “UserView” now is “com.mypackage.view.UserView” forcing you to rewrite a lot of code if you use the way Adobe recommended to define the default styles to a class.

Still don't be to hasty to complain, this is just a minor change compare to what it takes to go from hallo to spark on a program including the way some stuff has been changed from the core like the way text is processed.

If you've been a flash programmer since the beginning all this should not be a surprise to you.Every mayor version of flash (this is every 2 years) comes with vast changes on the programming architecture that force you to learn all over again, I still remember what it was to go from the first version of FLASH to when they make it actionscript emacs4 compliant, or when they went from FLASH to Flex.

I think they are moving in the right direction, and even I've just started my learning process of Flex 4, I've already realized that there are some mayor changes on how things has been rethinked and probably I'll have to rewrite most o what I have to take advantages of this changes, in the end of course I'll end up with a program that is a lot more up to date to programming trends :) .

Still there is a point on what you are saying, as actionscript becomes more powerful and applications get more complex, Adobe should restrain itself of doing this huge changes on the way the code is written since each time the overhaul gets a lot harder.

]]>