<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Thinking about Seaside installation and pages on the homepage, I started to think about putting a Seaside installation script in SqueakMap. [1] (This script loads with no server, I don’t think, so I figure it’s incomplete. Does anybody have a more complete one?) <div class="">Maybe I’d create two new pages: Seaside; and, Installation. (That URI - Installation - is from the old site). And then add links to SqueakMap and SqueakSource on that page. </div><div class="">But then it made me think I’d have to find out who the Seaside maintainers are to ask them to put in a new script. But Seaside should be what we were calling a few years ago a Community Supported Package. Is it a CSM in SqueakMap? How does that work? </div><div class="">It seems to me that creating a Seaside page and slapping a Metacello installation script on it is a short sighted solution. Perhaps the notion of a CSM could be explored at this juncture. <br class=""><div class=""><br class=""></div><div class="">Chris </div><div class=""><pre style="background-color: rgb(255, 255, 255);" class="">[1] </pre><pre style="background-color: rgb(255, 255, 255);" class="">(Installer ss project: 'MetacelloRepository') install: 'ConfigurationOfSeaside3'.
((ConfigurationOfSeaside3 project) version: #stable) load.</pre><div class=""><br class=""></div></div></div></body></html>