html - How to know when to put closing tag on nested elements -

-

i'm converting following xml html:

<rule>     <condition type="and">         <condition type="and">             <condition type="not">             </condition>         </condition>     </condition> </rule>

from structure, can infer condition can have other condition's (or not last condition).

i'm trying make same structure in html , not sure when/how/where put closing tags conditions have conditions inside of them. output i'm getting output above:

<rule>     <condition type="and">     </condition>          <condition type="and">         </condition>              <condition type="not">             </condition>  </rule>

here's xsl:

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/xsl/transform">     <xsl:output method="html" />     <xsl:template match="/">         &lt;rule&gt;         <xsl:apply-templates select=".//condition" />         &lt;/rule&gt;     </xsl:template>     <xsl:template match="condition">         <xsl:variable name="margin-left"><xsl:number value="(count(ancestor::condition) + 1) * 20" />px</xsl:variable>         <ul class="list-unstyled" style="margin:0px;margin-left:{$margin-left}">             <li>                 &lt;condition type="<xsl:value-of select="@type"/>"&gt;<br />                 &lt;/condition&gt;             </li>         </ul>     </xsl:template> </xsl:stylesheet>

the select=".//condition" has effect of flattening out hierarchy, you're selecting condition elements @ levels single list. instead, need start applying templates top-level condition:

<xsl:template match="/rule">     &lt;rule&gt;     <xsl:apply-templates select="condition" />     &lt;/rule&gt; </xsl:template>

and have condition template handle recursion applying templates own children, e.g.:

<xsl:template match="condition">     <ul>         <li>             &lt;condition type="<xsl:value-of select="@type"/>"&gt;<br />             <xsl:apply-templates select="condition"/>             &lt;/condition&gt;         </li>     </ul> </xsl:template>

(i've omitted styling part, can sort out in full stylesheet once have concept of using recursion - in fact, if use padding rather margin may not need whole counting of ancestors trick @ since each ul nests within previous one).


Comments

Post a Comment

Popular posts from this blog

python - TypeError: start must be a integer -

-
i trying draw 5 turtles, getting typeerror on line 25. here code: import turtle wn = turtle.screen() redrose = turtle.turtle() color = input("what background color be?") fillcolor_f = input("what color of rose be?") redrose.hideturtle() redrose.speed(30) redrose.penup() redrose.left(180) redrose.forward(175) redrose.right(90) redrose.forward(30) redrose.right(90) redrose.pendown() def drawrose(red): redrose.color("pink") redrose.fillcolor(fillcolor_f) redrose.fill(true) in range(red): redrose.forward(i) redrose.right(49) in range(5): drawrose(redrose) redrose.penup() redrose.forward(350) redrose.right(144) redrose.pendown() redrose.fill(false) drawrose(50) wn.bgcolor(color) i trying draw 5 roses, produces errors. doing in interactivepython.org. you recursively calling drawrose wrong parameter. on line 23 ( for in range(red): ) expect red integer...
Read more

c# - DevExpress RepositoryItemComboBox BackColor property ignored -

-
i have following code almost works properly; private void cbstatus_drawitem(object sender, listboxdrawitemeventargs e) { string item = e.item string; if (item != null) { switch (item) { case "1": e.appearance.forecolor = color.green; e.appearance.backcolor = color.green; break; case "2": e.appearance.forecolor = color.orange; e.appearance.backcolor = color.orange; break; case "3": e.appearance.forecolor = color.red; e.appearance.backcolor = color.red; break; } } } when dropdown shown, items forecolor correct, backcolor remains whatever backcolor of theme is; i.e. if i've got set dark theme, backcolor dark, cells in gridview, rather being green/orange/red. i've tried setting e.appearance.options.usebackcolor trying set e....
Read more

django - Creating multiple model instances in DRF3 -

-
1) create multiple model instances 1 api call, asked here: how create multiple model instances django rest framework? tried solution named in link, no success. i trying upload multiple files in 1 api call. result: files uploaded (only once overwrote perform_create) 1 instance created (if send 2 files, latter created instance). my code: class fileuploadserializer(serializers.modelserializer): def __init__(self, *args, **kwargs): many = kwargs.pop('many', true) super(fileuploadserializer, self).__init__(many=many, *args, **kwargs) class meta: model = fileupload read_only_fields = ('created', 'datafile', 'owner') class fileuploadviewset(viewsets.modelviewset): queryset = fileupload.objects.all() serializer_class = fileuploadserializer parser_classes = (multipartparser, formparser, ) def perform_create(self, serializer): file_list = self.request.data.getlist('file') ...
Read more