Smalltalk › Pharo › Pharo Smalltalk Users

Seaside 3.1 and 3.2 in Pharo 5

‹ Previous Topic Next Topic ›
 
classic Classic list List threaded Threaded
♦
♦
 6 messages Options
Johan Brichau-2
Reply | Threaded
Open this post in threaded view
♦
♦
|

Seaside 3.1 and 3.2 in Pharo 5

Johan Brichau-2
Hi Pharoers,

If you are looking to use Seaside in Pharo 5, please go ahead and let us know if you run into any issues.
Seaside 3.1.5 and 3.2.0 (unreleased) load into Pharo 5 and all tests are green [1].

Also: I know the finalization of 3.2.0 is long overdue, so news about that is coming soon.

cheers,
Johan


“Load release 3.1"
Metacello new
    configuration: 'Seaside3';
    version: #'release3.1';
    load.

“Load pre-release 3.2"
Metacello new
    configuration: 'Seaside3';
    version: #’3.2.0';
    load
Sven Van Caekenberghe-2
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Seaside 3.1 and 3.2 in Pharo 5

Sven Van Caekenberghe-2
SUPER !!

Thanks

> On 20 Mar 2016, at 19:49, Johan Brichau <[hidden email]> wrote:
>
> Hi Pharoers,
>
> If you are looking to use Seaside in Pharo 5, please go ahead and let us know if you run into any issues.
> Seaside 3.1.5 and 3.2.0 (unreleased) load into Pharo 5 and all tests are green [1].
>
> Also: I know the finalization of 3.2.0 is long overdue, so news about that is coming soon.
>
> cheers,
> Johan
>
> [1] https://ci.inria.fr/pharo-contribution/job/Seaside/
>
> “Load release 3.1"
> Metacello new
>     configuration: 'Seaside3';
>     repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
>     version: #'release3.1';
>     load.
>
> “Load pre-release 3.2"
> Metacello new
>     configuration: 'Seaside3';
>     repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
>     version: #’3.2.0';
>     load


CyrilFerlicot
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Seaside 3.1 and 3.2 in Pharo 5

CyrilFerlicot
In reply to this post by Johan Brichau-2
Le 20/03/2016 19:49, Johan Brichau a écrit :
> Hi Pharoers,
>
> If you are looking to use Seaside in Pharo 5, please go ahead and let us
> know if you run into any issues.
> Seaside 3.1.5 and 3.2.0 (unreleased) load into Pharo 5 and all tests are
> green [1].
>

Hi,

I use Seaside 3.1 in Pharo 5 and I have an application running with this
setup currently.

I thought about sending a mail to the seaside mailing list soon but if
you ask I will respond here :)

This is the main issues I got the past few weeks:
- When we load Seaside of Pharo 5 we have to add "onWarningLog" in order
to avoid a lot of deprecation warning.
- When we register a component to WAAdmin we also have a deprecation
warning.
- In the status component we got a MNU in the VM tab
- In the latest Pharo5 the seaside adaptor is not launched by default on
8080. We have to add it manually (probably because of the SessionManager
changes).

If I see other problems I will contact you :)

In my baseline I load Seaside3 stable, which is the realise 3.1 I think.

> Also: I know the finalization of 3.2.0 is long overdue, so news about
> that is coming soon.
>
> cheers,
> Johan
>
> [1] https://ci.inria.fr/pharo-contribution/job/Seaside/
>
> “Load release 3.1"
> Metacello new
>     configuration: 'Seaside3';
>     repository:
> 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
>     version: #'release3.1';
>     load.
>
> “Load pre-release 3.2"
> Metacello new
>     configuration: 'Seaside3';
>     repository:
> 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
>     version: #’3.2.0';
>     load

--
Cyril Ferlicot

http://www.synectique.eu

165 Avenue Bretagne
Lille 59000 France


signature.asc (836 bytes) Download Attachment
Johan Brichau-2
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Seaside 3.1 and 3.2 in Pharo 5

Johan Brichau-2
Hi Cyril,

I use Seaside 3.1 in Pharo 5 and I have an application running with this
setup currently.

Great! There were indeed very few failing tests that were fixed quickly. 
I think most of Seaside was just working and you confirm that.

This is the main issues I got the past few weeks:
- When we load Seaside of Pharo 5 we have to add "onWarningLog" in order
to avoid a lot of deprecation warning.
- When we register a component to WAAdmin we also have a deprecation
warning.

For Seaside 3.1.5, this will remain the case. The tests are fixed and the broken parts have been replaced but the deprecation warning about #subStrings: will not be fixed anymore in Seaside 3.1
For Seaside 3.2, they have been addressed and you should not get any of those anymore.

- In the status component we got a MNU in the VM tab

thanks for reporting, will look into that.

- In the latest Pharo5 the seaside adaptor is not launched by default on
8080. We have to add it manually (probably because of the SessionManager
changes).

Aha, indeed. The Grease abstraction for this needs to be changed. 
Will take a look asap.

If I see other problems I will contact you :)

Great. You can also report issues on the issue tracker: https://github.com/SeasideSt/Seaside/issues

In my baseline I load Seaside3 stable, which is the realise 3.1 I think.

Yes, that’s correct.
I would suggest using 3.2.0 from now on if you’re not running a production environment though. It’s still a moving target but it’s good if people experiment with it.

cheers
Johan
HilaireFernandes
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Seaside 3.1 and 3.2 in Pharo 5

HilaireFernandes
In reply to this post by Johan Brichau-2
Thanks Johan!


Le 20/03/2016 19:49, Johan Brichau a écrit :
> If you are looking to use Seaside in Pharo 5, please go ahead and let us
> know if you run into any issues.
> Seaside 3.1.5 and 3.2.0 (unreleased) load into Pharo 5 and all tests are
> green [1].
>

--
Dr. Geo
http://drgeo.eu


http://drgeo.eu
Johan Brichau-2
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Seaside 3.1 and 3.2 in Pharo 5

Johan Brichau-2
In reply to this post by Johan Brichau-2
Torsten pointed me to a typo I made for loading version 3.2.0.
This is the correct version:

“Load pre-release 3.2"
Metacello new
    configuration: 'Seaside3';
    version: ’3.2.0';
    load

You could also already use the symbolic version #release3.2, but it’s not released yet :)
Metacello new
    configuration: 'Seaside3';
    version: #'release3.2';
    load

thx for trying and the feedback!
Johan

On 20 Mar 2016, at 19:49, Johan Brichau <[hidden email]> wrote:

Hi Pharoers,

If you are looking to use Seaside in Pharo 5, please go ahead and let us know if you run into any issues.
Seaside 3.1.5 and 3.2.0 (unreleased) load into Pharo 5 and all tests are green [1].

Also: I know the finalization of 3.2.0 is long overdue, so news about that is coming soon.

cheers,
Johan


“Load release 3.1"
Metacello new
    configuration: 'Seaside3';
    version: #'release3.1';
    load.

“Load pre-release 3.2"
Metacello new
    configuration: 'Seaside3';
    version: #’3.2.0';
    load
Free forum by Nabble Edit this page