StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POmaster stylesheet sharing in XSLT
primarykey
Id
646878
data
AcceptedAnswerId
647932
AnswerCount
3
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-03-14T22:42:25.853
FavoriteCount
0
LastActivityDate
2009-09-23T12:53:25.370
LastEditDate
2009-03-15T20:37:06.643
LastEditorUserId
64771
OwnerUserId
64771
ParentId
0
PostTypeId
1
Score
4
ViewCount
1168
LastEditorDisplayName
text
Body
i would like to create a master template in XSLT, which could be stored in a separate file. Every other Page stylesheets share it, with xsl:import. master.xslt <pre><code> <xsl:template match="Page"> <html> <head> </head> <body> <call-template name="Content"/> </body> </html> </xsl:template> <xsl:stylesheet> </code></pre> page.xslt <pre><code><xsl:stylesheet> <xsl:import href="master.xslt"/> <xsl:template match="/"> <apply-templates match="Page"/> </xsl:template> <xsl:template name="Content"> ... apply something page-specific </xsl:template> </xsl:stylesheet> </code></pre> page.xml <pre><code><Page> ... something page-specific </Page> </code></pre> Can i improve this solution? <ul> <li>i cannot start from master stylesheet, because i will need xsl:import everything. </li> <li>i dont want master.xslt contain references on each particular page.</li> </ul> Another decision (which is against the xslt spirit) maybe such: master.xslt <pre><code><xsl:template name="masterHead"> <html> <head> </head> <body> </xsl:template> <xsl:template name=masterEnd> </body> </html> </xsl:template> </xsl:stylesheet> </code></pre> page.xslt <pre><code><xsl:stylesheet> <xsl:import href="master.xslt"/> <xsl:template match="/"> <call-template name=masterHead> ... apply something page-specific <call-template name=masterEnd/> </xsl:template> </xsl:stylesheet> </code></pre> we don't need any general root <code><Page></code> element.
Tags
<xslt>
Title
master stylesheet sharing in XSLT
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USrudnev
UserOwnerUserId
1. USrudnev
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
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POmaster stylesheet sharing in XSLT
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POmaster stylesheet sharing in XSLT
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POmaster stylesheet sharing in XSLT
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.