Return Receipt
Your document: Re: where to go next (after submit
Langdon Stevenson wrote:
How about this: In the case of deleting an object, would it make sense
to display the list of objects that it used to be part of (obviously
with the deleted item missing)? This would allow the user to visually
confirm that the object has in fact been deleted.
That's the
David Stevenson wrote:
On 4/9/04 8:26, "Dan Allen" <[EMAIL PROTECTED]> wrote:
This workflow seems to make the most sense.
Doesn't work in all cases - after deleting something, I'd rarely want to
have a screen that says "this is what you deleted", in that case I would go
to the index page.
This i
On 4/9/04 8:26, "Dan Allen" <[EMAIL PROTECTED]> wrote:
> This workflow seems to make the most sense.
It certainly does in some cases. In my messageboard for instance, after
submitting a new message I go directly to the page that views the message,
rather than back to the index. As people often
Dan Allen wrote:
Every single time I sit down to develop an application in Struts
(though the I am going to present is certainly not unique to Struts) I
find myself stuck on the same question:
"Where to go next?"
Dynamic applications are all about forms and those forms send data to
be saved. Howev
Hi Dan
I agree entirely with you on this front. I follow the same sort of
process myself when saving data from forms.
My personal preference is to be able to see the data that I have saved,
and (if necessary) be able to edit any silly mistakes that I may have
made. This is especially true of
Every single time I sit down to develop an application in Struts
(though the I am going to present is certainly not unique to Struts) I
find myself stuck on the same question:
"Where to go next?"
Dynamic applications are all about forms and those forms send data to
be saved. However, once the da
7 matches
Mail list logo
