agree. I also think this should be handled differently and not by Apache Flex.
IMHO there is no "right" (nor "wrong") way in how to architect a Flex application at all. And as you can see it's actually depending very much on your very POV and preferences. Getting consensus on this hot (religious?) topic will be pretty difficult I would imagine. Do we really need something bloated like the J2EE Blueprint Patterns? I don't think so. J2EE needed it because it was not a framework at all but just a specification so people needed advice, best practices and patterns. I don't see why we would need this for Flex. Personally, I use Swiz since 2 or 3 years now in some projects and I really like it and my team likes it as well. In other projects we do not use it because we don't have to and don't need to, I would not go as far as evangelizing Swiz or any other framework or architectural approach and saying that this ir that is the de-facto standard or a best practice. I also did use Cairngorm 2 in some projects. Heck, I even did Cairngorm consulting and training for customers that wanted to learn and use Cairngorm. Adobe clearly stated they won't offer any professional (commercial) services around Apache Flex. Surely they will do it for Adobe Flex 4.6 but there will be a void in the near future that needs to be filled of course. I think this is a *huge* opportunity for 3rd parties to provide training, consulting and services around Apache Flex for companies and developers that need it. This is where you can tell them how they could / should use Flex in a way that fits their needs. Again, I don't think that this is something Apache Flex should provide. We should focus on the framework and the tools going forward and leave enough flex-ibility for others to do something great with it. Dirk. 2012/1/13 João Fernandes <joaopedromartinsfernan...@gmail.com>: > Jude don't get me wrong but clearly I still don't believe it's an Apache > Flex matter. Apache Flex exists to drive the future of the project, not to > teach people how they should do something. Yes, if new stuff comes around, > documentation about new features should be available,eventually some specs > might be available, similar to what Adobe did with spark specs but that's > it. I clearly doubt will see at Apache Flex website, content telling people > how to build an application.
