[Seaside-dev] Seaside Configuration in 2.0

Philippe Marschall philippe.marschall at gmail.com
Mon Apr 1 11:51:56 UTC 2013


On Sun, Mar 31, 2013 at 7:13 PM, Johan Brichau <johan at inceptive.be> wrote:
> I published the changed packages and opened 3.0.8 for development in Seaside3.0 repository.

I had a look and they look good.

> On 30 Mar 2013, at 15:07, Philippe Marschall <philippe.marschall at gmail.com> wrote:
>
>>> Since Grease and several Seaside packages have evolved further in Seaside3.1, I propose to keep these changes to the Seaside3.0 repository to make the current stable version of Seaside work in Pharo2.0.
>>
>> As long as you keep the patches coming that's fine with me. Same goes
>> for Squeak 4.4. Actually once we have something working in Pharo 2.0
>> we can very well call it 3.0.8 [1]. Maybe I can even fix 749, which
>> turned out the be thorny.
>
> Yes, and there's a couple of other bugs which have been fixed long time ago which we can include.
> Obviously, we are interested to keep patches coming for this version of Seaside. Although it's probably the last bugfix release for this one.
>
> It would be good to get 3.1 out but I have no idea what is open (I will look!).

Only the configuration.

>>> Next I will sit together with Diego at PharoConf to adapt the configuration class in the 3.1 repository as well. I believe the intention is that this class loads both versions?
>>
>> Probably yes. The configuration is called ConfigurationOfSeaside30 in
>> case you build a 3rd party library that works with both Seaside 3.1
>> and 3.0 but you can only reference a single configuration. Since we
>> probably want it in the metacello repository it will probably have to
>> load both.
>
> Ok. Once 3.0.8 is finished I will merge it in the class in Seaside3.1 repo

I just did that for the #includesSubString: changes.

Cheers
Philippe


More information about the seaside-dev mailing list