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 17:30:54 -0700 (PDT)
On Mon, 2 Aug 2004, William Norris wrote:
> perhaps that's why i'm a little confused. for those not familiar with
> the sample application I'm referring to, it simply builds a list of
> authors and books associated with the authors. There is an "update"
> button to update changes you've made to an entry, but the example also
> has an explicit "save" button that calls EditingContext.saveChanges().
> unless the "save" button is pressed after the "update" button is
> pressed, the changes are not committed. so i take it having an
> explicit "save" button like this is not normally practiced?... rather
> is done behind the scenes at a logic point in the code?
Hrm, I remember wrestling a fair amount with that, trying to get a cleaner
interface, but I'd forgotten that part.
I think the idea was to have someone confirm their changes, but, unless
that's actually needed, it has the problem that people just get used to
clicking OK twice.
If you'd like, I can send you a copy of the (relatively simple) WO app I
derived from some of the concepts. I use it to track manuscripts and
submissions, so it's at least related in concept to the Authors example.
It makes some of the stuff a bit cleaner.
--
_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.