tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Closed: (TAP5-496) Dummy component which renders nothing
Date Wed, 04 Feb 2009 15:39:59 GMT

     [ https://issues.apache.org/jira/browse/TAP5-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Howard M. Lewis Ship closed TAP5-496.
-------------------------------------

    Resolution: Invalid
      Assignee: Howard M. Lewis Ship

Already in the framework,

<ul>
  <li t:type="if" t:test="show.item">conditional item</li>
  <li t:type="if" t:test="literal:false">dummy item</li>
</ul> 

If, Unless and Loop adapt to the element used to define them in the template.

> Dummy component which renders nothing
> -------------------------------------
>
>                 Key: TAP5-496
>                 URL: https://issues.apache.org/jira/browse/TAP5-496
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.0.18
>            Reporter: Folke Behrens
>            Assignee: Howard M. Lewis Ship
>
> I use a lot of dummy texts in my template to see what the page will actually look like
when rendered. To filter out these fragments I created a "Dummy" component whose setupRender
method always returns "false".
> I don't know if this is efficient but it would be nice to have something like this already
in T5's component library.
> More efficient would be a special marker XML attribute that the template parser recognizes.
Maybe something like a t:test attribute which is works like <t:if test="...">...</t:if>.
If the contained expression evaluations to false or null the marked element is filtered.
> <ul>
>   <li t:test="show.item">conditional item</li>
>   <li t:test="literal:false">dummy item</li>
> </ul>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message