For the meantime, yes, move your code to Java code:
<t:if test="sufficientPlayers"> ...
public boolean isSufficientPlayers() { return playersOnline > 100; }
This is not so terrible because of live class reloading.
A future release of Tapestry will likely include a few more basic
comparison operators.
On Wed, Sep 23, 2009 at 11:06 PM, Kalle Korhonen
<kalle.o.korho...@gmail.com> wrote:
>
> On Wed, Sep 23, 2009 at 10:23 PM, Gunnar Eketrapp
> <gunnar.eketr...@gmail.com> wrote:
> > I often come across JSP code like ...
> > <c:when test="${ playersOnline > 100 }">
> > According to my understanding T5 does not support expressions in the test
> > parameter. Correct?
> > Now I am coding a test method in the java class for each such case. Is there
> > a smarter solution?
>
> You could use ognl
> (http://chenillekit.codehaus.org/chenillekit-tapestry/ognlbinding.html),
> but I'd argue that coding the test method in the class is the smart
> choice. It keeps your template clean from potentially complex logic
> and since the changes in the page class are reloaded automatically (in
> development mode), you don't loose anything compared to jsp.
>
> Kalle
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
