If you don't need the events, and don't need the delegates, I'm just curious what led you to use Cairngorm in the first place. If you don't need/want a MVC framework, why not just build your project as a standard Flex app that calls functions directly from your views?
The whole concept of Cairngorm is that it separates the Model from the View from the Controller. One chief advantage is that, in a larger team, you can have different developers working on each without a whole lot of regard to what others are doing. Another advantage, even in a small team, is maintainability... particularly during upgrades (if a View component is versioned, you only have to concern yourself with the revisions to the Views... you know the Model and Controller are still valid) and migrations (if you want a view into your app via WAP, you can build a new interface that is ONLY a View, leveraging the existing Model and, possibly, even the Controller). But if you don't need any of this, there really is no need to load up the overhead of Cairngorm. --- In [email protected], "munkydung" <[EMAIL PROTECTED]> wrote: > > I've currently building a medium-large size application in Flex using > Cairngorm. I've already decided not to use 'delegates'. Instead, I'm > just updating the 'model' from within 'commands'. Now I'm seeing a > pattern where each 'event' I create is just a container for a data > structure to a 'command'. Also, it seems the mapping of 'events' is > one-to-one for 'commands'. > > So, my question is, why not just do away with the 'events' and have > views call 'command.execute()'? > > Someone talk me out of this... > > thanks, > Mike >
