[Seaside] How to Implement a Website

Richard Eng richard.eng at rogers.com
Mon Jul 2 00:28:56 UTC 2007

Okay, as a Seaside/Squeak newbie, please forgive my stupid questions...

How do I embed or redirect to a Seaside app from within static html content?
I tried to find Boris' blog post concerning this but I was unsuccessful.

I looked at "Best way to embedding Seaside in static HTML?" but the iframe
technique seems problematic. The rest of the thread is over my head.

Is there not a "best practice" recommendation for how to mix static html and
Seaside components together? This would seem to me to be a common (the most
common!) way to develop a website. As I understand it, you want static html
to be served up by Apache for performance reasons, and Seaside for the
actual application (business logic).

And you want the Seaside app embedded within the static html content so that
you have a consistent look and feel for the entire website. This has to be
the canonical architecture for a website/web app, doesn't it?



On 6/29/07 8:18 AM, "Sebastian Sastre" <ssastre at seaswork.com> wrote:

> Hi Richard,
> a couple of threads ago ("Best way to embedding Seaside in static
> HTML?") was discussed about exactly this concern you have, may you want to
> take a look at it.
> With Seaside the html is always a consequence of your Seaside
> application so you will have to forget the approach of using it as a cause
> (of a page). Also the experience of developing those applications will be *a
> lot* like developing desktop applications (developing the causes of the
> html). That is one of the key advantages of Seaside because it will be
> tempting you (developer) to deploy desktop like applications that run in web
> browsers.
> Said that, you can allways do "static windows" on desktop
> applications. In seaside you can do that making components that render it's
> content in the canvas. The problem of this is that is not *that* efficient
> nor escalable as an apache serving files.
> To make the static efficient you can manage apache to serve static
> content (html files and even resources like jpg, png, etc) and embbed (or
> redirect) when proper your Seaside application (that you may want it look
> the same with CSS).
> There is a blog post in the blog of Boris that will give you
> technical details on how this is archieved (mostly apache conf stuff).
> Hope this helps, cheers,
> Sebastian Sastre
>> -----Mensaje original-----
>> De: seaside-bounces at lists.squeakfoundation.org
>> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre
>> de Richard K Eng II
>> Enviado el: Viernes, 29 de Junio de 2007 08:02
>> Para: Seaside - general discussion
>> Asunto: Re: [Seaside] How to Implement a Website
>> I thought one of the advantages of Seaside was being able to
>> do away with HTML templates and to generate HTML
>> programmatically. If a particular webpage consists of a mix
>> of HTML (from the traditional website) and a dynamic web app,
>> are you supposed to generate HTML just for this webpage?
>> How do you get your website to serve up *both* the
>> traditional webpages and the Seaside app? (I saw a blog that
>> explained how to setup a virtual http host and a Seaside
>> server in Apache2, but I am unclear about the mechanism by
>> which traditional webpages and the dynamic app coexist.)
>> Thanks,
>> Richard
>> ----- Original Message -----
>> From: "Lukas Renggli" <renggli at gmail.com>
>> To: "Seaside - general discussion"
>> <seaside at lists.squeakfoundation.org>
>> Sent: Friday, June 29, 2007 1:14 AM
>> Subject: Re: [Seaside] How to Implement a Website
>>>> Do you create a component for each webpage with its own
>> renderContentOn:
>>>> message? If so, how do you invoke a webpage component when
>> you click on 
>>>> one
>>>> of the menu anchors (eg, html anchor callback: [???] with:
>> 'about us'.). 
>>>> Is
>>>> this even the correct approach using Seaside?
>>> You will have a hard time building a traditional web site with
>>> Seaside. Seaside's target is building dynamic Web Application. It is
>>> possible though.
>> _______________________________________________
>> Seaside mailing list
>> Seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the Seaside mailing list