[Seaside] Re: Broken Seaside on SqueakMap

[Nevin Pratt]

Avi Bryant wrote:

>On Sun, 29 Jun 2003, Nevin Pratt wrote:
>
>  
>
>>So, it's not a catastrophic problem for the site, so it is not forcing
>>me to backrev.  But yes, it is a problem.
>>    
>>
>
>Well, it's a catastrophic problem as far as I'm concerned - #call: is
>pretty crucial! (How does your site get away with not using it much?)
>  
>

The main page is called 'index'.  So, it's path is:

   http://www.bountifulbaby.com/seaside/index

The 'index' page has three instance variables: 'header', 'footer', 
'main'.  They are used to hold components for the header, footer, and 
the main part of the page.

For the most part, every web interaction just causes 'main' to be set to 
something else, and then the 'index' page is simply re-rendered.  The 
re-rendering is done by the usual #renderContentOn: method of the index 
page, via 'html render: self main'.

The header and footer are answered by #header and #footer accessors, 
which the Seaside framework picks up and renders automatically.

Thus, no #call: anywhere (for the most part).  But, there are a couple 
of exceptions to this.

Oh yea, my Comanche installation also can render static pages, and I 
have a static page at:

   http://www.bountifulbaby.com

that just forwards to:

   http://www.bountifulbaby.com/seaside/index

*******

Well, actually, the above isn't exactly right.  I don't have a 'main' 
instance variable in the index page-- it is called 'embed'.  And I also 
have an 'embeds' collection that caches the components, so when 'embed' 
is set to something else, the cache is checked first.  And also, instead 
of 'self main', it is 'self embed'.

And there is a little bit more going on, too.  But you get the idea.


-- 
Nevin Pratt
Bountiful Baby
http://www.bountifulbaby.com
(801) 992-3137