Frederick Cheung wrote in post #960432: > Another [approach] would be to have the form created server side (ie > normally), > but fill in the form values client side once they become known (and if > you care you can have the form hidden initially and show it only once > the geocoding data is available) > > Fred
When I first read this, I slapped my head and said "doh! -- it's javascript, so of course it can modify the form generated by the server". But then I realized that it won't exactly work in my case. I oversimplified the original problem statement: the javascript can generate an arbitrary number of these forms, and I don't know how many that will be beforehand. I s'pose I could let the server generate a single form, as Fred suggests, and use that as a template for the javascript code to replicate/modify as needed. This approach is still a little bizarre but might be easier to maintain. Right now, I'm doing it the stupid way (described in the OP) and it's working. - ff -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en.
