StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8438519
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-12-08T22:20:32.293
FavoriteCount
0
LastActivityDate
2011-12-09T13:15:04.910
LastEditDate
2011-12-09T13:15:04.910
LastEditorUserId
304832
OwnerUserId
304832
ParentId
8346437
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
This may only be a partial answer to your question, if I understand it correctly. Regarding your example with <code><input type="text" class="date" /></code>, we experienced a similar issue with our partial form views that use jQuery unobtrusive validation. When loading them in the browser, we had to call <code>$.validator.unobtrusive.parse('a form selector');</code> in order to get the validation rules to apply during the next form submission. If your goal is to avoid repeated code, you could make your js actions unobtrusive, using a pattern like in the jq unobtrusive validation lib. So you would end up with HTML that looks more like this: <pre><code><input type="text" class="date" data-datepicker="true" /> </code></pre> You can then put the initialization logic in an unobtrusive parse method. <pre><code>parse: function(selector) { $(selector).find(':input[data-datepicker=true]').each(function() { $(this).datepicker(); } }; </code></pre> } This solves your problem of having one place to refactor the code. You can make it start up automatically when the page first loads, and when you load new content via ajax, you can apply the rule to all matching elements by just calling <code>myAppNamespace.unobtrusive.parse('selector for the partial view content');</code> Update Take a look at the jquery.validate.unobtrusive.js file in your scripts folder. It really is pretty smart, and if you're not actually extending another jquery plugin (like validate), your code would end up a lot slimmer. If you're looking for full separation of HTML and script, using the HTML5 unobtrusive data- attributes is a good solution imo.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow do you structure your web applications to make AJAX and DHTML easier?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USdanludwig
UserOwnerUserId
1. USdanludwig
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow do you structure your web applications to make AJAX and DHTML easier?
 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
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.