StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5368594
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-03-20T12:52:48.803
FavoriteCount
0
LastActivityDate
2011-03-20T12:52:48.803
LastEditDate
LastEditorUserId
0
OwnerUserId
270591
ParentId
5367622
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
For a Tab-based interface <a href="http://msdn.microsoft.com/en-us/magazine/dd419663.aspx" rel="nofollow">this classical article about MVVM pattern in WPF</a> might be very useful. (It also offers a downloadable sample application.) The basic idea to connect each tab with a UserControl is as follows (only a rough sketch, details are in the article): The MainWindow View has a ContentControl ... <pre><code><ContentControl Content="{Binding Path=Workspaces}" ContentTemplate="{StaticResource WorkspacesTemplate}" /> </code></pre> ... which binds to a collection of "Workspaces" in the MainWindowViewModel: <pre><code>public ObservableCollection<WorkspaceViewModel> Workspaces { get; private set; } </code></pre> This <code>WorkspaceViewModel</code> serves as a base class for all ViewModels you want to display as a tab. The <code>WorkspacesTemplate</code> is a DataTemplate which binds a TabControl to the collection of WorkspaceViewModels: <pre><code><DataTemplate x:Key="WorkspacesTemplate"> <TabControl IsSynchronizedWithCurrentItem="True" ItemsSource="{Binding}" /> </TabControl> </DataTemplate> </code></pre> And for every specific Tab you have a UserControl with a ViewModel which derives from WorkspaceViewModel ... <pre><code>public class MySpecialViewModel : WorkspaceViewModel </code></pre> ... and which is related to the UserControl by a DataTemplate: <pre><code><DataTemplate DataType="{x:Type vm:MySpecialViewModel}" > <v:MySpecialUserControl /> </DataTemplate> </code></pre> Now, if you want to open a tab you would have a Command in the MainWindowViewModel which creates the ViewModel belonging to that tab and add it to the Workspaces collection of the MainWindowViewModel: <pre><code>void CreateMySpecialViewModel() { MySpecialViewModel workspace = new MySpecialViewModel(); Workspaces.Add(workspace); } </code></pre> The rest is done by the WPF binding engine. The TabControl recognizes automatically that this special workspace item in the collection is of type <code>MySpecialViewModel</code> and selects the right View/UserControl through the DataTemplate we have defined to connect ViewModel and View and displays it in a new Tab.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PONested Data Context with Unity
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USSlauma
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.