Re: WO's need to "save changes"
Re: WO's need to "save changes"
- Subject: Re: WO's need to "save changes"
- From: Tom Jones <email@hidden>
- Date: Tue, 3 Aug 2004 11:15:25 -0500
What you failed to mention was that there is also a revert button on
that app. I think the purpose of the application was to show you how
WO can be used to update data displayed to the customer, without
hitting the database until necessary.
I don't think the purpose of the example was to demonstrate a best
practice, rather it was to demonstrate what can be done with
editingcontexts.
Tom
On Mon, 2 Aug 2004 18:30:39 -0500, William Norris <email@hidden> wrote:
> After walking through Apple's sample "Author" application, I was a
> little confused by the need to "save changes" to the editingContext.
> While I understand how and why it works, and see the potential use of
> this, I'm concerned it will confuse users. Web users are used to
> clicking a "submit" button, and having their changes saved without any
> other action necessary... that's the way most all websites work.
> Granted they understand that they need to "save changes" if working in
> MS Word or something, but they don't really think about it when it
> comes to the web.
>
> I'm curious to know how other developers have handled this... do you
> just retrain users on how to use your WO Application, or do you just
> not make use of this feature and have the ec save changes with every
> form submission?
>
> thanks,
> will
> _______________________________________________
> webobjects-dev mailing list | email@hidden
> Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
> Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.