Thanks for the insights, Mark,
On Sep 9, 9:08 pm, Mark Hildreth <[email protected]> wrote: > Second is that the pylons validate decorator probably shouldn't be used, but > I don't see that as a big loss (it's slated for a rewrite anyway). I've just > used my own functions for that part to simplify the validation handling. I'm not using the decorator anyway. Since I'm just starting to use pylons, I prefer to do some more work and to understand how things work instead of relying on these 'automagic' solutions. > Finally, you need to make sure that on the javascript side you are > generating the correct ids for your fields, but I think you'd have this > problem anyway if you're not using a framework. Anyone know of a javascript > library to help with that sort of thing? At some point I'm gonna' take a > look at some of these libraries that have a feature like this and see what > they do for javascript and just make a stand-alone script for helping with > these kind of things. I simply use a hidden <input> field for this which contains the number of dynamically added fields. This field is set by the controller and consequently read and set by the javascript function that is called when adding a new field. cheers, Henk --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
