• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: When (not) to use session().defaultEditingContext()
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: When (not) to use session().defaultEditingContext()


  • Subject: Re: When (not) to use session().defaultEditingContext()
  • From: Mark Morris <email@hidden>
  • Date: Fri, 29 Oct 2004 10:50:24 -0500

Ah, backtracking, the bane of the web application developer.  ;-)

I have a strategy for that as well, the end result being that the user sees a "Backtracking has been disabled for this application" page if they use the Back button. But obviously it's a trade-off with page caching and dealing with special cases (e.g. pop-up windows), and is probably not for everyone.

-- Mark

On Oct 29, 2004, at 10:12 AM, Chuck Hill wrote:

Beware the back tracking user!


On Oct 29, 2004, at 7:34 AM, Ben Ketteridge wrote:

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:
village.net


This email sent to email@hidden

--
Practical WebObjects - a book for intermediate WebObjects developers who want to increase their overall knowledge of WebObjects, or those who are trying to solve specific application development problems.
http://www.global-village.net/products/practical_webobjects





_______________________________________________ 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
  • Follow-Ups:
    • Re: When (not) to use session().defaultEditingContext()
      • From: James Cicenia <email@hidden>
References: 
 >RE: When (not) to use session().defaultEditingContext() (From: <email@hidden>)
 >Re: When (not) to use session().defaultEditingContext() (From: Ben Ketteridge <email@hidden>)
 >Re: When (not) to use session().defaultEditingContext() (From: Mark Morris <email@hidden>)
 >Re: When (not) to use session().defaultEditingContext() (From: Ben Ketteridge <email@hidden>)
 >Re: When (not) to use session().defaultEditingContext() (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: When (not) to use session().defaultEditingContext()
  • Next by Date: Re: When (not) to use session().defaultEditingContext()
  • Previous by thread: Re: When (not) to use session().defaultEditingContext()
  • Next by thread: Re: When (not) to use session().defaultEditingContext()
  • Index(es):
    • Date
    • Thread