seaside July 2007

seaside@lists.squeakfoundation.org

106 participants
173 discussions

How to Implement a Website
by Richard K Eng II 02 Jul '07

02 Jul '07

Hi. I'm a Seaside/Smalltalk newbie. I've studied a number of tutorials and I've read quite a few blogs about Seaside. But I am still puzzled about how to implement a traditional website consisting of a number of webpages that are linked together (eg, homepage linked to "about us", homepage linked to "products", homepage linked to "contact us", etc.). You navigate these webpages by clicking on the various menu selections. But how do you implement that in Seaside? 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? Please forgive my newbie ignorance. Thanks, Richard

6 11

Re: [Seaside] WAComponent class>>applicationClass fix
by Boris Popov 02 Jul '07

02 Jul '07

Sorry Lukas! Oh I agree it should be simpler, but as things stand the suggested fix is the only way of subclassing application class especially considering presence of #applicationClass on WAComponent which isn't sent anywhere else as is. Cheers! -Boris (Sent from an iPhone... NOT!) ----- Original Message ----- From: seaside-bounces(a)lists.squeakfoundation.org <seaside-bounces(a)lists.squeakfoundation.org> To: Seaside - general discussion <seaside(a)lists.squeakfoundation.org> Sent: Sat Jun 30 12:44:58 2007 Subject: Re: [Seaside] WAComponent class>>applicationClass fix 2007/6/30, Boris Popov <boris(a)deepcovelabs.com>: > expiryPathFor: Looks like you just ruined the weekend of Lukas ;) Less cryptic this means: Valid point but we think this should be doable easier than by subclassing WAApplication. An expired handler similar to an error handler. There was once a bug for this .... Cheers Philippe > Cheers! > > -Boris > (Sent from a BlackBerry) > > > ----- Original Message ----- > From: seaside-bounces(a)lists.squeakfoundation.org > <seaside-bounces(a)lists.squeakfoundation.org> > To: Seaside - general discussion > <seaside(a)lists.squeakfoundation.org> > Sent: Sat Jun 30 09:16:57 2007 > Subject: Re: [Seaside] WAComponent class>>applicationClass fix > > 2007/6/29, Boris Popov <boris(a)deepcovelabs.com>: > > Looks like #applicationClass wasn't called anymore to allow subclasses > > to override the application, so changed hardcoded WAApplication to a > > call site here, > > > > applicationNamed: aString > > | application | > > application := self applicationClass named: aString. > > application configuration addAncestor: WARenderLoopConfiguration new. > > application preferenceAt: #rootComponent put: self. > > ^application > > > > This is based on VisualWorks 2.7b1.5.1, it might be fixed in the Squeak > > stream already. > > This is not the case. I remember having seen this patch before but we > rejected it because we saw no need tying a component to an application > and for subclassing applications. Can you elaborate what you need > application subclasses for? > > Cheers > Philippe > > > Cheers! > > > > -Boris > > > > -- > > +1.604.689.0322 > > DeepCove Labs Ltd. > > 4th floor 595 Howe Street > > Vancouver, Canada V6C 2T5 > > http://tinyurl.com/r7uw4 > > > > boris(a)deepcovelabs.com > > > > CONFIDENTIALITY NOTICE > > > > This email is intended only for the persons named in the message > > header. Unless otherwise indicated, it contains information that is > > private and confidential. If you have received it in error, please > > notify the sender and delete the entire message including any > > attachments. > > > > Thank you. > > > > _______________________________________________ > > Seaside mailing list > > Seaside(a)lists.squeakfoundation.org > > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > _______________________________________________ > Seaside mailing list > Seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > _______________________________________________ > Seaside mailing list > Seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > _______________________________________________ Seaside mailing list Seaside(a)lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

1 0

Re: [Seaside] How to Implement a Website
by Boris Popov 02 Jul '07

02 Jul '07

First rule of seaside club is to never optimize prematurely. Second rule of seaside club is to never optimize prematurely. In all seriousness one can already serve all resources with a plain web server, just dump them to disk when deploying and change resource URL on your root component to that location. Works great and let's you develop without apache, manage all files in source control system of choice etc. Bookmarkable URLs are also possible, but its hard to get into much detail on a small keyboard, but there was plenty of talk on the list about it just a little while ago. What I'm hinting at is this. Try to implement what you want in seaside and then check if you need to go the static route or not. Chances are you'll save yourself a lot of work :) Cheers! -Boris (Sent from a BlackBerry) ----- Original Message ----- From: seaside-bounces(a)lists.squeakfoundation.org <seaside-bounces(a)lists.squeakfoundation.org> To: Seaside - general discussion <seaside(a)lists.squeakfoundation.org> Sent: Sun Jul 01 18:34:43 2007 Subject: Re: [Seaside] How to Implement a Website Richard Eng wrote: > 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? [snip] I too think this would be a nice feature. It seems that it would be nice to be able to generate an html page which could be served by Apache or web server of choice which contains the static html (parts) of a web page with possibly a JS controller for making the call and inserting the dynamic (Seaside) parts. This would seeming help in a couple of ways. Offloading truly static pieces to a high performance web server, static html, images, css, etc. But allow the truly dynamic web app part to be seaside. This would seemingly help performance of a Seaside site, and provide a potentially reasonable way to implement a RESTful/bookmarkable interface to a Seaside site. I am not yet learned enough to understand all the implications, if and where it would limit are cause problems in a Seaside web app. Or to implement a best practices way of doing this. But I am interesting in learning. I believe this is a good discussion to have. If there are issues or problems cause by such an idea, hopefully they will be disclosed. If not maybe an implementation come for at some point in the future. Just some thoughts. Jimmie _______________________________________________ Seaside mailing list Seaside(a)lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside July 2007