StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POTemplating regex versus DOM nodes; Modifying attributes?
primarykey
Id
4538432
data
AcceptedAnswerId
4538657
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-12-27T11:45:59.170
FavoriteCount
0
LastActivityDate
2015-02-10T22:41:49.867
LastEditDate
2015-02-10T22:41:49.867
LastEditorUserId
3204551
OwnerUserId
409279
ParentId
0
PostTypeId
1
Score
0
ViewCount
90
LastEditorDisplayName
text
Body
<p>I've asked a few questions as of recent on this topic, and whether answered or not, I've been learning a fair amount about the tech involved. In any case;</p> <p>I've been reworking a templating engine I had created previously, moving the parsing engine from being regular expression driven, to node (XML) driven. For comparison's sake here are the two:</p> <p><strong>Regex driven:</strong></p> <pre><code><body>  <div class="myClass"> <h1>{{ var:myHeading format:trim[200] }}</h1> </div>  </body> </code></pre> <p><strong>Node driven:</strong></p> <pre><code><body> <zuq:region name="myRegion"> <div class="myClass"> <h1> <zuq:data name="myHeading"> <zuq:format type="trim"> <zuq:param name="length" value="200" /> </zuq:format> </zuq:data> </h1> </div> </zuq:region> </body> </code></pre> <p>Now while much more verbose, I figure the node driven approach here is preferred, giving much more flexibility for situations like formatting, where multiple format nodes can be inserted and processed in order of appearance.</p> <p>Anyways, my <strong>problem</strong> lies in <strong>attributes</strong>. With the regex driven approach, if I want to have a template generated value in an attribute, it's as simple as:</p> <pre><code><a href="page.php?param={{ var:myParam }}">Link</a> </code></pre> <p>I'm trying to figure out how to incorporate a clean implementation of generating attribute values, while keeping the documents well formed. Something to consider is again, the formatting options, among other possible elements that the parser would read as modifiers to data.</p> <p>Any ideas?</p>
Tags
<regex><xml><dom>
Title
Templating regex versus DOM nodes; Modifying attributes?
singulars
PostAcceptedAnswerId
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDan Lugg
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.