Starting/restarting with a running server in the image works OK for me (macOS) and recent Pharo 7. What is different for you ?

On 8 Feb 2018, at 12:51, Maximiliano Tabacman via Pharo-dev <pharo-dev@lists.pharo.org> wrote:

From: Maximiliano Tabacman <mtabacman@yahoo.com> Subject: Re: [Pharo-dev] [Seaside-dev] How should I load Seaside/Bootstrap in Pharo 7 ? Date: 8 February 2018 at 12:51:15 GMT+1 To: Pharo Development List <pharo-dev@lists.pharo.org>

Up until Pharo build 382 (sha 115e95c) you could load Seaside by using: Metacello new

baseline:'Seaside3' ;

repository: 'github://SeasideSt/Seaside:master/repository' ; load

If you adapt the baselineOf to include Pharo 7.x

BUT, from build 383 onwards, and tested again just now with 509 (sha 1276a3f) the following happens: - Download Pharo -- OK - Load Seaside master -- OK - Save and quit image -- OK - Start image again -- Hangs and never completes starting

In Ubuntu, this manifests as the main Pharo window opening, but never displaying anything inside it. In Windows, the VM starts and closes without any warning, and no logs are created.

I have no idea why this is happening, and I am not sure if the tests in Travis cover this scenario. On Wednesday, February 7, 2018, 4:14:24 PM GMT-3, Stephane Ducasse <stepharo.self@gmail.com> wrote:

Thanks for pushing this. I plan to work on migrating the seaside book to pillar when I'm done with the moose book and the magritte booklet.

Stef

On Wed, Feb 7, 2018 at 1:45 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:

...

Hi,

Using [ https://github.com/SeasideSt/Seaside/pull/979 ] (I attach a manually modified BaselineOfSeaside3 that I used), I managed to load Seaside 3.2 (GitHub.1516790362) in Pharo 7 (Pharo-7.0+alpha.build.493.sha.d53a70bc946ed83b046f61ac35f00c67fa77269a (32 Bit)) and at least the load and some quick testing with ZnZincSeasideAdaptor (via the spec based Seaside Control Panel) seems to indicate no direct problems.

Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:master/repository'; load.

Why don't we integrate this so that others can load Seaside 3.2 in Pharo 7 too ?

This is _really_ important to make progress, IMHO.

I changed WABrowser>>#updateUrl: to send #name instead of #fullName to the selected class of the model. I am not sure that is entirely correct, but it seemed to work. Apart from that, the WAImageStatus web app worked fine.

Sven

...

On 6 Nov 2017, at 09:49, Sven Van Caekenberghe <sven@stfx.eu> wrote:

OK, Max, thanks for the reply.

I will ask on the Pharo ML as well.

I think it is important that Seaside works on Pharo 7, it is an important use case and test during development, and very necessary as well.

...

On 6 Nov 2017, at 09:40, Max Leske <maxleske@gmail.com> wrote:

Hi Sven,

We don't have a build for Pharo 7 yet. Loading from github would be the recommended way. A quick look makes me think that it will require a bit of work to get the baseline set up correctly. I can't promise anything before next weekend.

How urgent is the situation for you?

Cheers, Max

On 5 November 2017 at 19:22:03, Sven Van Caekenberghe (sven@stfx.eu) wrote:

...

Hi,

I am stuck trying to move my main development to Pharo 7 because I have trouble loading Seaside (which I normally do indirectly by loading the Bootstrap project). Here is my dependency:

project: 'Bootstrap' with: [ spec className: 'ConfigurationOfBootstrap'; repository: 'http://smalltalkhub.com/mc/TorstenBergmann/Bootstrap/main/'; versionString: #stable ]

I also tried the following:

Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:master/repository'; load.

What is the right/recommended way to do it ?

Thx,

Sven

_______________________________________________ seaside-dev mailing list seaside-dev@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

---

seaside-dev mailing list seaside-dev@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev