StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PODynamic UI Creation using DSL in .NET
primarykey
Id
7768765
data
AcceptedAnswerId
7769215
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-10-14T14:01:04.037
FavoriteCount
0
LastActivityDate
2011-10-14T14:34:12.690
LastEditDate
2011-10-14T14:33:40.120
LastEditorUserId
15541
OwnerUserId
834910
ParentId
0
PostTypeId
1
Score
0
ViewCount
409
LastEditorDisplayName
text
Body
I'm developing a WPF application for a client. The application needs to prompt the user at the start of a production run to populate a number of fields. The data the user is prompted to enter is dependent on the type of product associated with the production run. So for example, Product A may require the user to enter an expiry number, lot number while Product B may require the user to enter a manufacturing date only. I will need to dynamically create the UI and display the name of the field, the input control (text box, list box, checkbox etc) . The system needs to be flexible and a mechanism to allow the user "create" the dynamic UI layout needs to be put in place. I'm looking at various options, such as: <ol> <li>XML to declare the ui structure the user would like. The app would then process the XML and create apprropriate ui controls for the various XML elements</li> <li>A custom DSL which would allow the user to enter something like: "create textbox for field LOT NUMBER" Like the xml approach, the app will save the above and assign it to a Product and save it in the DB. During the start of the production run the app dynamically creates the UI.</li> </ol> Initially the user will edit these files by hand and assign them to a product. Eventually we plan to have a graphical front end for designing the UI with drag and drop support. I don't have much experience with DSLs. Just wondering if the above is a suitable application for DSLs or if I should take a completely different approach.
Tags
<.net><wpf><dsl>
Title
Dynamic UI Creation using DSL in .NET
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USleppie
UserOwnerUserId
1. USLance
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
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.