Robert Walker wrote: > Marnen Laibow-Koser wrote: >> Robert Walker wrote: >> [...] >>> The view is where these things get a little more tricky. There is no >>> "one right way" to do this. It's going to depend on your specific case. >>> Often it's a good idea to allow the user to add steps by using AJAX to >>> insert new form fields to hold all the steps the user may want to enter. >> >> Not Ajax, just straight client-side JavaScript. There is no need to >> involve the server. > > That was boneheaded of me! All that's needed is client-side DOM > manipulation with no server involvement. The AJAX acronym should just go > way. It's used to generally and really has no clear meaning anyway. And > here I am perpetuation the problem. :-)
Ajax (specifically not an acronym according to its creator, although it really is one) has a very clear meaning -- asynchronous JavaScript server requests that don't require a page reload. The term is useful and I see no reason to drop it -- if it's used in its proper sense. This wasn't it. :) Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- 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.
