On Dec 27, 2008, at 1:24 AM, Samo Korosec wrote:
> > Erm, I am probably missing something – why not use the browser's back > button for that? Here's a use case. The application has contact data that consists of name + optional (0..n) addresses, phones, emails, websites. There are a few areas within the application (appointments, check in, check out, activity, admin) where the customer may tell the user something like, "by the way, I have a new phone number and email address". What I'm wanting is to be able to jump to the contact editing, make whatever changes, then return to where the user was. So a simple, "change a phone number and add an email from appointment" would look like: appointments/111 customer contact ->contacts/55 edit -> contacts/55/edit edit phone -> contacts/55/phones/777/edit update -> contacts/55/phones/777 back -> contacts/55/edit add email -> contacts/55/emails/new update -> contacts/55/emails/333 back -> contacts/55/edit back -> contacts/55 back -> appointments/111 I just think that is smoother than having the user press browser back to return to appointments/111 as it skips over the "new/update", "edit/ updates", and "delete/confirm" paths. Also while I'm calling the button 'back', it will probably be displayed as 'next', or 'done', I haven't bounced the semantics off of my customer yet. This is the closest I can see to treating the "update customer contact" as a sub-routine. Thank you, Roy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
