On Thu, 25 Aug 2011 14:36:26 -0300, Kalle Korhonen
<[email protected]> wrote:
On Thu, Aug 25, 2011 at 8:40 AM, Taha Hafeez <[email protected]>
wrote:
I had a look at the code. It may not be the best of designs but it
certainly is a good resource to learn about the internals of tapestry.
Would love you see a blog post about its implementation !!
So far, nobody has stepped up to propose a better design to solve the
same issue. It may not be the best design, but it's certainly not the
worst either and it addresses the problem in a generic manner rather
than for a specific case or component only. The simple suggestions
that were given do not address the whole problem. Personally, I'd take
a decent working solution any day over no solution.
As far as I can remember, this was the original problem: "I just want to
read the gridCell's propertyValue, propertyName and the current row
object." It was specific for a given component and the solution would
change the Tapestry philosophy too much (at least for my taste). Even
Dragan itself agrees that that isn't a good solution.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, 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]
