Suggested ProjectsThe Flex team receives feature requests all the time, both official and through other means. Clearly we are not able to implement everything as part of the core Flex project, and not everything can be done by the Flex team itself. One of the benefits we hope to achieve by being open source is that the community feels encouraged to build features on their own that can then have an opportunity to be discussed and potentially integrated at a later time. This page is meant to list a small number of the top projects that we think the community would really benefit from, based on anecdotal evidence as well as observations from feature requests and bug filing and voting trends. Feel free to add your own thoughts (including whether you want to work on one of these projects) in the comments or even better in the General Discussion forum. Of course you may not be interested in working on a whole new project, but that doesn't mean you can't contribute. We are always looking for help with documentation as well as bug fixes. The List
|
|
Depedency Injection / IoC - Prana by Christophe Herreman
http://www.pranaframework.org/
Dependency Injection / IoC - Framework Indigo by Olivier Bugalotto aka Iteratif
http://code.google.com/p/indigoframework
Rails/Merb Integration / "Simplified Cairngorm" Framework: Ruboss by Peter Armstrong and Dima Berastau
http://ruboss.com/
Dependency Injection / IoC Framework: Swiz by Chris Scott
http://code.google.com/p/swizframework/
Only in part related to Flex, but i would still like to continue working on DENG for AS3:
http://deng.com.br/
These are all great. Flex-mojos looks like the way to go for Maven, I see some bug fixes that are requested that maybe folks could assist with by contributing patches. IoC definitely has multiple contenders, I wonder if folks would be interested in combining efforts.
Content Management System (CMS) library that is specifically designed to take advantage of MXML and Flex CSS. It's gotta be built so the app programmer can pick and choose which aspects of a CMS will go into the app. Also, the CMS will not be standalone. It will only be functional in the context of an application. Basically, the app programmer will be able to tell the app that it wants a CMS-controlled block in a certain place in the mxml. Then, the content will just automatically get put there, and the admin user can edit the content from its location during runtime.
ORM framework for BlazeDS with annotations like suggested here: http://coenraets.org/blog/2007/10/annotating-actionscript-classes-with-custom-metadata-simple-orm-framework-for-air/
Mxml-based Dependency Injection / IoC - Flicc
http://flicc.sourceforge.net/

For Maven2 support I suggest flex-mojos:
http://blog.flex-mojos.info/
VELO