>
Most tapestry folk will agree that putting logic in your templates
makes them brittle and hard to maintain, but sometimes need a little
something in the template. I created a simple utility binding to help
out in these kinds of situations.
Example usage:
Why | ? because : isn't valid in the
On Tue, 25 Oct 2011 14:57:50 -0200, Brian Long
wrote:
Hi Thiago,
Hi!
thanks for the quick reply, I'd already seen the official tapestry
property expressions page but as there's no examples given there I was
hoping there was something else buried in one of the wiki pages?
I don't know an
Hi Thiago,
thanks for the quick reply, I'd already seen the official tapestry
property expressions page but as there's no examples given there I was
hoping there was something else buried in one of the wiki pages?
I'll take your advise and move this logic to the java class, I'm going
to have a lo
In Tapestry 4, we shifted a lot of logic into OGNL because that was
the only logic that could be reloaded (with the template) at runtime,
during development. This was good in some ways, OGNL is still more
versatile than Tapestry 5's property expressions, but came at a huge
cost in terms of reflecti
On Tue, 25 Oct 2011 12:14:47 -0200, Brian Long
wrote:
Hi all,
Hi!
was hoping someone could point me in the direction on a good tutorial
on the new property expressions in tapestry 5.2.6?
http://tapestry.apache.org/property-expressions.html
I was using OGNL
previously and would like to
Thanks for the quick replay, my updated 'ognless' if condition now reads
. . .
${message:EXPORT}
/Brian. :-)
Howard Lewis Ship wrote:
> The not operator (!) coerces the value to a boolean; nil is false, as
> is any kind of empty collection. Thus
> ...
The not operator (!) coerces the value to a boolean; nil is false, as
is any kind of empty collection. Thus
... should work.
On Mon, Oct 5, 2009 at 8:39 AM, Brian Long wrote:
> Hi all,
>
> just a quick question, looking at the property expressions guide @
> http://tapestry.apache.org/tapestry5
