Thanks for the tips Thiago & Kristian they sound promising! I will give them a try and let you know...
PS: I do absolutely love the static structure, dynamic behavior of Tapestry! Cheers, Peter > so you want to generate a link in a grid and dependending > on a parameter have a mixin attached. > you can solve it by using a delegate that is directed to a block > (or component) that in one case contains a simple eventlink and > in the other case contains a eventlink with the attached mixin Or passing some parameter to the mixin controlling if it will really do something or not. Instead of dynamically applying a mixin or not, you always apply the mixin but not always it will do something. > that's one of the drawbacks you have, when following the static > structure, dynamic behaviour paradigm. you always have to > have all posibilities defined in advance. and from my point of > view it's not always that bad. You're right. You just need to think with the static structure in mind. There are solutions for almost any scenario, they just aren't always implemented the same way as in dynamic structure frameworks. ----- Original Message ----- From: "Thiago H. de Paula Figueiredo" <[email protected]> To: "Tapestry users" <[email protected]> Sent: Tuesday, 30 March, 2010 15:17:26 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: Generated links in a loop On Tue, 30 Mar 2010 09:08:19 -0300, Kristian Marinkovic <[email protected]> wrote: > so you want to generate a link in a grid and dependending > on a parameter have a mixin attached. > you can solve it by using a delegate that is directed to a block > (or component) that in one case contains a simple eventlink and > in the other case contains a eventlink with the attached mixin Or passing some parameter to the mixin controlling if it will really do something or not. Instead of dynamically applying a mixin or not, you always apply the mixin but not always it will do something. > that's one of the drawbacks you have, when following the static > structure, dynamic behaviour paradigm. you always have to > have all posibilities defined in advance. and from my point of > view it's not always that bad. You're right. You just need to think with the static structure in mind. There are solutions for almost any scenario, they just aren't always implemented the same way as in dynamic structure frameworks. -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, software architect and developer, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br --------------------------------------------------------------------- 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]
