[Seaside] Using WAFileLibrary for external resources?

Boris Popov boris at deepcovelabs.com
Thu Jan 8 20:17:33 UTC 2009

Seaside elements that support #url: also support #resourceUrl: and you
can adjust the base resourse url in preferences of your application

myApp preferenceAt: #resourceBaseUrl put: 'http://mycdn.com/files/'

Hope this helps,


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.

Thank you.
-----Original Message-----
From: seaside-bounces at lists.squeakfoundation.org
[mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of Udo
Sent: Thursday, January 08, 2009 12:12 PM
To: seaside at lists.squeakfoundation.org
Subject: [Seaside] Using WAFileLibrary for external resources?


as far as I remember WAFileLibrary is not intended to be used in
production. But what's the way "replace" WAFileLibrary  for external

I'm currently thinking of patching WAFileLibrary to return external URLs
(i.e. simply using a different #basePath). This would allow me to export
all the files from the file library and simply upload them to the
external URL. By patching the basePath I would not have to touch each
and every reference to the library by hand. Instead something like
"MyWAFileLibrary  / #myFilePng" would simply return an external URL.

Or maybe something like this is already in the image with me being to
dumb to find it :-)



seaside mailing list
seaside at lists.squeakfoundation.org

More information about the seaside mailing list