On Fri, 26 Aug 2011 05:56:07 -0300, Denis Stepanov
<denis.stepa...@gmail.com> wrote:
Guys,
Hi!
I'm kinda disappointed here, I came here with a valid issue and no one
seems to see a problem here, I don't want to fix it in my project we are
already using ifNotNull component I just want a syntax option
improvement which will avoid some behavior/performace issues.
We acknowledge the problem, but we (at least me) disagree with the
solution (adding syntax).
I don't want to change default Object - > boolean coercion
There's no default Object -> boolean coercion.
or somekind of PropertyConduitSource hack,
It wouldn't be a hack. It would be an improvement on the implementation of
the ! operator.
it will break stuff and just admit nobody will change it in the
framework so don't argue that it could be fixed here.
I doubt there's any toString() implementation out there that returns
"false", so it wouldn't break stuff.
I'm surprised that you didn't discover that kind of problem in big
projects with complicated view logic,
Same comment as above.
even Howard suggested to use an approach which I would never suggest in
our team, toString is getting called on unknown object to check if it
isn't a "false" is a little bit to much of Tapestry magic and I don't
think that Tapestry should force developers to use the only one way.
I don't think it's the case here, but sometimes a framework forcing some
way of doing something (the recommended way) is a good thing. :)
--
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: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
