Thanks Lance, I'm all set now :)
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/passing-values-into-script-after-ajaxformloop-row-has-been-added-tp5716762p5716800.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
Use an environmental
http://tapestry.apache.org/environmental-services.html
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/passing-values-into-script-after-ajaxformloop-row-has-been-added-tp5716762p5716789.html
Sent from the Tapestry - User mailing list archive at Nabble
Thanks Lance, I'm really good with css, so that part shouldn't be an issue,
just wasn't sure how you were setting the css class from the mixin :)
I think the only other obstacle I foresee is the ability to dynamically
validate the required fields based on the submit action. I currently handle
thi
You can use the @BindParameter annotation in a mixin to get/set parameters on
the component that the mixin is bound to. So, your mixin could set the
"validate" and "disabled" properties the field.
I'm rubbish at css but I assume you can add a class to each required field
and then style an asterisk
Actually I think I may be able to use ehcache for this.
Last question, your saying I may be able to do this with css, "which I would
prefer" and possibly handle the required in the mixin as well. Any thoughts
on how you might get the css / required back to the field? I'm not sure how
t:validate w
Note, servlet containers re-use threads between requests so use tapestry's
PerThreadManager.createValue() to create a value that is per-request.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/passing-values-into-script-after-ajaxformloop-row-has-been-added-tp5716762p5716
Have the mixin call methods on a service backed by a cache. If you don't want
to cache forever, perhaps a ThreadLocal cache will do?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/passing-values-into-script-after-ajaxformloop-row-has-been-added-tp5716762p5716782.html
Sen
Hi Lance,
I planned on initializing the field in setupRender() once I came up with a
viable solution.
The mixin seems like an interesting solution. I guess my only concern would
be the mixin calling the query everytime a new field called a mixin. Any
thoughts on that?
Thanks Lance.
--
View
> private Set fieldIds = new HashSet();
Never initialize a field in it's declaration, the value should be
initialized on setupRender()
> Any thoughts on how to do this?
I'd do it serverside. Attach a mixin to each field which adds the asterisk
to the dom (this can most likely be done through css
