[Seaside] Swazoo, VisualWorks, and Seaside 2.8
boris at deepcovelabs.com
Mon Apr 20 19:14:32 UTC 2009
I'm sorry, why are long URLs an issue for you?
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
boris at deepcovelabs.com
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.
From: seaside-bounces at lists.squeakfoundation.org
[mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of Carl
Sent: Monday, April 20, 2009 12:13 PM
To: Seaside - general discussion
Subject: Re: [Seaside] Swazoo, VisualWorks, and Seaside 2.8
Ah, I looked at SeasideServer before but I was baffled by the lack of
instance side methods. Everything is in the class methods. Okay, so
I look at the rootDirectory method. It returns 'seaside'. Is this a
disk folder? I change it to point at my static files using the
rootDirectory: method and now my app isn't even found. My Seaside app
isn't a disk file, so why does this affect it?
Am I supposed to use WAExternalFileLibrary for this? It forces a very
long URL. The class comment gives this example
With the VisualWave server I can do this
Or I can specify a subfolder of the public root:
I realize that I can write my own WAFileLibrary subclass, but it seems
like it should be easy to do what I need out of the box.
On Apr 20, 2009, at 2:18 PM, James Robertson wrote:
> See class SeasideServer.
> James Robertson
> Cincom Smalltalk Product Evangelist
> Talk Small and Carry a Big Class Library
> On Apr 20, 2009, at 1:55 PM, Carl Gundel wrote:
>> On Apr 20, 2009, at 1:12 PM, John M McIntosh wrote:
>>> If you check the archives there is some heated arguments about the
>>> Swazoo licence history.
>>> At this point it's LGPL, so can you live with that?
>> I'm not quite sure if I can. I'd really prefer to use Opentalk if
>> I can just figure out how to programmatically:
>> -Get the web server for my Seaside app
>> -Change the port number for the web server
>> -Specify a root folder for static resources so that any URL. For
>> example if I specify the folder to be c:\myseasideapp\public
>> including a file named asdf.html then the URL
>> resolves to that file. Subfolders should also work.
>> These things are probably easy once you know how to do them, but so
>> far I haven't managed to figure it out.
>> -Carl Gundel
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
> seaside mailing list
> seaside at lists.squeakfoundation.org
seaside mailing list
seaside at lists.squeakfoundation.org
More information about the seaside