You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Jim <op...@gmail.com> on 2008/04/11 20:31:10 UTC
Commenting templates
Is there a way to do server-side commenting, ala <%-- --> in JSPs? i.e.
to comment sections that you (temporarily) don't wish to be dynamically
processed server-side?
Adding <!-- --> only precludes client-side processing, of course, and if
I try to surround a template section (which contains Tapestry
components) with $remove$ tags, I get: "Tag __ on line __ is a dynamic
component, and may not appear inside an ignored block." Is there
another way? I've been resorting to pasting into a separate file.
Thanks,
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Commenting templates
Posted by Jim <op...@gmail.com>.
Somehow I tuned out your CDATA discussion, sorry.
Jim wrote:
> What about:
> <t:comment><!-- <t:put something here ... --></t:comment> ?
>
> Haven't touched T5 yet, but this is working for me in T4:
>
> <div jwcid="@If" condition="ognl:false">
> <!-- COMMENT: blah blah
> <span jwcid="@Insert" value=
> -->
> </div>
>
> This has the bonus of making (most of) the section syntax-highlighted.
>
> Jim
>
> Josh Canfield wrote:
>> Neither approach really solves the problem all the way. They both
>> require that the commented out section is valid code.
>>
>> <t:comment>
>> <t:put something here...
>> </t:comment>
>>
>> Won't parse.
>>
>> It would be convenient to be able to mark a component as containing
>> CDATA so that the template parser would leave it alone.
>>
>> for instance, if the above were equivalent to:
>>
>> <t:comment><![CDATA[
>> <t:put something here...
>> ]]></t:comment>
>>
>> which does compile.
>>
>> Especially cool if you could grab the body of the cdata element as a
>> string and do something with it.
>>
>> <t:xml.transform xml="responseXml">
>> <xsl:stylesheet version="1.0"
>> xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
>> <xsl:template match="/catalog/cd">
>> <tr>
>> <td><xsl:value-of select="title"/></td>
>> <td><xsl:value-of select="artist"/></td>
>> </tr>
>> </xsl:template>
>> </xsl:stylesheet>
>> </t:xml.transform>
>>
>> Josh
>>
>> On Fri, Apr 11, 2008 at 12:11 PM, Howard Lewis Ship
>> <hl...@gmail.com> wrote:
>>
>>> You can "simulate" a comment directive as a component:
>>>
>>>
>>> public class Comment
>>> {
>>> boolean setupRender() { return false; }
>>> }
>>>
>>>
>>> This is a no-op component, it skips directly from the SetupRender
>>> phase to the CleanupRender phase, rendering nothing. This is even
>>> less work than <t:if test="false">.
>>>
>>>
>>> On Fri, Apr 11, 2008 at 12:03 PM, nicholas Krul
>>> <ni...@gmail.com> wrote:
>>>
>>>> Good to know that it works, but I would think thats a little
>>>> dangerous...
>>>>
>>>> If its not commented, I always assume its live code. There should
>>>> be a way
>>>> to comment properly.
>>>>
>>>> I can do it in the jsps I stare at all day long... I'd think it
>>>> reasonable
>>>> T5 does real comments.
>>>>
>>>> *I haven't tested any of this, nor have I needed to put in server
>>>> side
>>>> comments... I find they tend to contain old code that may be
>>>> needed again
>>>> (or 'uncomment this for...')
>>>>
>>>> --just a thought.
>>>>
>>>> --nK
>>>> nicholas Krul
>>>>
>>>>
>>>>
>>>> On Fri, Apr 11, 2008 at 7:57 PM, Jim <op...@gmail.com> wrote:
>>>>
>>>> > That's perfect, thanks Josh.
>>>> >
>>>> > Josh Canfield wrote:
>>>> >
>>>> > > How about just doing whatever the equivalent to <t:if
>>>> test="false"> is
>>>> > > in T4?
>>>> > >
>>>> > > On Fri, Apr 11, 2008 at 11:31 AM, Jim <op...@gmail.com> wrote:
>>>> > >
>>>> > >
>>>> > > > Is there a way to do server-side commenting, ala <%-- --> in
>>>> JSPs?
>>>> > > > i.e. to
>>>> > > > comment sections that you (temporarily) don't wish to be
>>>> dynamically
>>>> > > > processed server-side?
>>>> > > >
>>>> > > > Adding <!-- --> only precludes client-side processing, of
>>>> course, and
>>>> > > > if I
>>>> > > > try to surround a template section (which contains Tapestry
>>>> > > > components) with
>>>> > > > $remove$ tags, I get: "Tag __ on line __ is a dynamic
>>>> component, and
>>>> > > > may not
>>>> > > > appear inside an ignored block." Is there another way?
>>>> I've been
>>>> > > > resorting
>>>> > > > to pasting into a separate file.
>>>> > > >
>>>> > > > Thanks,
>>>> > > > Jim
>>>> > > >
>>>> > > >
>>>> ---------------------------------------------------------------------
>>>> > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>> > > > For additional commands, e-mail: users-help@tapestry.apache.org
>>>> > > >
>>>> > > >
>>>> > > >
>>>> > > >
>>>> > >
>>>> > >
>>>> > >
>>>> > >
>>>> > >
>>>> >
>>>> >
>>>> >
>>>> ---------------------------------------------------------------------
>>>> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>> > For additional commands, e-mail: users-help@tapestry.apache.org
>>>> >
>>>> >
>>>>
>>>>
>>>
>>> --
>>> Howard M. Lewis Ship
>>>
>>> Creator Apache Tapestry and Apache HiveMind
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>>
>>>
>>
>>
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Commenting templates
Posted by Jim <op...@gmail.com>.
What about:
<t:comment><!-- <t:put something here ... --></t:comment> ?
Haven't touched T5 yet, but this is working for me in T4:
<div jwcid="@If" condition="ognl:false">
<!-- COMMENT: blah blah
<span jwcid="@Insert" value=
-->
</div>
This has the bonus of making (most of) the section syntax-highlighted.
Jim
Josh Canfield wrote:
> Neither approach really solves the problem all the way. They both
> require that the commented out section is valid code.
>
> <t:comment>
> <t:put something here...
> </t:comment>
>
> Won't parse.
>
> It would be convenient to be able to mark a component as containing
> CDATA so that the template parser would leave it alone.
>
> for instance, if the above were equivalent to:
>
> <t:comment><![CDATA[
> <t:put something here...
> ]]></t:comment>
>
> which does compile.
>
> Especially cool if you could grab the body of the cdata element as a
> string and do something with it.
>
> <t:xml.transform xml="responseXml">
> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
> <xsl:template match="/catalog/cd">
> <tr>
> <td><xsl:value-of select="title"/></td>
> <td><xsl:value-of select="artist"/></td>
> </tr>
> </xsl:template>
> </xsl:stylesheet>
> </t:xml.transform>
>
> Josh
>
> On Fri, Apr 11, 2008 at 12:11 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
>
>> You can "simulate" a comment directive as a component:
>>
>>
>> public class Comment
>> {
>> boolean setupRender() { return false; }
>> }
>>
>>
>> This is a no-op component, it skips directly from the SetupRender
>> phase to the CleanupRender phase, rendering nothing. This is even
>> less work than <t:if test="false">.
>>
>>
>> On Fri, Apr 11, 2008 at 12:03 PM, nicholas Krul <ni...@gmail.com> wrote:
>>
>>> Good to know that it works, but I would think thats a little dangerous...
>>>
>>> If its not commented, I always assume its live code. There should be a way
>>> to comment properly.
>>>
>>> I can do it in the jsps I stare at all day long... I'd think it reasonable
>>> T5 does real comments.
>>>
>>> *I haven't tested any of this, nor have I needed to put in server side
>>> comments... I find they tend to contain old code that may be needed again
>>> (or 'uncomment this for...')
>>>
>>> --just a thought.
>>>
>>> --nK
>>> nicholas Krul
>>>
>>>
>>>
>>> On Fri, Apr 11, 2008 at 7:57 PM, Jim <op...@gmail.com> wrote:
>>>
>>> > That's perfect, thanks Josh.
>>> >
>>> > Josh Canfield wrote:
>>> >
>>> > > How about just doing whatever the equivalent to <t:if test="false"> is
>>> > > in T4?
>>> > >
>>> > > On Fri, Apr 11, 2008 at 11:31 AM, Jim <op...@gmail.com> wrote:
>>> > >
>>> > >
>>> > > > Is there a way to do server-side commenting, ala <%-- --> in JSPs?
>>> > > > i.e. to
>>> > > > comment sections that you (temporarily) don't wish to be dynamically
>>> > > > processed server-side?
>>> > > >
>>> > > > Adding <!-- --> only precludes client-side processing, of course, and
>>> > > > if I
>>> > > > try to surround a template section (which contains Tapestry
>>> > > > components) with
>>> > > > $remove$ tags, I get: "Tag __ on line __ is a dynamic component, and
>>> > > > may not
>>> > > > appear inside an ignored block." Is there another way? I've been
>>> > > > resorting
>>> > > > to pasting into a separate file.
>>> > > >
>>> > > > Thanks,
>>> > > > Jim
>>> > > >
>>> > > > ---------------------------------------------------------------------
>>> > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> > > > For additional commands, e-mail: users-help@tapestry.apache.org
>>> > > >
>>> > > >
>>> > > >
>>> > > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> >
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> > For additional commands, e-mail: users-help@tapestry.apache.org
>>> >
>>> >
>>>
>>>
>>
>> --
>> Howard M. Lewis Ship
>>
>> Creator Apache Tapestry and Apache HiveMind
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Commenting templates
Posted by Josh Canfield <jo...@thedailytube.com>.
Neither approach really solves the problem all the way. They both
require that the commented out section is valid code.
<t:comment>
<t:put something here...
</t:comment>
Won't parse.
It would be convenient to be able to mark a component as containing
CDATA so that the template parser would leave it alone.
for instance, if the above were equivalent to:
<t:comment><![CDATA[
<t:put something here...
]]></t:comment>
which does compile.
Especially cool if you could grab the body of the cdata element as a
string and do something with it.
<t:xml.transform xml="responseXml">
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/catalog/cd">
<tr>
<td><xsl:value-of select="title"/></td>
<td><xsl:value-of select="artist"/></td>
</tr>
</xsl:template>
</xsl:stylesheet>
</t:xml.transform>
Josh
On Fri, Apr 11, 2008 at 12:11 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
> You can "simulate" a comment directive as a component:
>
>
> public class Comment
> {
> boolean setupRender() { return false; }
> }
>
>
> This is a no-op component, it skips directly from the SetupRender
> phase to the CleanupRender phase, rendering nothing. This is even
> less work than <t:if test="false">.
>
>
> On Fri, Apr 11, 2008 at 12:03 PM, nicholas Krul <ni...@gmail.com> wrote:
> > Good to know that it works, but I would think thats a little dangerous...
> >
> > If its not commented, I always assume its live code. There should be a way
> > to comment properly.
> >
> > I can do it in the jsps I stare at all day long... I'd think it reasonable
> > T5 does real comments.
> >
> > *I haven't tested any of this, nor have I needed to put in server side
> > comments... I find they tend to contain old code that may be needed again
> > (or 'uncomment this for...')
> >
> > --just a thought.
> >
> > --nK
> > nicholas Krul
> >
> >
> >
> > On Fri, Apr 11, 2008 at 7:57 PM, Jim <op...@gmail.com> wrote:
> >
> > > That's perfect, thanks Josh.
> > >
> > > Josh Canfield wrote:
> > >
> > > > How about just doing whatever the equivalent to <t:if test="false"> is
> > > > in T4?
> > > >
> > > > On Fri, Apr 11, 2008 at 11:31 AM, Jim <op...@gmail.com> wrote:
> > > >
> > > >
> > > > > Is there a way to do server-side commenting, ala <%-- --> in JSPs?
> > > > > i.e. to
> > > > > comment sections that you (temporarily) don't wish to be dynamically
> > > > > processed server-side?
> > > > >
> > > > > Adding <!-- --> only precludes client-side processing, of course, and
> > > > > if I
> > > > > try to surround a template section (which contains Tapestry
> > > > > components) with
> > > > > $remove$ tags, I get: "Tag __ on line __ is a dynamic component, and
> > > > > may not
> > > > > appear inside an ignored block." Is there another way? I've been
> > > > > resorting
> > > > > to pasting into a separate file.
> > > > >
> > > > > Thanks,
> > > > > Jim
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
--
TheDailyTube.com. Sign up and get the best new videos on the internet
delivered fresh to your inbox.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Commenting templates
Posted by Jim <op...@gmail.com>.
Would it be possible and within Tapestry's vision to give users the
ability to annotate actual <!-- --> tags to designate them as
server-side? In the spirit of being able to hand a Tapestry template to
a web designer using Dreamweaver, the syntax-highlighting would be
value-added.
Otherwise, there'd at least be value-added, in my opinion, in including
that no-op Comment component as standard, so that a potential
Spindle-like project could have its editor productively handle those
sections, as a JSP editor handles <%-- --> sections. Plus, I think
users should be encouraged to document the dynamic behavior of their
templates -- requiring any hoops at all is going to be enough of an
excuse for too many people not to bother.
Thanks,
Jim
Howard Lewis Ship wrote:
> You can "simulate" a comment directive as a component:
>
>
> public class Comment
> {
> boolean setupRender() { return false; }
> }
>
>
> This is a no-op component, it skips directly from the SetupRender
> phase to the CleanupRender phase, rendering nothing. This is even
> less work than <t:if test="false">.
>
> On Fri, Apr 11, 2008 at 12:03 PM, nicholas Krul <ni...@gmail.com> wrote:
>
>> Good to know that it works, but I would think thats a little dangerous...
>>
>> If its not commented, I always assume its live code. There should be a way
>> to comment properly.
>>
>> I can do it in the jsps I stare at all day long... I'd think it reasonable
>> T5 does real comments.
>>
>> *I haven't tested any of this, nor have I needed to put in server side
>> comments... I find they tend to contain old code that may be needed again
>> (or 'uncomment this for...')
>>
>> --just a thought.
>>
>> --nK
>> nicholas Krul
>>
>>
>>
>> On Fri, Apr 11, 2008 at 7:57 PM, Jim <op...@gmail.com> wrote:
>>
>> > That's perfect, thanks Josh.
>> >
>> > Josh Canfield wrote:
>> >
>> > > How about just doing whatever the equivalent to <t:if test="false"> is
>> > > in T4?
>> > >
>> > > On Fri, Apr 11, 2008 at 11:31 AM, Jim <op...@gmail.com> wrote:
>> > >
>> > >
>> > > > Is there a way to do server-side commenting, ala <%-- --> in JSPs?
>> > > > i.e. to
>> > > > comment sections that you (temporarily) don't wish to be dynamically
>> > > > processed server-side?
>> > > >
>> > > > Adding <!-- --> only precludes client-side processing, of course, and
>> > > > if I
>> > > > try to surround a template section (which contains Tapestry
>> > > > components) with
>> > > > $remove$ tags, I get: "Tag __ on line __ is a dynamic component, and
>> > > > may not
>> > > > appear inside an ignored block." Is there another way? I've been
>> > > > resorting
>> > > > to pasting into a separate file.
>> > > >
>> > > > Thanks,
>> > > > Jim
>> > > >
>> > > > ---------------------------------------------------------------------
>> > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> > > > For additional commands, e-mail: users-help@tapestry.apache.org
>> > > >
>> > > >
>> > > >
>> > > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> > For additional commands, e-mail: users-help@tapestry.apache.org
>> >
>> >
>>
>>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Commenting templates
Posted by Howard Lewis Ship <hl...@gmail.com>.
You can "simulate" a comment directive as a component:
public class Comment
{
boolean setupRender() { return false; }
}
This is a no-op component, it skips directly from the SetupRender
phase to the CleanupRender phase, rendering nothing. This is even
less work than <t:if test="false">.
On Fri, Apr 11, 2008 at 12:03 PM, nicholas Krul <ni...@gmail.com> wrote:
> Good to know that it works, but I would think thats a little dangerous...
>
> If its not commented, I always assume its live code. There should be a way
> to comment properly.
>
> I can do it in the jsps I stare at all day long... I'd think it reasonable
> T5 does real comments.
>
> *I haven't tested any of this, nor have I needed to put in server side
> comments... I find they tend to contain old code that may be needed again
> (or 'uncomment this for...')
>
> --just a thought.
>
> --nK
> nicholas Krul
>
>
>
> On Fri, Apr 11, 2008 at 7:57 PM, Jim <op...@gmail.com> wrote:
>
> > That's perfect, thanks Josh.
> >
> > Josh Canfield wrote:
> >
> > > How about just doing whatever the equivalent to <t:if test="false"> is
> > > in T4?
> > >
> > > On Fri, Apr 11, 2008 at 11:31 AM, Jim <op...@gmail.com> wrote:
> > >
> > >
> > > > Is there a way to do server-side commenting, ala <%-- --> in JSPs?
> > > > i.e. to
> > > > comment sections that you (temporarily) don't wish to be dynamically
> > > > processed server-side?
> > > >
> > > > Adding <!-- --> only precludes client-side processing, of course, and
> > > > if I
> > > > try to surround a template section (which contains Tapestry
> > > > components) with
> > > > $remove$ tags, I get: "Tag __ on line __ is a dynamic component, and
> > > > may not
> > > > appear inside an ignored block." Is there another way? I've been
> > > > resorting
> > > > to pasting into a separate file.
> > > >
> > > > Thanks,
> > > > Jim
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Commenting templates
Posted by nicholas Krul <ni...@gmail.com>.
Good to know that it works, but I would think thats a little dangerous...
If its not commented, I always assume its live code. There should be a way
to comment properly.
I can do it in the jsps I stare at all day long... I'd think it reasonable
T5 does real comments.
*I haven't tested any of this, nor have I needed to put in server side
comments... I find they tend to contain old code that may be needed again
(or 'uncomment this for...')
--just a thought.
--nK
nicholas Krul
On Fri, Apr 11, 2008 at 7:57 PM, Jim <op...@gmail.com> wrote:
> That's perfect, thanks Josh.
>
> Josh Canfield wrote:
>
> > How about just doing whatever the equivalent to <t:if test="false"> is
> > in T4?
> >
> > On Fri, Apr 11, 2008 at 11:31 AM, Jim <op...@gmail.com> wrote:
> >
> >
> > > Is there a way to do server-side commenting, ala <%-- --> in JSPs?
> > > i.e. to
> > > comment sections that you (temporarily) don't wish to be dynamically
> > > processed server-side?
> > >
> > > Adding <!-- --> only precludes client-side processing, of course, and
> > > if I
> > > try to surround a template section (which contains Tapestry
> > > components) with
> > > $remove$ tags, I get: "Tag __ on line __ is a dynamic component, and
> > > may not
> > > appear inside an ignored block." Is there another way? I've been
> > > resorting
> > > to pasting into a separate file.
> > >
> > > Thanks,
> > > Jim
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: Commenting templates
Posted by Jim <op...@gmail.com>.
That's perfect, thanks Josh.
Josh Canfield wrote:
> How about just doing whatever the equivalent to <t:if test="false"> is in T4?
>
> On Fri, Apr 11, 2008 at 11:31 AM, Jim <op...@gmail.com> wrote:
>
>> Is there a way to do server-side commenting, ala <%-- --> in JSPs? i.e. to
>> comment sections that you (temporarily) don't wish to be dynamically
>> processed server-side?
>>
>> Adding <!-- --> only precludes client-side processing, of course, and if I
>> try to surround a template section (which contains Tapestry components) with
>> $remove$ tags, I get: "Tag __ on line __ is a dynamic component, and may not
>> appear inside an ignored block." Is there another way? I've been resorting
>> to pasting into a separate file.
>>
>> Thanks,
>> Jim
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Commenting templates
Posted by Josh Canfield <jo...@thedailytube.com>.
How about just doing whatever the equivalent to <t:if test="false"> is in T4?
On Fri, Apr 11, 2008 at 11:31 AM, Jim <op...@gmail.com> wrote:
> Is there a way to do server-side commenting, ala <%-- --> in JSPs? i.e. to
> comment sections that you (temporarily) don't wish to be dynamically
> processed server-side?
>
> Adding <!-- --> only precludes client-side processing, of course, and if I
> try to surround a template section (which contains Tapestry components) with
> $remove$ tags, I get: "Tag __ on line __ is a dynamic component, and may not
> appear inside an ignored block." Is there another way? I've been resorting
> to pasting into a separate file.
>
> Thanks,
> Jim
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
--
TheDailyTube.com. Sign up and get the best new videos on the internet
delivered fresh to your inbox.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org