Cart
[Home] [By Thread] [By Date] [Recent Entries]
And in fact checking your post again I do see where you bring this out...
I saw this
<snip/>
I posted a minor annoyance about
still having to do some redundant coding for SGML attribute minimazation
brought into XML:
#set ($isChecked = $page.getBoolean("isChecked"))
#if ($isChecked)
<input ... checked="checked"/>
#else
<input .../>
#end
</snip>
which at the end of a long dev-day triggered a response focused on
something you obviously didnt want. I wonder, do they have a bit
recycling facility over on your side of the internet or are you stuck
with this for the long term? ;)
Enjoy your XSLT infested evening...
On Mon, 28 Mar 2005 21:03:07 -0800, Robert Koberg <rob@k...> wrote:
> M. David Peterson wrote:
> > Hi Robert...
> >
>
> Hi M.,
>
> > There are lots of different ways you can hack your XSLT to conform
> > more to your desired format but probably the easiest is simply:
> >
> > <input>
> > <xsl:if test="boolean(@checked)">
> > <xsl:attribute name="checked">checked</xsl:attribute>
> > </xsl:if>
> > </input>
>
> Yea, I know how to do it in XSL. That was not the question. I distinctly
> said I wanted to avoid XSL as a runtime templating language. I am using
> XSL to produce (pre-generate) the runtime template language pages that
> are scalable and performant in a high volume environment.
>
> >>*I was wondering if there are other runtime templating languages out
> >>there that I am missing.* I am not including XSLT for runtime processing
> >>because of its need to parse the XML source for each transformation.
> >>
>
> best,
> -Rob
>
--
<M:D/>
:: M. David Peterson ::
XML & XML Transformations, C#, .NET, and Functional Languages Specialist
|
