Re: WO's need to "save changes"
Re: WO's need to "save changes"
- Subject: Re: WO's need to "save changes"
- From: Deirdre Saoirse Moen <email@hidden>
- Date: Mon, 2 Aug 2004 16:51:44 -0700 (PDT)
On Mon, 2 Aug 2004, William Norris wrote:
> After walking through Apple's sample "Author" application, I was a
> little confused by the need to "save changes" to the editingContext.
It's been a while since I used Authors -- thuogh I do use, daily, an app
developed from what I learned from that app.
I could be wrong, but I always assumed that this made the in-memory
records and the database jive. It also allows for post-processing prior to
actually saving the data.
> 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.
Sure they do -- how many times have you had a form on the web spit (an
error message) at you because you didn't enter some required data? And
where do you think that gets handled?
> 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?
Maybe I need to look at that app again, because it didn't stick out as
being that weird to me.
--
_Deirdre web: http://deirdre.net blog: http://deirdre.org/blog/
yarn: http://fuzzyorange.com cat's blog: http://fuzzyorange.com/vsd/
"Memes are a hoax! Pass it on!"
_______________________________________________
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.