Seaside Configuration in 2.0

Same story for me.

Is there now a config (like we could load from the Configurations tool
of Pharo2.0? All the ones in there do now work.)

What works was what I found in the mailing list and on Lukas Renggli scripts:

"Basic"
Gofer new
        squeaksource: 'Seaside31';
        package: 'Grease-Core';
        package: 'Grease-Pharo20-Core';
        package: 'Grease-Tests-Core';
        package: 'Grease-Tests-Pharo20-Core';
        package: 'Seaside-Core';
        package: 'Seaside-Pharo20-Core';
        package: 'Seaside-Tests-Core';
        package: 'Seaside-Tests-UTF8';
        package: 'Seaside-Tests-Pharo20-Core';
        package: 'Seaside-Canvas';
        package: 'Seaside-Pharo-Canvas';
        package: 'Seaside-Tests-Canvas';
        package: 'Seaside-Session';
        package: 'Seaside-Tests-Session';
        package: 'Seaside-Component';
        package: 'Seaside-Tests-Component';
        package: 'Seaside-RenderLoop';
        package: 'Seaside-Tests-RenderLoop';
        package: 'Seaside-Tools-Core';
        package: 'Seaside-Widgets';
        package: 'Seaside-Environment';
        package: 'Seaside-Pharo-Environment';
        package: 'Seaside-Tests-Environment';
        load.

"Traditional"
Gofer new
        squeaksource: 'Seaside31';
        package: 'Seaside-Tests-Functional';
        package: 'Seaside-Tests-Pharo-Functional';
        package: 'Seaside-Pharo-Continuation';
        package: 'Seaside-Tests-Pharo-Continuation';
        package: 'Seaside-Flow';
        package: 'Seaside-Pharo-Flow';
        package: 'Seaside-Tests-Flow';
        package: 'Seaside-Tools-Web';
        package: 'Seaside-Pharo20-Tools-Web';
        package: 'Seaside-Tests-Tools-Web';
        package: 'Seaside-Development';
        package: 'Seaside-Pharo-Development';
        package: 'Seaside-Tests-Development';
        package: 'Seaside-Tests-Pharo-Development';
        package: 'Seaside-Examples';
        package: 'Seaside-Tests-Examples';
        load.

"RSS"
Gofer new
        squeaksource: 'Seaside31';
        package: 'RSS-Core';
        package: 'RSS-Tests-Core';
        package: 'RSS-Examples';
        load.

"Javascript"
Gofer new
        squeaksource: 'Seaside31';
        package: 'Javascript-Core';
        package: 'Seaside-JSON-Core';
        package: 'Seaside-Pharo-JSON-Core';
        package: 'Javascript-Pharo20-Core';
        package: 'Javascript-Tests-Core';
        package: 'Javascript-Tests-Pharo-Core';
        package: 'Seaside-Tests-JSON';
        package: 'JQuery-Core';
        package: 'JQuery-Tests-Core';
        package: 'JQuery-JSON';
        package: 'JQuery-Tests-JSON';
        package: 'JQuery-UI';
        package: 'JQuery-Tests-UI';
        package: 'Prototype-Core';
        package: 'Prototype-Tests-Core';
        package: 'Scriptaculous-Core';
        package: 'Scriptaculous-Tests-Core';
        package: 'Scriptaculous-Components';
        package: 'Scriptaculous-Tests-Components';
        package: 'Comet-Core';
        package: 'Comet-Examples';
        package: 'Comet-Pharo-Core';
        package: 'Comet-Tests-Core';
        load.

"Other Packages"
Gofer new
        squeaksource: 'Seaside31';
        package: 'Seaside-Welcome';
        package: 'Seaside-Pharo-Welcome';
        package: 'Seaside-Tests-Welcome';
        package: 'Seaside-HTML5';
        package: 'Seaside-Tests-HTML5';
        package: 'Seaside-InternetExplorer';
        package: 'Seaside-Tests-InternetExplorer';
        package: 'Seaside-Email';
        package: 'Seaside-Tests-Email';
        package: 'Seaside-Pharo-Email';
        package: 'Seaside-Tests-Pharo-Email';
        load.

"REST"
Gofer new
        squeaksource: 'Seaside31';
        package: 'Seaside-REST-Core';
        package: 'Seaside-Pharo-REST-Core';
        package: 'Seaside-Tests-REST-Core';
        load.


"This does not yet load an adaptor.
You can go find ZnZincServerAdaptor in the Zinc repository, like this
(updating all Zn):"

Gofer new
        url: 'http://mc.stfx.eu/ZincHTTPComponents';
        package: 'Zinc-HTTP';
        package: 'Zinc-Tests';
        package: 'Zinc-FileSystem';
        package: 'Zinc-Seaside';
        load.

"And finally,"

ZnZincStaticServerAdaptor startOn: 8081.
ZnZincStaticServerAdaptor stop.

"The method String>>includesSubString: has been deprecated.
Bad spelled, the good one is #includesSubstring:

Select Proceed to continue, or close this window to cancel the operation."
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

On Sun, Mar 24, 2013 at 2:49 PM, [hidden email] <[hidden email]> wrote:
> Same story for me.
>
> Is there now a config (like we could load from the Configurations tool
> of Pharo2.0? All the ones in there do now work.)

Yes there is ConfigurationOfSeaside30 (don't let the name confuse you)
in [1]. It has a class comment that explains what the groups are and
what they should load. Apparently things don't yet happen as they
should and we need to iron out some bugs. Any help is welcome.

 [1] http://www.squeaksource.com/Seaside31

Cheers
Philippe
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

For clarity: is this Configuration class intended to load Seaside 3.1 only or also (still) Seaside 3.0.x ?

Because I _am_ confused.

On 24 Mar 2013, at 16:04, Philippe Marschall <[hidden email]> wrote:

_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Me too... :(

On Sun, Mar 24, 2013 at 6:09 PM, Johan Brichau <[hidden email]> wrote: _______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Okay...

My impression is that everyone is working on a configuration for Seaside 3.1
I want to be able to switch to Pharo2.0 but not to Seaside 3.1

On 24 Mar 2013, at 20:26, Julian Fitzell <[hidden email]> wrote:

_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

On 03/25/2013 01:23 AM, Johan Brichau wrote:
> Okay...
>
> My impression is that everyone is working on a configuration for Seaside 3.1
> I want to be able to switch to Pharo2.0 but not to Seaside 3.1
>


The packages in this Zip work for me for both Seaside 31 and 3.0.7 in
Pharo 2. I've made a 3.0.7.2 version that is Pharo 2 only because of the
256 literal limit per method.  Its my understanding that Tobais Pape may
have made a 3.0.7.2 version for Squeak as well.  I'm not sure.

http://dl.dropbox.com/u/4460862/seaside31Config.zip


_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Hi Paul,

We have to merge our works (or possibly throw away mine :-)
In the meantime, I also talked to Diego to synchronize.

We all have working versions of our own, now we need to consolidate and push them to the repository only.

I am wondering (without having looked at your config): I have a couple of failing tests regarding Grease in Pharo2.0 (for Seaside 3.0.7.1). Are you using the version of Grease from the 3.1 repo or the one from the 3.0 repo?

thanks
Johan

On 25 Mar 2013, at 15:13, Paul DeBruicker <[hidden email]> wrote:

_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Hi Johan,


>From the 3.1 repo.


There are some tests that fail for both Seaside and Grease in the files
I provided.  I can put up an image if you prefer.

I'm also completely fine with my packages being left unused.

Thanks

Paul


On 03/25/2013 07:20 AM, Johan Brichau wrote:
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Am 25.03.2013 um 15:20 schrieb Johan Brichau <[hidden email]>:

> Hi Paul,
>
> We have to merge our works (or possibly throw away mine :-)
> In the meantime, I also talked to Diego to synchronize.
>

If you want, I can chime in, too.

> We all have working versions of our own, now we need to consolidate and push them to the repository only.
>
> I am wondering (without having looked at your config): I have a couple of failing tests regarding Grease in Pharo2.0 (for Seaside 3.0.7.1). Are you using the version of Grease from the 3.1 repo or the one from the 3.0 repo?
>
> thanks
> Johan



So, let us go for a combined,
        Seaside 3.0.7.2
that works on
        Pharo 2 and
        Squeak 4.4

also, let us make 3.1 work on Pharo2.0 and Squeak 4.4 together. :)

best
        -Tobias_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Hi all,

Testing the configuration of Seaside30 version 3.1.0 still give some errors. Here is a complete list. Please suggestions!

In Pharo 2.0, I still have the following tests not in the green:
        1) there is a deprecation warning about "includeSubString:". In Pharo 2 the spelling changed. This is on several place.
        2) In grease the tests are red, because the package Grease-Pharo-Core is renamed to Grease-Pharo20-Core, and Grease-Pharo-Continuation depends on this package.
        3) There is an issue in the UTF8 converter, something about the shortest form.

In Pharo 1.4 I also have some problems:
        4) There is no GRCountingStream. There is a test, that tests the functionality of this class.
        5) The encoder tests fail here, because some messages to the test class give a "does not understand"

How should I handle these things?
1) is easy enough to fix … but it still needs to work in Pharo 1.4 too … so is this something that should be moved to Grease?
2) Should all Grease-Pharo packages be renamed to Grease-Pharo20, so we can fix dependencies?
3, 4 and 5) I don't know what is wrong here. Are these known issues?

Cheers,
Diego

On Mar 25, 2013, at 3:59 PM, Tobias Pape wrote:

_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

On Mon, Mar 25, 2013 at 3:20 PM, Johan Brichau <[hidden email]> wrote:
>
> Hi Paul,
>
> We have to merge our works (or possibly throw away mine :-)
> In the meantime, I also talked to Diego to synchronize.

We have Monticello for this, who needs commit access?

Cheers
Philippe
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

On Fri, Mar 29, 2013 at 11:20 AM, Diego Lont <[hidden email]> wrote:
> Hi all,
>
> Testing the configuration of Seaside30 version 3.1.0 still give some errors. Here is a complete list. Please suggestions!
>
> In Pharo 2.0, I still have the following tests not in the green:
>         1) there is a deprecation warning about "includeSubString:". In Pharo 2 the spelling changed. This is on several place.

Yes, this is known. Since we only have four senders, switching to
#indexOfSubCollection:startingAt: (which is ANSI) is probably the way
to go.

>         2) In grease the tests are red, because the package Grease-Pharo-Core is renamed to Grease-Pharo20-Core, and Grease-Pharo-Continuation depends on this package.

Yes the package verification code has no been updated to deal with the
optional Pharo20 packages.

>         3) There is an issue in the UTF8 converter, something about the shortest form.

That's an expected failure and should therefore be in
#expectedFailures. It's a limitation of the Squeak/Pharo UTF-8 support
[1]. My understanding is people don't want to implement this because
Java follows the standard [2].

> In Pharo 1.4 I also have some problems:
>         4) There is no GRCountingStream. There is a test, that tests the functionality of this class.

That should be in Grease-Pharo-Core, what gets loaded?

>         5) The encoder tests fail here, because some messages to the test class give a "does not understand"

Which messages to which classes?

> How should I handle these things?
> 1) is easy enough to fix … but it still needs to work in Pharo 1.4 too … so is this something that should be moved to Grease?
> 2) Should all Grease-Pharo packages be renamed to Grease-Pharo20, so we can fix dependencies?
> 3, 4 and 5) I don't know what is wrong here. Are these known issues?

 [1] http://www.unicode.org/versions/corrigendum1.html
 [2] https://blogs.oracle.com/xuemingshen/entry/the_big_overhaul_of_java

Cheers
Philippe
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

I made the following changes to the packages in the Seaside30 repository:

- Replaced senders of #includesSubString: by #indexOfSubCollection:startingAt: in Seaside-Core and Seaside-Canvas
- Factored out uses of SystemChangeNotifier to a separate method that delegates differently in Pharo1.x and Pharo2.x (i.e. to SystemAnnouncer). This avoids creating a separate Pharo20 package for Grease in this repository of Seaside.
- Included FileSystem-Legacy package (+ some bugfixes there) for Seaside-FileSystem as a dependency. This should be fine for the 3.0.x branch. Even better is to have this dependency included in SPort (as Paul proposed). I will contact Janko for that.
- Created a new baseline to remove OB and Swazoo2 from the dependencies (see bottom of my email).

All of this renders all Seaside and Grease (except Slime) tests green.
If I can have commit access to the Seaside30 repository, I gladly publish this and continue to work to port Slime as well.

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.

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?

Philippe: will you be at the PharoConf?

cheers
Johan

        spec for: #'pharo2.x' do:[

                spec
                        removeProject: 'OB';
                        removeProject: 'Swazoo2'.

                spec
                        package: 'FileSystem-Legacy'
                        with:[spec repository: 'http://smalltalkhub.com/mc/dh83/fisleg/main'].
               
                spec
                        package: 'Seaside-FileSystem' with: [ spec requires: 'FileSystem-Legacy'].

                spec group: 'Core' overrides: #('Base' 'Development' 'RSS-Core' 'Javascript-Core' 'Prototype-Core' 'Scriptaculous-Core' 'JQuery-Core' 'JQuery-UI' 'Seaside-Email' 'Seaside-HTML5' 'Seaside-InternetExplorer' 'Seaside-Examples' 'RSS-Examples' 'Seaside-Tools-Web' 'Scriptaculous-Components' 'Seaside-Welcome' 'Seaside-FileSystem' )
        ].

On 29 Mar 2013, at 15:53, Philippe Marschall <[hidden email]> wrote:

_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Just a small correction: the new ConfigurationOfSPort was already published, so it's as easy as to require that version in the ConfigurationOfSeaside30

and I need commit access if the changes are accepted so I can publish them.

On 30 Mar 2013, at 08:52, Johan Brichau <[hidden email]> wrote:

_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Am 29.03.2013 um 15:53 schrieb Philippe Marschall <[hidden email]>:

> On Mon, Mar 25, 2013 at 3:20 PM, Johan Brichau <[hidden email]> wrote:
>>
>> Hi Paul,
>>
>> We have to merge our works (or possibly throw away mine :-)
>> In the meantime, I also talked to Diego to synchronize.
>
> We have Monticello for this, who needs commit access?


I would like to, for the Squeak config :)

Best
        -Tobias

_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

On Sat, Mar 30, 2013 at 8:52 AM, Johan Brichau <[hidden email]> wrote:
> I made the following changes to the packages in the Seaside30 repository:
>
> - Replaced senders of #includesSubString: by #indexOfSubCollection:startingAt: in Seaside-Core and Seaside-Canvas

Sounds good.

> - Factored out uses of SystemChangeNotifier to a separate method that delegates differently in Pharo1.x and Pharo2.x (i.e. to SystemAnnouncer). This avoids creating a separate Pharo20 package for Grease in this repository of Seaside.

Ah, the joys of #ifdef, sounds good.

> - Included FileSystem-Legacy package (+ some bugfixes there) for Seaside-FileSystem as a dependency. This should be fine for the 3.0.x branch. Even better is to have this dependency included in SPort (as Paul proposed). I will contact Janko for that.

Sounds good.

> - Created a new baseline to remove OB and Swazoo2 from the dependencies (see bottom of my email).

Sounds good.

> All of this renders all Seaside and Grease (except Slime) tests green.
> If I can have commit access to the Seaside30 repository, I gladly publish this and continue to work to port Slime as well.

Done, and I added Tobias as well.

> 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.

> 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.

> Philippe: will you be at the PharoConf?

No :-(

 [1] http://code.google.com/p/seaside/wiki/Seaside308Changelog

Cheers
Philippe
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

I published the changed packages and opened 3.0.8 for development in Seaside3.0 repository.

On 30 Mar 2013, at 15:07, Philippe Marschall <[hidden email]> 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!).

>> 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

cheers
Johan_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

On Sun, Mar 31, 2013 at 7:13 PM, Johan Brichau <[hidden email]> 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.

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
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

On 01 Apr 2013, at 13:51, Philippe Marschall <[hidden email]> wrote:

>> 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.

thanks!

I just noticed that there still is a dependency of Seaside-Pharo-Core to BlockContext.
We probably need to split of the package for Pharo1.x and remove the BlockContext>>#renderOn: method in the actual package.

I'll take care of that later tonight or tomorrow.
After that, I think it's all set to go.

Johan_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Hi all,

I just made a clean version of the seaside 3.1 configuration that I want to commit.

version 409 is a merge of Johans work in the MetacelloRepository, in 410 I changed the configuration of 3.1.0, such that it loads in Pharo 2.0 as well. I tested this version in both Pharo 1.4 and Pharo 2.0. In Pharo 1.4 this configuration works fine, in 2.0 there are still some projects that give some errors (like swazoo), but loading of version 3.1.0 is fine.

Can someone put them in Seaside3.1 or give me rights to do so?

Thanks,
Diego


Op 1 apr. 2013, om 17:49 heeft Johan Brichau het volgende geschreven:

_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev