On Fri, Jun 20, 2008 at 9:39 AM, Tim Hoff <[EMAIL PROTECTED]> wrote: > Binding to the model works the majority of the time. However, it can > also add a significant amount of model variables, that are used stricly > for state, that can be eliminated with view call-backs. It's clearly an > issue of preference, but I personally like what the guys at UM have done > to add a little more flexibily to the architecture.
Yes, I agree. And not only because the model gets more complex, but because those flags are, most of the time, used only for that particular view... so that data is not something that really needs to be shared with the rest of the application. I've been using Cairngorm for some time and that tends to happen a bit too much as applications grow. I've also been playing with the UM extensions. I redid my little blogging thing with it as an exercise. You can see it running from here: http://rojored.com You can check out the source code (and grab whatever you want) from here: http://rojored.com/code/rojored/ Of course comments or corrections are more than welcome! If you are already familiar with Cairngorm but don't yet want the overhead of learning the UM extensions just yet, you can do a super simplified CairngormEvent subclass which can have an callbacks property typed IResponder. If you extend from that for all your events, you'll have a super minimal UMEvent-ish base class that will be able to handle your callbacks easily. I recommend, though, that you check out the extensions in detail. Lots of cool things are packed in there. G. -- gabriel montagné láscaris comneno http://rojored.com t/506.8392.2040
