>>> Hm, I thought Tobias meant "run source.squeak.org's image with SS3
>>> code" rather than "move source.squeak.org's code to the SS3 servers".
>>
>> Porting SS3 from GemStone to Squeak would probably be harder than just
>> upgrading the existing code.
>>
>
> Have you actually looked at SS3?
> I develop SS3 in Squeak (and pharo and gemstone)
> and it always runs on Squeak (as long as Seaside does, for that matter).

Ok, I didn't know that.  I thought SS3 was targeted at GemStone.
You're saying it'll run on Squeak as-is, right now?

> Installer squeaksource
>    project: 'MetacelloRepository';
>    install: 'ConfigurationOfSqueakSource'.
>
> ((Smalltalk classNamed: #'ConfigurationOfSqueakSource') project version: #bleedingEdge) load: 'All'.
> "
>  Or without tests:
> ((Smalltalk classNamed: #'ConfigurationOfSqueakSource') project version: #bleedingEdge) load: 'Full'.

When I tried the above in trunk, it goes for a while before I get an
error which says:  " 'table is already defined in a subclass of nil'".
 Apparently while trying to load "WAEncoder" class...

In Squeak 4.4, is an immediate error.

> Have an image, see for yourself:
> https://dl.dropboxusercontent.com/u/14917452/SS3.zip
> http://localhost:8080/installSS
>
> You know, SS3 is one of the two only reasons I have made the
> Squeak/Seaside all-in-one images. It is as if nobody cared about
> seaside in the squeak world anymore.
> It actually upsets me a little bit.

Me too.  I think people have given up because Seaside has not been
reliably loadable on Squeak for a long time.  That's why I think it
would be good for us as a community to depend on a Squeak-based
web-site so we will keep it maintained like the trunk.

Squeak was a leader of web-dev tech in the early 2000's with Seaside.
But the irony about trying to keep Seaside accessible on all platforms
including Pharo is that it has became a huge, complex beast for all
platforms, and inaccessible on its original platform entirely.

You and I both have done work to try to keep Seaside 3.x loading and
working in Squeak.  Your script above doesn't work and now even my
SqueakMap script for Seaside 3.0.3 no longer works because someone
decided to delete all versions of Grease from SS3 without
understanding or caring about the impacts to Squeak.

(Sigh)  So, in some respects it almost seems easier to just take
charge of our own web-software destiny and fork our own Seaside, in
our own repositories than to beg for cooperation from, ahem, other
groups.

And maybe that is why I thought there may be a case for the good ol'e
days of SS2 on Seaside 2.x.  Much smaller and easier to install and
understand, just a few packages compared to 3.x.  I don't care, I just
think we need control because, if we don't, you can bet, in one week
it won't work anymore.

Maybe web guru's will speak up, I just think we need to do _something_
to wrest back control of our own software-destiny for web-development
for Squeak.  People want to build their OWN images from a base 4.4 /
4.5, not download a special all-in-one "Seaside" image..