Swiz updates and documentation!
You may have heard (certainly not here!) about a little Flex framework I have been working on called Swiz. Although I have been a tiny bit quiet around here, I have been extremely actively developing and using Swiz, as well as traveling out to 360|Flex to do a session, and trying to get the word out on a few podcasts. Well, today I REALLY need to get cracking on the blogging, and luckily I have a few updates to share. First off, I just added a section to the Swiz documentation on DynamicMediators as well as updated the project setup page. Here's a quick rundown of the changes for the week.
At 360|Flex I learned that the Flex 3 SDK will automatically include custom metadata compiled into a library. So now there is no reason to add the additional compiler arguments unless you are using the Flex 2 SDK. Also, there has been a little confusion between the first swc I posted and the latest about how to get Swiz properly initialized. The correct method is to call Swiz.loadBeans( [ loaders ] ) in a function that is invoked in your main application on preinitialize. This will allow Swiz to load all of your beans before any views are added to stage and then autowire your views as they are added.
The major new addition, however, is the new DynamicMediators, which I showed at 360|Flex. Basically this function allows your controllers to respond to event dispatching by just adding an annotation to the function that you would like invoked. Check out the documentation for a full explanation. In the coming weeks I am going to put together a short series of blog posts walking you through the setup and usage of Swiz, but for now, head on over the the google code site, and if you are interested, join the user group and provide feedback to help Swiz grow!
At 360|Flex I learned that the Flex 3 SDK will automatically include custom metadata compiled into a library. So now there is no reason to add the additional compiler arguments unless you are using the Flex 2 SDK. Also, there has been a little confusion between the first swc I posted and the latest about how to get Swiz properly initialized. The correct method is to call Swiz.loadBeans( [ loaders ] ) in a function that is invoked in your main application on preinitialize. This will allow Swiz to load all of your beans before any views are added to stage and then autowire your views as they are added.
The major new addition, however, is the new DynamicMediators, which I showed at 360|Flex. Basically this function allows your controllers to respond to event dispatching by just adding an annotation to the function that you would like invoked. Check out the documentation for a full explanation. In the coming weeks I am going to put together a short series of blog posts walking you through the setup and usage of Swiz, but for now, head on over the the google code site, and if you are interested, join the user group and provide feedback to help Swiz grow!
posted by Chris Scott at 11:29 AM
4 comments
