On Aug 10, 2009, at 4:51 AM, Pratik wrote: > > -1. > > On Mon, Aug 10, 2009 at 12:39 PM, Yehuda Katz<wyc...@gmail.com> wrote: >> I am in favor of a standard delete action, analagous to new and >> edit. I >> can't think of a good reason not to have it--it shows good practice >> and >> isn't exactly a new concept. > > It makes poor and slow UI. > >> We have new and edit as HTML precursor actions >> for the POST and PUT verbs, why not delete as HTML precursor for >> DELETE. One >> of the biggest wins of Rails is conventionality; when you come into >> a new >> Rails app, you don't have to wonder what the edit action is called. >> Why not >> extend this to delete confirmation screens as well? > > When you edit/create - you don't just press one button. You enter a > good amount of data too. That's not true when you DELETE the record in > 99.99% of the cases.
Not sure I understand your position. The existing functionality where a JS dialogue appears requires the user to just press one button, and you're saying that this is good UI, but having an HTML form appear requiring the user to press a button is not good UI? Seems like precisely the same UI to me, just in two different forms and with the obvious latency for the non-JS user. As others have mentioned, surely a slower UI is better than no UI at all? -- Jason King --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
