FlexMVCS Application Framework Released!
Posted by Luke Bayes Wed, 16 Jul 2008 01:01:00 GMT
I just wanted to get a quick announcement out there.
While Ali and I were working at Bunchball, we built out a huge application using PureMVC.
As we worked with PureMVC, we encountered some issues that didn’t quite feel right. One of the major factors that drew us to PureMVC in the first place was that Cliff designed everything to work with interfaces instead of hard-coded object references.
This proved to be a critical feature that helped support our desired modifications.
Since leaving Bunchball, Rajat Praharia (the CEO) has generously agreed to let us open-source the modifications under a new project we called, FlexMVCS.
It looks like some of the modifications we made have been integrated with later releases of PureMVC, and to be honest, we haven’t really kept up with changes in the underlying project.
As it stands, we’re not planning on putting much time into this project, but we wanted to get it out there for people that might find it useful.
Please check it out and let us know what you think!
I'd love to tell you what I think, but I think I need to see some examples before I do that.
Good riddance to the singletons in PureMVC, I couldn't understand why they were necessary, and why they weren't removed when the multicore version was made. It should have been so obvious, but instead they had the incredibly convoluted idea of multitons.
My main gripes about PureMVC as a Flex framework are:
I could go on and on about this but to be brief I'll just explain what I mean by the last point:
One major rationale behind using an application framework is to minimize the effort of the application programmer. In many ways PureMVC does this the other way around. One of the goals of the framework is to be portable across platforms, and to achieve this goal you, the application programmer, has to sacrifice some benefits of your platform. Instead of making your work easier, you are made to do work in order to make the framework programmer's job easier.
From the perspective of a Flex application programmer it is insane to use Supervising Presenter as controller-view interaction instead of leveraging the power of bindings. Same goes for throwing out event bubbling and so on.
From the description above and from the Google Code page it seems like you've solved some of the issues I have with PureMVC, but it would be interesting to see it in action.