IMHO not good idea: you leave out all security filters, do_new methods, associated data updates, concurrent edit(update) locking, developers specific definitions/procs, plus converting all new and edit stubs to JS what if data changed between page load (list) and "new"(or "edit")?
for better user experience i think it's good approach to mantain ajax calls light as a ping :D again, that's IMHO... On Mon, Jun 15, 2009 at 8:52 AM, Dave Roberts <[email protected]>wrote: > > Hello, > > I was browsing and I noticed that pulling up the forms for Create New > and Edit both send a request to the server. Would it be possible to > make these calls not run to the server? It would be a better > experience for the user. What would the design look like? It is > possible? What trade-offs would it have? How could it be implemented? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ActiveScaffold : Ruby on Rails plugin" 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/activescaffold?hl=en -~----------~----~----~----~------~----~------~--~---
