[Seaside] Re: Navigating away from call:'s

Boris Popov boris at deepcovelabs.com
Fri Feb 22 03:40:42 UTC 2008

That kind of navigation is not uncommon. Imagine making a flight reservation, reviewing the checkout page and clicking on header navigation to get back to the home page. I would hate to be limited to next and previous buttons in that situation. If your component never answers, so be it. But you can always hit back in your browser and proceed and that's the whole point IMHO.


-Boris (via BlackBerry)

----- Original Message -----
From: seaside-bounces at lists.squeakfoundation.org <seaside-bounces at lists.squeakfoundation.org>
To: 'Seaside - general discussion' <seaside at lists.squeakfoundation.org>
Sent: Thu Feb 21 19:34:57 2008
Subject: RE: [Seaside] Re: Navigating away from call:'s

> Maybe, but the home example was just one of many possible. What is the
> user is in the midst of an edition and just clicks away?
Cliks away is just too wide. You probably want to include in that editor only
anchors who has callbacks with sense for an edition context. For example an
explicit save or cancel. By saying 'clicks away' you are suggesting just a
different kind of post cancel action?


seaside mailing list
seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20080221/0980b690/attachment.htm

More information about the seaside mailing list