On Thu, 24 Feb 2011 16:12:10 -0300, Josh Canfield <joshcanfi...@gmail.com>
wrote:
Yes agreed - I think t:select should take an optional context parameter.
I guess it's a little late to second guess the wisdom of adding a
"zone" parameter to the Select component in the first place... I
hadn't noticed it until now. This functionality could have been
provided as a mixin and then applied to Radio and Checkbox as well...
We can still write this plugin and leave Select as is.
A context parameter doesn't make sense outside of the ajax update
scenario. Someone will inevitably try to use the attribute outside of
an ajax update and file another defect.
What about ajaxContext instead of context in this case?
Would it be reasonable to instead provide an OnChange mixin in core
(one exists in a third party library already, right?) that handled the
context correctly?
I think so. Tapestry 4 was quite easy to make AJAX updates in response to
arbitrary JavaScript events.
--
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: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
