StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
352668
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2008-12-09T13:14:48.010
FavoriteCount
0
LastActivityDate
2008-12-09T13:14:48.010
LastEditDate
LastEditorUserId
0
OwnerUserId
7890
ParentId
352632
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
In general you need to use a Factory Pattern for these types of situations. Your mix of ScreenService, ScreenRepository, and Screeninfo sounds like you nailed it. <a href="http://en.wikipedia.org/wiki/Factory_pattern" rel="nofollow noreferrer">Here</a> is a basic overview of what a Factory Pattern. You can use the Wikipedia article as a starting point to see if there are any variation or aspects that you missed. I designed and maintain a CAD/CAM application that has several libraries of precanned parametric shapes where the user can type in a few dimensions and calculate the shape for cutting. Each shape has it's own screen setup. I use a similar pattern to your during the startup of my applications. I scan the directory of shape library for each assembly, pick out the factory class which has a method that retrieves a list of shapes, load it into a master list. When the user clicks on a toolbar button or picks from the list the software then uses a key to pull the right shape out of the list which exposes a IShapeScreen interface. The form that manages the shapes uses that interface to draw the correct entry screen for that shape. This method has worked for nearly a decade without any significant problems and just as important hasn't left me with a "Oh I wish I did this when I designed it" feeling. So I think you are on the right track. Note that you may not need to use a text based config file. Using attributes, some interfaces you define and the .NET reflection API you can just throw DLLs in a directory the software can scan that directory and correctly pull in the desired objects. In your case screen objects. However if you want a human to edit the configuration then a text based file is certainly called for. I am assuming that you are using the .NET API as you tagged with .NET.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODeclaring Presenters and Views
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USRS Conley
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. This table or related slice is empty.
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.