[Seaside] ConfigurationOfSeaside for Pharo 2.0

Torsten Bergmann astares at gmx.de
Mon Mar 4 20:20:28 UTC 2013

Hi @seaside-dev (CC-ing Pharo list and seaside users list):

Pharo 2.0 is upon completion and it would be good to have a working Seaside 
running on it out of the box using a ConfigurationOfSeaside accessible 
through the configuration browser.

(Aida is also already working this way).

What I currently know from own simple tests and postings is that it is basically 
working on Pharo 2.0 using this load script:


and then 

"Zinc Server"
	Gofer new
		squeaksource: 'ZincHTTPComponents';
		"package: 'Zinc-HTTP';"  
		package: 'Zinc-Seaside';

	"Start Zinc"
	" (ZnZincServerAdaptor port: 8080)
	codec: GRPharoUtf8Codec new;
	start. "

There are some small issue left in #includesSubString: vs. #includesSubstring:
(now in Pharo). I found it in 
 - WAAbstractFileLibrary>>updateRoot:,
 - WAFormTag>>isInternetExplorer
 - WARenderContext>>absoluteUrlForResource:

Also when one uploads files using config -> files the methods for the uploaded
content get generated but not packaged with Monticello for whatever reason.

Is there a plan/timeline for having a valid Seaside on top of Pharo available. 
Creating an updates ConfigurationOfSeaside was also discussed here on the seaside list
... but still not yet realized. 
We all know time is always an issue - but at least I want to start a dicussion
if it is possible (maybe with the help from many using a virtual sprint).

Also is there any plan in moving Seaside to SmalltalkHub as well? Since
there is now infrastructure for CI ready on Pharo side it could be used for 
Seaside also. 

Any comments?

If possible respond on "seaside-dev" list so it is discussed on one
central place (http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev)


More information about the seaside mailing list