Re: [Pharo-users] what is wrong here. Tests are green but the outcome with real code is much to high

2018-12-17 Thread Roelof Wobben
Op 18-12-2018 om 01:30 schreef Richard O'Keefe: Not an answer to your specific question, but your #move... methods look very odd.  I think you meant something like     moveUpAFloor       floor := floor +

Re: [Pharo-users] Teapot installation

2018-12-17 Thread Renaud de Villemeur
Hi Teapot has been moved from smalltalkhub to github. The new location is https://github.com/zeroflag/Teapot You can have a look at the doc on how to install it, either standalone or as a dependency. https://github.com/zeroflag/Teapot/blob/master/docs/Installation.md Renaud Le lun. 17 déc.

[Pharo-users] Teapot installation

2018-12-17 Thread horrido
/Something/ has recently changed. The following now incurs an error: Gofer it smalltalkhubUser: 'zeroflag' project: 'Teapot'; configuration; loadStable. The error is: "Could not resolve: ConfigurationOfNeoJSON in /home/richard/blah blah blah" What's going on??? -- Sent from:

Re: [Pharo-users] what is wrong here. Tests are green but the outcome with real code is much to high

2018-12-17 Thread Richard O'Keefe
Not an answer to your specific question, but your #move... methods look very odd. I think you meant something like moveUpAFloor floor := floor + 1. moveDownAFloat floor := floor - 1. hasReachedBasement ^floor = -1 AH! Now I see it. You are reporting the LAST time

[Pharo-users] what is wrong here. Tests are green but the outcome with real code is much to high

2018-12-17 Thread Roelof Wobben
hello I have this code hasReachedBasement: aFloor     "comment stating purpose of message"     ^ aFloor = -1 initialize     "comment stating purpose of message"     super initialize.     position := 1.     floor := 0 moveFloorDown: aFloor     "comment stating purpose of message"     ^

Re: [Pharo-users] NeoCSV

2018-12-17 Thread Sven Van Caekenberghe
Loading a Tonel project on GitHub using a BaselineOf only works in Pharo 6.1 and higher, AFAIU. Pharo 5 is already pretty old ... > On 17 Dec 2018, at 19:09, eftomi wrote: > > Thanks, Sven! I'm trying to load NeoCSV in Pharo 5.0 from GitHub, but I get > > Could not resolve: BaselineOfNeoCSV

Re: [Pharo-users] NeoCSV

2018-12-17 Thread eftomi
Thanks, Sven! I'm trying to load NeoCSV in Pharo 5.0 from GitHub, but I get Could not resolve: BaselineOfNeoCSV [BaselineOfNeoCSV] in C:\users … However, it loaded nicely in Pharo 6.1 32-bit. Both are on the same location (branch) on the disk. Is there any suggestion what to do (how to debug

Re: [Pharo-users] voygae on P7 install problens on Windows

2018-12-17 Thread Roelof Wobben
Yep, I think so . Roelof Op 17-12-2018 om 17:36 schreef Sanjay Minni: Hi Roelof, can you check if your problem has any bearing to this thread just

[Pharo-users] http://planet.smalltalk.org ?

2018-12-17 Thread Sven Van Caekenberghe
Anybody knows what happened to http://planet.smalltalk.org ? I find it quite handy to catch up with multiple blog posts / feeds.

Re: [Pharo-users] voygae on P7 install problens on Windows

2018-12-17 Thread Sanjay Minni
Hi Roelof, can you check if your problem has any bearing to this thread just discussed http://forum.world.st/Voyage-td5088984i20.html --- Sanjay Minni +91-9900-902902 On Mon, 17 Dec 2018 at 03:26, Ben Coman wrote: > On Mon, 17 Dec 2018 at 03:25, Roelof Wobben wrote: > >> Hello >> >> Are

Re: [Pharo-users] Some issues with Pharo and Ubuntu

2018-12-17 Thread Sven Van Caekenberghe
To load the latest Seaside in Pharo 7 I use the develop branch: Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:develop/repository'; load. > On 17 Dec 2018, at 16:36, Vitor Medina Cruz wrote: > > Hello, > > I am trying Pharo with Docker and I will leave here some

[Pharo-users] Some issues with Pharo and Ubuntu

2018-12-17 Thread Vitor Medina Cruz
Hello, I am trying Pharo with Docker and I will leave here some issues I had since I am unsure where I should report them. The command I am running is: Metacello new baseline: 'Employees'; repository: 'tonel:///home/employeesSource/pharo/'; ignoreImage; onConflict: [ :ex | ex