Re: Using methods other thang getters and listeners

2008-07-21 Thread Filip S. Adamsen
That, or just add @Cached to getItems. -Filip On 2008-07-21 20:48, Howard Lewis Ship wrote: Yes, and perhaps adding a SetupRender render phase method to setup a temporary list with the values to iterate over. On Mon, Jul 21, 2008 at 10:42 AM, Filip S. Adamsen <[EMAIL PROTECTED]> wrote: Hi, O

Re: Using methods other thang getters and listeners

2008-07-21 Thread Howard Lewis Ship
Yes, and perhaps adding a SetupRender render phase method to setup a temporary list with the values to iterate over. On Mon, Jul 21, 2008 at 10:42 AM, Filip S. Adamsen <[EMAIL PROTECTED]> wrote: > Hi, > > On 2008-07-21 17:49, margi wrote: >> >> That's what I did finally! You're right about the fac

Re: Using methods other thang getters and listeners

2008-07-21 Thread Filip S. Adamsen
Hi, On 2008-07-21 17:49, margi wrote: That's what I did finally! You're right about the fact that we're not supposed to have logic in template, but personnaly I think there as some logics that don't worth a Getter. Imagine if my list contains 10 elements through which I have to iterate, I'd be

Re: Using methods other thang getters and listeners

2008-07-21 Thread Thiago H. de Paula Figueiredo
Em Mon, 21 Jul 2008 12:49:43 -0300, margi <[EMAIL PROTECTED]> escreveu: That's what I did finally! You're right about the fact that we're not supposed to have logic in template, but personnaly I think there as some logics that don't worth a Getter. Imagine if my list contains 10 elements throug

Re: Using methods other thang getters and listeners

2008-07-21 Thread Josh Canfield
> > Imagine if my list contains 10 elements > through which I have to iterate, I'd be oblige to write 10 getters, > I would say that a design that is pulling items from a list like this is questionable. I would be curious to hear of a real world example where this is the best solution. Josh On M

Re: Using methods other thang getters and listeners

2008-07-21 Thread Marcelo Lotif
Thiago, you are completely right, but I think sometimes we cannot avoid to make simple tests or pass some arguments to a method... I try not to use it too much, but sometimes it makes my life easier. This is actually a major issue for me. On Mon, Jul 21, 2008 at 12:49 PM, margi <[EMAIL PROTECTED]>

Re: Using methods other thang getters and listeners

2008-07-21 Thread margi
That's what I did finally! You're right about the fact that we're not supposed to have logic in template, but personnaly I think there as some logics that don't worth a Getter. Imagine if my list contains 10 elements through which I have to iterate, I'd be oblige to write 10 getters, I really thi

Re: Using methods other thang getters and listeners

2008-07-21 Thread Thiago H. de Paula Figueiredo
Em Mon, 21 Jul 2008 11:22:31 -0300, margi <[EMAIL PROTECTED]> escreveu: retrieve one element whose index I know. In T4 I'd invoke myList.getItem(index). I've tried ${myList.getItem(index)}, b ut didn't work. I'd appreciate if someone can tell me what I miss or the way to do Try creating a gett

Re: Using methods other thang getters and listeners

2008-07-21 Thread Marcelo Lotif
Hi margi, This is a known issue, marked to be solved to 5.1 version. see https://issues.apache.org/jira/browse/TAPESTRY-1624 I believe this feature was removed because of the bottleneck created by the use of OGNL to evaluate those expressions. Tapestry uses a very own solution that right now is no