[Seaside] New catalog entry for Seaside 3.0.3

Chris Muller asqueaker at gmail.com
Wed Feb 27 02:50:09 UTC 2013

Hi Tobias, I made new Community-Supported catalog entries for:

  DynamicBindings ("4.4" and "head")
  KomHttpServer ("4.4")
  Grease ("1.1.0" and "head")
  Sport (already up-to-date, no action taken)
  Seaside ("3.0.3")

These each consume with single-click (necessary pre-reqs are loaded
automatically for each package).  Installing the head versions always
perform a merge, similar to updating trunk packages.

I didn't know what version to make for DynamicBindings and
KomHttpServer so I just made them the same as the Squeak version
they're for.

I didn't make head versions of KomHttpServer or Seaside because I
wanted to ask your (and others') opinions about it.  If Seaside
Development Team is still putting out Squeak versions and using
Metacello to keep that managed, our catalog entries should definitely
reflect that.  Otherwise, it's worth asking, what is the best way for
us as a community to keep up a dependably working version of Seaside
for Squeak?

Do you know why the Metacello scripts keep failing for stuff that was
once working?


On Tue, Feb 26, 2013 at 7:29 AM, Tobias Pape <Das.Linux at gmx.de> wrote:
> Hi again Seasiders
> Anfang der weitergeleiteten Nachricht:
>> Von: Tobias Pape <Das.Linux at gmx.de>
>> Betreff: [Seaside] Making seaside load in Squeak again.
>> Datum: 26. Februar 2013 09:42:56 MEZ
>> An: Seaside - general discussion <seaside at lists.squeakfoundation.org>
>> Kopie: The general-purpose Squeak developers list <squeak-dev at lists.squeakfoundation.org>
>> Antwort an: Seaside - general discussion <seaside at lists.squeakfoundation.org>
>> Hey Seasiders
>> I am trying to prepare a stable Seaside Image for Squeak 4.4
>> and just tried loading via the Metacello configuration
>> (Like this:
>> Installer ss
>>       project: 'MetacelloRepository';
>>       install: 'ConfigurationOfSeaside30'.
>> ((Smalltalk at: #ConfigurationOfSeaside30 project) version: #stable) load
>> )
>> This fails, as there is a dependency on Zinc #stable in
>> #squeakCommon. Also, I think it is worthwhile to add WebCilent
>> to the Adaptors for, at least, Squeak, if not Pharo, too.
>> I have seen that there is progress for that in the Seaside31 repository,
>> especially for the 3.1 version of Seaside.
> In my effort to see what I can do I succeeded in
> Running Seaside 3.1 atop Squeak 4.4 (I needed to bring an interim Grease 1.1.1 version for that)
> You load  [1]
>         http://netshed.de/seaside/ConfigurationOfGrease-topa.191.mcz
>         http://netshed.de/seaside/ConfigurationOfSeaside30-topa.415.mcz
> and then you can DoIt
> ((Smalltalk at: #ConfigurationOfSeaside30) project version: '3.1.0') load: #(Development OmniBrowser Swazoo WebClient Welcome).
> (Smalltalk at: #WAServerAdaptorBrowser) open
> in a fresh Squeak4.4-12327.
> (Then rightclick in the Seaside Control Panel and 'Add adaptor', a WebServer Adaptor,
> which uses WebClient. Then go to localhost:8080 and be happy.)
> Now I will try to work on Seaside 3.0.
> To any Seaside dev, please consider merging my versions :)
> <<
> Best
>         -Tobias
> [1] this is no MC repo, I just don't have access to the Seaside Repos and didn't want to pollute
>     any MetacelloRepository.

More information about the seaside mailing list