StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
545637
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
2009-02-13T11:34:03.980
CreationDate
2009-02-13T11:34:03.980
FavoriteCount
0
LastActivityDate
2009-02-13T11:42:52.603
LastEditDate
2009-02-13T11:42:52.603
LastEditorUserId
64457
OwnerUserId
64457
ParentId
519725
PostTypeId
2
Score
8
ViewCount
0
LastEditorDisplayName
Paxic
text
Body
Although it is not uncommon to have "nested" design patterns it is not necessary in your case. Drawing on the other answers: Model  - Contains all the real data, variables, objects  - knows how to set its stored data values to the new values  - responds to orders (method calls)  - has method setPreferences(value1,value2,value3...); View  - is the IO for the application, just output and input  - it can only work on its self, on its state  - it maintains local variables and objects, eg. it has JButtons, JMenus, int counters ...  - it is knows how to inform the Presenter of State Change  - its state is visible to the Presenter, or revealed by method call  - responds to orders (method calls)  - knows how to get preferences from the user  - has method askForPrefs();  - has method getPrefState(); Presenter  - Responds to state changes  - does all the deciding, it tells the other objects what to do (not how to do it)  - knows when preferences are needed  - knows where to get new preferences and where to put them  - has method newPrefsAvailable(); <blockquote> ... to obtain further information from the user. In the case of these events, I believe it is appropriate for the Swing view to spawn a new JDialog window. </blockquote> Presenter - checks the Model, determines new preferences are required Presenter - this.myView.askForPrefs(); //tells view to ask user for pref values View.askForPrefs - pops up a JDialog box, retVals stored in the view as a state change View - this.myPresenter.newPrefsAvailable(); Presenter - responds with this.myModel.setPreferences (this.myView.getPrefState()); Model.setPreferences - changes the stored values to View.getPrefState() Presenter - checks the Model - determines preferences are good Presenter - continues on The JDialog is treated as just an extension of the View,it is a member of the View just like a JButton would be. The model has the authoritative actual preference values, and the view has local variables that represent the state of the JDialog.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POApplying the MVP pattern to JDialogs
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USPaxic
UserOwnerUserId
1. USPaxic
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POApplying the MVP pattern to JDialogs
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTBountyClose
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. CO"The JDialog is treated as just an extension of the View,it is a member of the View just like a JButton would be" - that says it all. Thank you.
 singulars
 PostPostId
 PO
 UserUserId
 USDavid Grant
2. COCheers, I can get rather verbose :)
 singulars
 PostPostId
 PO
 UserUserId
 USPaxic

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.