DevForce Community Forum : Screen composition in cocktail http://www.ideablade.com/forum/ This is an XML content feed of; DevForce Community Forum : Community Forum : Screen composition in cocktail Thu, 30 Apr 2026 09:15:19 -700 Wed, 02 May 2012 14:45:53 -700 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 9.69 360 www.ideablade.com/forum/RSS_post_feed.asp?TID=3420 DevForce Community Forum http://www.ideablade.com/forum/forum_images/IdeaBlade_logo_tm.png http://www.ideablade.com/forum/ Screen composition in cocktail : The third way is how it's... http://www.ideablade.com/forum/forum_posts.asp?TID=3420&PID=13476#13476 Author: mgood
Subject: 3420
Posted: 02-May-2012 at 2:45pm

The third way is how it's done in StaffingResourceContactInfoViewModel. It uses Conductor<T>.Collection.AllActive. You'll still have to activate each VM once, but from that point on the conductor manages deactivation and potential reactivation automatically. You can then either bind to the Items collection and layout the 16 views in an ItemsControl, TabControl etc. or if you need to access them individually than you add properties on top of the Items collection that pulls out know VMs.
 
To reduce the constructor those 16 VMs can implement an interface by which they are exported and do an ImportMany. You can see that done in StaffingResourceDetailViewModel. It imports IEnumerable<IStaffingResourceDetailSection> and each one automatically becomes a tab. I can add new tabs without having to touch the DetailViewModel at all. Just add another VM that implements IStaffingResourceDetailSection.
]]> Wed, 02 May 2012 14:45:53 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=3420&PID=13476#13476 Screen composition in cocktail : Ok so I need a little help in... http://www.ideablade.com/forum/forum_posts.asp?TID=3420&PID=13474#13474 Author: JohnBloom
Subject: 3420
Posted: 02-May-2012 at 12:32pm

Ok so I need a little help in the screen composition area of cocktail. For our massive data entry screen we have about 16 separate sections that are their own view. What we currently do now is create a conductor for each of the views and bind a content control to the active item of the conductor. I understand that this might not be the correct way to do things but it worked. 

It appears that in the temphire app you have an individual property for the viewmodel and bind to that. That works as well but you also have to manage the activating and deactivating of each view. Also that would be a huge constructor to bring in 16 vms. If I was looking to clean up this screen should I follow your approach or is there perhaps a third way that would handle our scenario?
]]> Wed, 02 May 2012 12:32:41 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=3420&PID=13474#13474