Re: [Pharo-users] Pharo 7.0.3 Seaside 3

2019-05-26 Thread Jeff Gray
Righto! Done. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] Pharo 7.0.3 Seaside 3

2019-05-26 Thread Tim Mackinnon
You should log an issue on the Pharo github - with the simplest reproducible case (I think I understand it was loading Ztimestamp in a fresh image via Monticello on 64bit windows? It’s been tricky having a good test on 64bit windows, so would be good if you’ve found something reproducible.

Re: [Pharo-users] Pharo 7.0.3 Seaside 3

2019-05-26 Thread Jeff Gray
I should have mentioned I was running the 64 bit version. I just downloaded the version 7 32 bit image and vm and Seaside downloaded fine -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] Pharo 7.0.3 Seaside 3

2019-05-26 Thread Jeff Gray
Turning off iceberg integration gets me further. If I then load the tonal branch I get an error: ZnUnknownScheme -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] Pharo 7.0.3 Seaside 3

2019-05-26 Thread Sven Van Caekenberghe
> On 26 May 2019, at 11:04, Jeff Gray wrote: > > Same problem with ZTimestamp. > However, I tried Complex and that worked ok You probably loaded that using the Catalog Browser. In the case of the Complex project, that means doing Metacello new smalltalkhubUser: 'Pharo' project:

Re: [Pharo-users] Pharo 7.0.3 Seaside 3

2019-05-26 Thread Johan Brichau
Before loading, try first disabling the Iceberg Metacello integration in the system settings. I believe this can also be done by evaluating: Iceberg enableMetacelloIntegration: false. Also, if you are on windows, do not load the master branch but load the tonel branch of Seaside. So:

Re: [Pharo-users] Pharo 7.0.3 Seaside 3

2019-05-26 Thread Jeff Gray
Same problem with ZTimestamp. However, I tried Complex and that worked ok -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] Pharo 7.0.3 Seaside 3

2019-05-26 Thread Sven Van Caekenberghe
And you are sure that you can load simpler/smaller projects from GitHub using Metacello and a BaselineOf ? For example, Metacello new baseline: 'ZTimestamp'; repository: 'github://svenvc/ztimestamp'; load. If so (you said you were also able to load Garage), that means there is something

Re: [Pharo-users] Pharo 7.0.3 Seaside 3

2019-05-25 Thread Jeff Gray
In fact, if I just do the first statement: Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:master/repository'; get. Pharo closes -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] Pharo 7.0.3 Seaside 3

2019-05-25 Thread Jeff Gray
Same result with that script. Pharo just closes -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] Pharo 7.0.3 Seaside 3

2019-05-25 Thread Cyril Ferlicot D.
Le 26/05/2019 à 02:41, Jeff Gray a écrit : > Nothing showed up running netstat, and I tried rebooting just in case > something in memory but no, 8080 is not being used. > I have checked that I can get other packages. Garage loaded with no problem. > > Just to be sure can you try to execute:

Re: [Pharo-users] Pharo 7.0.3 Seaside 3

2019-05-25 Thread Jeff Gray
Just tried an experiment as I haven't used netstat before. I opened a Pharo 6 image with seaside running. Netstat showed a line for 8080. I closed that image, ran netstat again and the 8080 line was gone. So, I'm fairly certain that 8080 isn't being used. -- Sent from:

Re: [Pharo-users] Pharo 7.0.3 Seaside 3

2019-05-25 Thread Jeff Gray
Just as I'd not used Netstat before I tried an experiment. I fired up a Pharo 6 image which has seaside installed and serving content. Ran Netstat and saw the line for port 8080. Then closed that image and ran netstat again and the 8080 line was gone. So I think I'm safe - 8080 not being used.

Re: [Pharo-users] Pharo 7.0.3 Seaside 3

2019-05-25 Thread Jeff Gray
Nothing showed up running netstat, and I tried rebooting just in case something in memory but no, 8080 is not being used. I have checked that I can get other packages. Garage loaded with no problem. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] Pharo 7.0.3 Seaside 3

2019-05-25 Thread Cyril Ferlicot D.
Le 26/05/2019 à 02:03, Jeff Gray a écrit : > I'll try iceberg later but I just tried this: > > Metacello new > baseline:'Seaside3'; > repository: 'github://SeasideSt/Seaside:master/repository'; > load > > Similar to the browser Pharo just closes. > Hum. I think I already got the problem

Re: [Pharo-users] Pharo 7.0.3 Seaside 3

2019-05-25 Thread Jeff Gray
I'll try iceberg later but I just tried this: Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:master/repository'; load Similar to the browser Pharo just closes. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] Pharo 7.0.3 Seaside 3

2019-05-25 Thread Cyril Ferlicot D.
Le 26/05/2019 à 01:24, Jeff Gray a écrit : > Hey all, > Apologies if this one has been done to death. > I am on windows 10. Just downloaded a fresh image, 7.0.3 and tried loading > Seaside 3 from the catalogue browser. I get the 'Seaside 3 has not been > marked as tested for Pharo 7.0.3' dialog

[Pharo-users] Pharo 7.0.3 Seaside 3

2019-05-25 Thread Jeff Gray
Hey all, Apologies if this one has been done to death. I am on windows 10. Just downloaded a fresh image, 7.0.3 and tried loading Seaside 3 from the catalogue browser. I get the 'Seaside 3 has not been marked as tested for Pharo 7.0.3' dialog but press Yes to continue. It looks like it starts to