[Seaside] Legacy system and Seaside

Boris Popov boris at deepcovelabs.com
Wed Sep 9 15:36:23 UTC 2009


Have you tried implementing the following on your root component and if
so, what happened?

initialRequest: aRequest
	super initialRequest: aRequest.
		at: 'var1'
		ifPresent: [:v | Transcript show: v].



DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5

-----Original Message-----
From: seaside-bounces at lists.squeakfoundation.org
[mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of Thierry
Sent: Wednesday, September 09, 2009 8:34 AM
To: Seaside - general discussion
Subject: [Seaside] Legacy system and Seaside


I am trying to port an older system to Seaside. The code is in
Smalltalk and it uses explicit HTTP POST and GET variables.

Is there a way in Seaside to receive a variable in the url (ie
http://abc/xyz?var1=123) and of course extract it within the Smalltalk

Searching this forum, the closest I found was the following in 2007,
but I cannot figure out how to make this work.

2007/10/16, Randal L. Schwartz <merlyn at stonehenge.com>:
> I'm replacing a badly-written (that is, not *mine*) Perl application
with a
> seaside application.  Let's say I've installed my application at
> /seaside/booking.  How do I intercept, say,
> /seaside/booking?legacy=app&does=this and turn that into an initial
> hit into my app with a couple of instance vars set, so that
> all the remaining /seaside/booking?_s=...&_c=... still work?

Implement #initialRequest (don't forget to send super). WABrowser has
an example. If you want the parameters (legacy and does) to stay
you'll also have to implement #updateUrl:


seaside mailing list
seaside at lists.squeakfoundation.org

More information about the seaside mailing list