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 this by only validating required fields server side. I can then pass the action id into the query restriction on submit and determine which fields are required on the fly. Example When a user clicks the "Save" button, none of the fields are required. When a user clicks the "Submit" button, a subset of fields are required based on the current state of the form. When a user clicks the "broadcast" button, a different set of fields are become required. This becomes more complicating with additional actions and state changes. When the forms state changes, so does all the actions and required fields. (IMHO, This entire validation process is way to complicating) . So the question is, can I dynamically pass into the mixin the submitted action? Example @Property private ApplicationAction action; <t:TextField t:mixins="validationMixin(action)" t:validate="prop:getFieldValidator(vendorInformation,'maxlength=255')"/> -- View this message in context: http://tapestry.1045711.n5.nabble.com/passing-values-into-script-after-ajaxformloop-row-has-been-added-tp5716762p5716786.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
