<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>Re: [Seaside] Re: Navigating away from call:'s</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>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.<BR>
<BR>
Cheers!<BR>
<BR>
-Boris (via BlackBerry)<BR>
<BR>
----- Original Message -----<BR>
From: seaside-bounces@lists.squeakfoundation.org <seaside-bounces@lists.squeakfoundation.org><BR>
To: 'Seaside - general discussion' <seaside@lists.squeakfoundation.org><BR>
Sent: Thu Feb 21 19:34:57 2008<BR>
Subject: RE: [Seaside] Re: Navigating away from call:'s<BR>
<BR>
<BR>
> Maybe, but the home example was just one of many possible. What is the<BR>
> user is in the midst of an edition and just clicks away?<BR>
><BR>
Cliks away is just too wide. You probably want to include in that editor only<BR>
anchors who has callbacks with sense for an edition context. For example an<BR>
explicit save or cancel. By saying 'clicks away' you are suggesting just a<BR>
different kind of post cancel action?<BR>
<BR>
Sebastian<BR>
<BR>
_______________________________________________<BR>
seaside mailing list<BR>
seaside@lists.squeakfoundation.org<BR>
<A HREF="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</A><BR>
</FONT>
</P>
</BODY>
</HTML>