foomonger-swizframework Updated With Swiz 1.0.0 RC1
Swiz 1.0.0 RC1 was recently released so I've updated my custom metadata processors to work with it. Head over to Google Code to check out [MediateSignal] and [Resource]. Happy coding...
foomonger's blog
Tips and Musings on Software Development, Flash, and Flex
Pages
Recent Posts
- foomonger-swizframework Updated With Swiz v1.0.0 and AS3Signals v0.8
- Lessons Learned in Agile
- foomonger-swizframework Updated With Swiz 1.0.0 RC1
- SwizLogger Helpers: SwizLoggerConfig and LoggerProcessor
- Swiz, ResourceManager, and [Resource]
Recent Comments
- Sam Ahn on foomonger-swizframework Updated With Swiz 1.0.0 RC1
- zzp on foomonger-swizframework Updated With Swiz 1.0.0 RC1
- Sam Ahn on Mocking Loader and Services
- Jason Hanson on Mocking Loader and Services
- Ian Serlin on Swiz, ResourceManager, and [Resource]
Archives
- January 2011
- September 2010
- May 2010
- March 2010
- February 2010
- January 2010
- November 2009
- October 2009
- September 2009
你为什么要新开foomonger-swizframework项目呢？
为什么不把功能提交到swizframework中去呢？
zzp
2 Dec 10 at 9:38 PM
Google translated previous comment:
Why do you want to open foomonger-swizframework item?
Why not feature in the submitted to the swizframework go?
Rephrase:
Why haven’t I submitted these custom processors to be included within Swiz?
Good question. There is an answer for each custom processor.
[Logger]
This one is so simple I don’t think it’s worth it. I could also see people wanting to use their own [Logger] to create non SwizLogger logger instances. Hmm, that might not translate well.
[MediateSignal] aka [SignalHandler] and [Resource]
These have dependencies on other frameworks (AS3Signals and Flex), and I don’t think Swiz should/wants to have those dependencies.
I really like the leanness of Swiz and hope it continues to stay that way.
Sam Ahn
2 Dec 10 at 11:27 PM