You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Jacob Hookom <ho...@uwec.edu> on 2002/09/24 08:55:32 UTC
RE: [OT][WORKFLOW] Any best practice for "back", "save", "continue" buttons?
Yeah, I used it in a login handler that I wrote for struts, where:
If (not logged in)
(push requested url on stack in session)
)
login.jsp
<form
<hidden value = requestStack.first
It's detailed in Java E-Commerce from Wrox publishing
| -----Original Message-----
| From: Dan Cancro [mailto:DCancro@bridgespan.com]
| Sent: Monday, September 23, 2002 8:43 PM
| To: 'struts-user@jakarta.apache.org'
| Subject: [OT][WORKFLOW] Any best practice for "back", "save",
"continue"
| buttons?
|
| I'm thinking about a design where I maintain a URL stack in a session
| variable that stores where a user has been, so that clicking a "back"
| button
| (not the browser's) will take a user to the right place. It would
work
| like
| this:
|
| Click a "Continue" button -> Push a new URL onto the stack, and take
the
| user to that page
| Click a "Save" button -> Leave the stack alone, and return the
user to
| the same page
| Click a "Back" button -> Pop a URL from the stack and take the
user to
| the URL on the top of the stack.
| Click a "Done" button -> Clear the stack. This would happen when
you
| click a link on a top nav bar or the finish button in a wizard, for
| example.
|
| These would be the basic types of navigation. The actual labels on
the
| buttons or links could be whatever you want. For example, you could
have
| a
| "Continue" button labeled "Save" that takes the user to another page.
|
| Has anyone tried something like this with good or bad results?
|
| Thanks,
| Dan
|
| --
| To unsubscribe, e-mail: <mailto:struts-user-
| unsubscribe@jakarta.apache.org>
| For additional commands, e-mail: <mailto:struts-user-
| help@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [OT][WORKFLOW] Any best practice for "back", "save", "continue" buttons?
Posted by Andrew Hill <an...@gridnode.com>.
Im using something a little more complex that is a bit similar.
I store some information into a uniquely identified object in the session ,
this includes the ActionForm the user is currently editing & a url to resume
editing this, then I forward to another page where the user can edit
something else (perhaps a detail record). The user can repeat this process
to stack to any number of levels. When an operation is complete the user is
returned to the form they were previously editing (the actionForm having
been preserved in the session) to continue editing it in the state is was
before they diverted.
(Incidentally, using the browsers back button in such a case results in a
rather bad case of server state confusion!)
-----Original Message-----
From: Jacob Hookom [mailto:hookomjj@uwec.edu]
Sent: Tuesday, September 24, 2002 14:56
To: 'Struts Users Mailing List'
Subject: RE: [OT][WORKFLOW] Any best practice for "back", "save",
"continue" buttons?
Yeah, I used it in a login handler that I wrote for struts, where:
If (not logged in)
(push requested url on stack in session)
)
login.jsp
<form
<hidden value = requestStack.first
It's detailed in Java E-Commerce from Wrox publishing
| -----Original Message-----
| From: Dan Cancro [mailto:DCancro@bridgespan.com]
| Sent: Monday, September 23, 2002 8:43 PM
| To: 'struts-user@jakarta.apache.org'
| Subject: [OT][WORKFLOW] Any best practice for "back", "save",
"continue"
| buttons?
|
| I'm thinking about a design where I maintain a URL stack in a session
| variable that stores where a user has been, so that clicking a "back"
| button
| (not the browser's) will take a user to the right place. It would
work
| like
| this:
|
| Click a "Continue" button -> Push a new URL onto the stack, and take
the
| user to that page
| Click a "Save" button -> Leave the stack alone, and return the
user to
| the same page
| Click a "Back" button -> Pop a URL from the stack and take the
user to
| the URL on the top of the stack.
| Click a "Done" button -> Clear the stack. This would happen when
you
| click a link on a top nav bar or the finish button in a wizard, for
| example.
|
| These would be the basic types of navigation. The actual labels on
the
| buttons or links could be whatever you want. For example, you could
have
| a
| "Continue" button labeled "Save" that takes the user to another page.
|
| Has anyone tried something like this with good or bad results?
|
| Thanks,
| Dan
|
| --
| To unsubscribe, e-mail: <mailto:struts-user-
| unsubscribe@jakarta.apache.org>
| For additional commands, e-mail: <mailto:struts-user-
| help@jakarta.apache.org>
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>