Re: When (not) to use session().defaultEditingContext()
Re: When (not) to use session().defaultEditingContext()
- Subject: Re: When (not) to use session().defaultEditingContext()
- From: Ben Ketteridge <email@hidden>
- Date: Fri, 29 Oct 2004 15:34:11 +0100
On Fri, 29 Oct 2004 09:29:12 -0500, Mark Morris
<email@hidden> wrote:
> However, I have some navigations components to address the problem of
> unsaved changes hanging around. My pages conform to a
> "PageNavigationInterface", and my tab and menu components check to see
> if it's okay to complete the change from one page to another. The
> default is to always revert() the defaultEditingContext and change
> pages, on the assumption that clicking a menu item without saving means
> the user wants to abort any changes. This can be overridden for cases
> where transactions span pages, etc. Also, a common scenario has the
> page NOT changing, and a message displayed to the user saying something
> like "This page has unsaved changes. Please save or cancel to proceed."
This sounds like a very interesting strategy, and one which we could
also implement in our system, through our standardised page header and
page tab components.
Ben
--
| Ben Ketteridge email@hidden, aka Gremlin |
| It is by caffeine alone that I set my mind in motion. |
| It is by the coffee that the thoughts acquire speed, |
| the lips acquire stains, the stains become a warning. |
| It is by caffeine alone that I set my mind in motion. |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden