I know this thread is being expounded upon, but thought I'd address your
post directly. I would question storing all your view states in a big phat
view stack and managing that via modellocator. The idea is, at least how
I've been practicing it, is to use this viewstack that has its state
I am developing an application using the cairngorm framework. The
following is a descripton of how I have been using cairngorm according
to what I have gleemed from the documentation and from my own usage.
The framework suggests that you use ViewStacks in combination with
constants and
I have been exploring using modules.
I have never made an app big enough to warrant such nested view
stacks, but I don't see why one would want to change a container in a
view stack. Do you mean changing during development or at runtime?
So far I create various views and then create my
3 matches
Mail list logo
