Jesse Knutsen wrote in post #1148836: > On 6/4/14, 1:19 PM, Ronald Fischer wrote: >> However, the form has two buttons, and one is (from the viewpoint of >> logic) doing a GET and the other one should do a POST. Of course I can't >> have both. Maybe it is the form which needs to be modified? > A form can do a get or a post, but not both at the same time. You would > need to change the form action though JS. also you would have to have > your routes set up accordingly.
I didn't think of the possibility to use JS in this case. This would be certainly a possibility, but I wonder: Would you still call it good design? Or should I design the user interface in a different way, for instance having two forms (one for the GET and one for the POST case)? The latter might be cleaner from the programmer's viewpoint, but perhaps confusing to the user. This is a problem which I still will have to solve, when abandoning the current Login design and use the "login" functional object you suggested, because even then, I would have a single form which, depending on the button being pressed, might to a creation of a Dict object, or a retrieval... -- 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 unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/7c4f0c3bd5ea7972d991fd7e2e12052c%40ruby-forum.com. For more options, visit https://groups.google.com/d/optout.
