[Seaside] Adding Libraries programatically?

Boris Popov boris at deepcovelabs.com
Wed Oct 25 16:26:13 UTC 2006

| app |
app := (self registerAsApplication: 'online')
		preferenceAt: #useSessionCookie put: true;
		preferenceAt: #deploymentMode put: false;
		preferenceAt: #serverProtocol put: #http;
		preferenceAt: #serverPort put: 9009;
(app libraries)
 remove: WAStandardStyles;
 add: SULibrary;



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

Thank you.

-----Original Message-----
From: seaside-bounces at lists.squeakfoundation.org
[mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of Ron
Sent: Wednesday, October 25, 2006 9:24 AM
To: 'The Squeak Enterprise Aubergines Server - general discussion.'
Subject: [Seaside] Adding Libraries programatically?



Is there a preferred way to check and add a library programmatically?
Since Seaside is holding configuration information in instances if I
don't save the image I lose SULibrary.


I would like to have components that need SULibrary check the
application they are installed in and add the library if necessary or
alternately it would be nice to add the library at the same time as
#registerAsApplication:.  Is anyone doing this or have suggestions on
how this should be done?  I saw that WAApplication libraries has the
information but I didn't find an easy way to get to the WAApplication
for the component from the component itself.  





More information about the Seaside mailing list