On Apr 11, 1:58 am, greghauptmann <[EMAIL PROTECTED]> wrote: > However this seems to be because they want to visualize the "OK" and > "Cancel" buttons in the table, so I suppose one question here is > whether the ExtJS example I mention above is actually deficient in the > sense that it doesn't seem to visually differentiate between OK and > cancel. Your comments?
It's not deficient; it just takes a different approach. Since the ExtJS grid is behaving like a spreadsheet, most users intuitively know that placing focus in a cell will make it editable, and that any changes made will persist after the cell is blurred. The example doesn't seem to send out an Ajax request after a cell is changed, but I'm guessing it would in a production environment. Since script.aculo.us's Ajax.InPlaceEditor was built as a stand-alone component, it behaves differently. My guess is that Thomas wrote it to use an OK button because it looks like a form and users are used to having to click on a submit button to commit the changes they make in forms. Keep in mind that Ajax.InPlaceEditor could easily be subclassed/ configured to behave like the ExtJS example (depending on one's personal definition of "easily" ;-). That's more dependent on how the elements are styled, rather than how they behave. Cheers, Andrew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
