[Seaside-dev] Seaside 3.0 final and Pharo 1.0

[Dale Henrichs]

On 10/07/2010 02:26 AM, Philippe Marschall wrote:
> 2010/10/7 Julian Fitzell<jfitzell at gmail.com>:
>> Well, I personally have no issue with someone maintaining a Grease
>> platform package for Pharo1.0 so I'm reluctant to say it's not
>> supported. But I think this falls into the same camp as Squeak or any
>> other platform: we'll do whatever we can to support people who want to
>> maintain support on other platforms but the core team is focusing on
>> just one (currently, the current stable version of Pharo).
>
> If it's really just the three overrides then it would be easy to do.
> OTOH Dale was the first requesting it. If there's strong demand for it
> then I think it would be worth the effort, otherwise not.

Exactly,

I just happened to have grabbed a older Pharo1.1 image for updating and 
whamo I got a bunch of test failures ... tests that passed before 
upgrading to Seaside3.0 final and Grease final.

When I announce the availability of the new configurations for Grease 
and Seaside3.0, I will have to tell folks the configs no longer work on 
Pharo1.0, to cut off the (presumably) inevitable this doesn't work on 
Pharoxyz emails .... So I am still at a loss what I should say ...

For me it would have been easier to just support Pharo1.0 than it has 
been to write the collection of emails, but I am concerned that if/when 
someone says "Seaside3.0 blah doesn't work on Pharo1.0" that the 
response will be "don't use Pharo1.0" if that will be the case, then 
lets up front say that Seaside3.0/Grease are no longer supported on 
Pharo1.0 and be done with it...

It is trivial to support Pharo1.0 with Metacello, so this isn't about 
the amount of work, but about _your_ intent.

Dale