Just came across this: http://github.com/Marak/route.js
Might be interesting food for thought as it strikes me that would hook into lifts function based javascript quite nicely. Cheers, Tim On Jan 14, 4:03 pm, Alex Boisvert <[email protected]> wrote: > Depends on your application. What would it do if it wasn't implemented with > AJAX? > > This isn't a magical feature. It's a feature that allows you to support > the back button 1) if it makes sense to you and 2) if you can figure out a > way to make it safe for the user. > > For example, you click the delete button. The snippet is replaced by "Item > deleted". You click back button, now you're back to the item you deleted. > If you go back again, maybe you go back to the list of items you were > working with and from there you can go delete others. So it's just a > navigation tool to support existing web idioms. > > alex > > On Thu, Jan 14, 2010 at 7:52 AM, Naftoli Gugenheim > <[email protected]>wrote: > > > > > If you press delete then back what will happen? > > > ------------------------------------- > > Alex Boisvert<[email protected]> wrote: > > > On Wed, Jan 13, 2010 at 6:10 PM, Naftoli Gugenheim <[email protected] > > >wrote: > > > > I haven't really used Ajax much but it seems to me there are two kinds of > > > changes. > > > 1. Modifying the view, e.g., clicking an emal in Gmail, or Expand All. > > One > > > can make an analogy to a GET request, in that there's no permanent > > change. > > > 2. Taking actions, e.g., invoking an action on the server, or deleting > > the > > > viewed email in Gmail. The analogy would be to a POST. > > > It seems to me that Lift's Ajax is often used for #2. However backbutton > > > support doesn't really make sense in that scenario. > > > I think the split between 1/2 depends greatly on your application. I'd say > > the backbutton is as useful for POST as it is for GET. It's a navigation > > tool and sometimes the best way to get where you want is to go back two > > steps and forward in another direction. Mind you, it's still more > > complicated to handle actions (POST) is a safe manner. The back button > > doesn't undo and if you go forward the same way, you may trigger a > > duplicate > > action. It's up to the application to handle such cases. > > > I think this is applicable to the wizard stuff too. I think back button > > support would be a very nice usability enhancement there. > > > alex > > -- > > You received this message because you are subscribed to the Google Groups > > "Lift" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<liftweb%[email protected] > > > > > . > > For more options, visit this group at > >http://groups.google.com/group/liftweb?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Lift" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<liftweb%[email protected] > > > > > . > > For more options, visit this group at > >http://groups.google.com/group/liftweb?hl=en.
-- You received this message because you are subscribed to the Google Groups "Lift" 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/liftweb?hl=en.
