> AOP is as well something many of us would want to have available in Flex. > AOP and metadata allows you to decouple code, add/remove functionality > easily across all your application, and create behaviours that can be > configured to modify the existing code at runtime...this and much more can > be done with AOP. Swiz framework get a valid and usable AOP implementation > for a framework, but it had the problem that was relying on some flash > player debugger, so it was not ready for production. >
Hi Carlos, Swiz was actually using as3commons-bytecode under the hood to generate its proxy classes, I'm not aware of any dependency on the debugger player. The only disadvantage as3commons-bytecode had was, in order to generate the proxy classes, it had to first parse the loaded SWF file. In debug mode this was indeed pretty slow, in release mode it was acceptable, but I did recommend people to split their code into modules, so that the AOP functionality didn't have to parse a huge SWF file just to generate 5 proxies. So, AOP @runtime was quite limited in its possibilities at that time. Mind you, the only reason why I had to parse the existing SWF was because the Flash player doesn't provide a complete set of reflection data for classes and methods. Had the reflection data been complete, the parsing wouldn't have been necessary and runtime proxy generation would have been an enormous amount faster. (Definitely usable for production) cheers, Roland
