[Seaside] odds and ends

[Blanchard, Todd]

Ah, back button support.  We've had a huge discussion around that recently.  Basically, partial page updates don't involve the back button.  If you back off of a "rich" page, then you are leaving the app.  OTOH, hitting forwards needs to take you back to the app just as you left it.  The trick to this seems to be to make  certain that the entire state of the app is represented in hidden form fields.  

The browser will restore form fields when rolling backwards and forwards. We also put a lot of effort into bookmark-ability and this is a nut we are still trying to crack as the state data doesn't generally fit within a 2k url.

-----Original Message-----
From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of Avi Bryant
Sent: Wednesday, June 29, 2005 4:03 PM
To: The Squeak Enterprise Aubergines Server - general discussion.
Subject: Re: [Seaside] odds and ends

On 6/30/05, Blanchard, Todd <tobl at amazon.com> wrote:

> It is very desireable and a number of large web-oriented companies are investing heavily in richer interfaces.  Pages are going to give way to client/server style applications using partial updates to create UI elements.  Page oriented apps are going to begin to look sluggish and 'quaint'.
> 
> Having seaside support this style of development will be a huge win.

Yes.  It is, however, a question worth asking if Seaside is the right basis for this kind of client/server app: for example, Seaside goes to a lot of effort to support page-based concepts like the back button that may not exist (for better or for worse) in a GMail-style app, or if they do are probably implemented with client-side JS hacks.  Is there some totally different design that would make more sense in this world?

Avi
_______________________________________________
Seaside mailing list
Seaside at lists.squeakfoundation.org
http://lists.squeakfoundation.org/listinfo/seaside