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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
