Re: [flexcoders] Question about Best Practices for Applications with many views using Cairngorm
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 managed by the modellocator to manage the MAIN view state, and I'm not talking State with a capital S here. eg, login and main or something like login, module1, module2, etc. Each of these top level views represent the major view sections in your app. Each of these may have its own view stacks with children having even more view stacks, however you need set it up. These main views would manage the state of each child stack, not the modellocator. DK On Sun, Aug 31, 2008 at 2:19 PM, j301c [EMAIL PROTECTED] wrote: 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 variables that hold the selectedIndex of the viewstack, which are then bound to the ViewStack itself. When an application gets very large, with many views, nested views and the need for hybrid views that require complex combinations of viewstack indexes this becomes very hard to maintain and also to make neccesary changes. For instance, if a container changes its location in a viewstack, it is very dependant on the variables stored in other files which becomes a tedious process to change. Also, the framework doesn't handle very well when a view needs to be instantiated in different ways when it is presented to the user. If this is wrong please correct me, because I feel like there must be a better way. If anyone knows a better way to deal with many views (whether using cairngorm or some other solution) please let me know what that is. Thanks. -- Douglas Knudsen http://www.cubicleman.com this is my signature, like it?
[flexcoders] Question about Best Practices for Applications with many views using Cairngorm
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 variables that hold the selectedIndex of the viewstack, which are then bound to the ViewStack itself. When an application gets very large, with many views, nested views and the need for hybrid views that require complex combinations of viewstack indexes this becomes very hard to maintain and also to make neccesary changes. For instance, if a container changes its location in a viewstack, it is very dependant on the variables stored in other files which becomes a tedious process to change. Also, the framework doesn't handle very well when a view needs to be instantiated in different ways when it is presented to the user. If this is wrong please correct me, because I feel like there must be a better way. If anyone knows a better way to deal with many views (whether using cairngorm or some other solution) please let me know what that is. Thanks.
Re: [flexcoders] Question about Best Practices for Applications with many views using Cairngorm
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 own components that may host other 'views'. I haven't tried to make nested view stacks - mostly cause that sounds scary. On Aug 31, 2008, at 2:19 PM, j301c wrote: If this is wrong please correct me, because I feel like there must be a better way. If anyone knows a better way to deal with many views (whether using cairngorm or some other solution) please let me know what that is. Thanks.
