StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3237777
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-07-13T13:45:38.357
FavoriteCount
0
LastActivityDate
2010-07-13T13:55:01.323
LastEditDate
2010-07-13T13:55:01.323
LastEditorUserId
215600
OwnerUserId
215600
ParentId
3237208
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Your Model will deal with your zip file in this case, e.g. methods like <code>Print()</code>, <code>Extract()</code> etc. and events like <code>PrintCompleted</code> and <code>ExtractCompleted</code> etc. Your IView will expose methods and events that abstract your interaction with the UI behind an interface. So perhaps some methods such as <code>DisplayFolderContents()</code> and events like <code>FileSelected()</code> etc. Your presenter will hook up to the Model and IView events and control which methods are called on each etc. The Form that you have a TabControl on is just an implemenation of the IView interface. You could have a different view just by injecting an implementation of IView into the Presenter, including a Mock IView for testing. Values can be passed around the MVP pattern through the EventArgs you use. <pre><code>/// <summary> /// The event args for a selected file. /// </summary> public class FileSelectedEventArgs : EventArgs { public string FileName { get; private set; } public FileSelectedEventArgs(string fileName) { this.FileName = fileName; } } </code></pre> When the user selects a file, the <code>FileSelected</code> event is raised in your View, with the FileName available in the <code>FileSelectedEventArgs</code>. The Presenter listens for this event, and calls a method on the Model - maybe <code>ExtractFile(string fileName)</code>, passing in the fileName from the FileSelectedEventArgs from the View. The Presenter then listens to the <code>ExtractCompleted</code> event to be fired from the Model (which also has whatever custom eventargs you want) and calls the appropriate method on your View, passing in the parameters from the Model. The method in the View can do whatever you want in terms of displaying the data in a TabControl or in another way. This is just one way of doing it anyway. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POImplementing MVC/MVP Design for TabControl ..design question
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USPeter Kelly
UserOwnerUserId
1. USPeter Kelly
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
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.