Some ideas
0 views
Skip to first unread message
Christophe Herreman
Oct 16, 2009, 3:42:54 AM10/16/09
to springactionscript-dev, as3-commons-developers
Hi,
just wanted to share some ideas I have for Spring AS and AS3Commons. These ideas are mainly about moving code and providing more reusable libraries. I'm looking for feedback on these things, so please fire away.
- In general for AS3Commons, I think we should also provide common libraries for Flex and AIR. I know the name AS3Commons implies that the libraries are all AS3 compatible, but there are certain libraries that can be useful to Flex and AIR developers. To prevent having to manage yet another project (Flex Commons for instance), I would suggest to add Flex and AIR libraries to the project and provide a clear overview of what platforms the libraries can be used on.
- FlexUnitTestCase: remove this class from Spring AS and provide the assertions as a set of functions instead. That way, you don't need to extend anything special and you can extend ASMockTestCase for instance if you are using ASMock and still use the custom assertions.
- MVCS: move this into a separate extension of Spring AS, like the Cairngorm and PureMVC extension. Not everyone will be interested in using these, so I think this is a good move.
- AppSettings: move this out of Spring AS into a AS3Commons project, AS3Commons-Config for instance. There is no real need for this in Spring AS since you have the container to configure things.
- Properties: this can be used for other projects as well, so I would suggest a AS3Commons-Properties project.
- SOSTarget: this is really just a flex logging target. Move this to AS3Commons together with some other logging targets.
- Security: separate Spring AS extension?
- org.springextensions.actionscript: I would like to shorten this to org.springactionscript.
- Mate: there is a Jira issue about Mate extensions. I can see value in this by providing classes that integrate the IoC container in Mate applications. Does anyone on this list use Mate? If so, can you comment on this and/or can you help to provide valuable extensions?
In conclusion, all these changes have to do with cleaning the Spring AS codebase and providing the essense of the core of the framework: the IoC container. By doing this, I also think that we show to the community that we are not focussing on the IoC container alone and want to promote maximum flexibility and choice in the development.
Thoughts?
regards,
Christophe
--
Christophe Herreman
http://www.herrodius.com
http://www.springactionscript.org
http://www.as3commons.org
just wanted to share some ideas I have for Spring AS and AS3Commons. These ideas are mainly about moving code and providing more reusable libraries. I'm looking for feedback on these things, so please fire away.
- In general for AS3Commons, I think we should also provide common libraries for Flex and AIR. I know the name AS3Commons implies that the libraries are all AS3 compatible, but there are certain libraries that can be useful to Flex and AIR developers. To prevent having to manage yet another project (Flex Commons for instance), I would suggest to add Flex and AIR libraries to the project and provide a clear overview of what platforms the libraries can be used on.
- FlexUnitTestCase: remove this class from Spring AS and provide the assertions as a set of functions instead. That way, you don't need to extend anything special and you can extend ASMockTestCase for instance if you are using ASMock and still use the custom assertions.
- MVCS: move this into a separate extension of Spring AS, like the Cairngorm and PureMVC extension. Not everyone will be interested in using these, so I think this is a good move.
- AppSettings: move this out of Spring AS into a AS3Commons project, AS3Commons-Config for instance. There is no real need for this in Spring AS since you have the container to configure things.
- Properties: this can be used for other projects as well, so I would suggest a AS3Commons-Properties project.
- SOSTarget: this is really just a flex logging target. Move this to AS3Commons together with some other logging targets.
- Security: separate Spring AS extension?
- org.springextensions.actionscript: I would like to shorten this to org.springactionscript.
- Mate: there is a Jira issue about Mate extensions. I can see value in this by providing classes that integrate the IoC container in Mate applications. Does anyone on this list use Mate? If so, can you comment on this and/or can you help to provide valuable extensions?
In conclusion, all these changes have to do with cleaning the Spring AS codebase and providing the essense of the core of the framework: the IoC container. By doing this, I also think that we show to the community that we are not focussing on the IoC container alone and want to promote maximum flexibility and choice in the development.
Thoughts?
regards,
Christophe
--
Christophe Herreman
http://www.herrodius.com
http://www.springactionscript.org
http://www.as3commons.org
Reply all
Reply to author
Forward
0 new messages