Re: [Pharo-users] Engineering notation

2017-08-30 Thread Marcus Denker
yes, some people use 1halt. instead of self halt as it is less characters to type… Marcus > On 30 Aug 2017, at 22:48, Andreas Sunardi wrote: > > I probably telling what has been known for ages, but some months ago I was > pleasantly surprise to find a space is not needed between t

[Pharo-users] Pharo 6 FileSystem>>changeDirectory: is missing

2017-08-30 Thread Andreas Sunardi
I found FileSystem class has changed from Pharo 5 to Pharo 6. I've been using FileSystem>>changeDirectory to make my program (Pharo 5) runs in the current working directory (thus able to find local files). This is now broken because #changeDirectory doesn't exist anymore. The change seems intentio

[Pharo-users] Engineering notation

2017-08-30 Thread Andreas Sunardi
I probably telling what has been known for ages, but some months ago I was pleasantly surprise to find a space is not needed between the receiver and the message when the receiver is a number. Because of that I'm able to define, for example #u, #n and #k for micron, nano and kilo units, and use the

[Pharo-users] #parseMethod:onError: isn't as obvious as expected - is it me?

2017-08-30 Thread Tim Mackinnon
I’m looking for some feedback on the usage of RBParser>>#parseMethod:onError:. I am looking at ways of improving the way we edit code - and making things work (as least for me - but maybe for everyone) a bit more like IntelliJ where they have some great code operations and very good keyboard su

[Pharo-users] Roassal question on Kiviat diagrams and coloring

2017-08-30 Thread Sebastian Heidbrink via Pharo-users
--- Begin Message --- Hi all! Does anybody have an advice on how to color Kiviat diagram nodes and edges based on a nodes property/attribute? For example, if I wanted to create a Kiviat diagram with weather information and color all days (nodes and edges) with temperatures above 0 degrees in

Re: [Pharo-users] [Fuel] Conditions for Fuel file compatibility?

2017-08-30 Thread H. Hirzel
Norbert Thank you for the info that the version of Fuel is important, not image version nor VM. This looks promising: my Pharo 5 image has FLMaterializer new version 194 and the Pharo 6.0/6.1 image has FLMaterializer new version 194 I'll to some tests. Regards Hannes On 8/30/1

Re: [Pharo-users] [Fuel] Conditions for Fuel file compatibility?

2017-08-30 Thread Norbert Hartl
Hannes, fuel should not be depend on image or vm version just on its own version. The rule is that if you have the same version of fuel in two images you should be able to use it on both images regardless of image or vm version. The current issue is probably vm dependent. I can also read fuel f

[Pharo-users] [Fuel] Conditions for Fuel file compatibility?

2017-08-30 Thread H. Hirzel
Hello I think the question is good for a new thread: Tim M. reported that a fuel file from a 6.1 image could be read in a 7.0 image. I wonder what the conditions are for this type of compatibility - type of objects written? - no class definition changes? - ... Regards Hannes

Re: [Pharo-users] Pharo 61 crashes on iceberg history

2017-08-30 Thread Esteban Lorenzano
there was a problem with latest VM. now, latest Iceberg release along with latest VM should fix this problem. Esteban > On 3 Aug 2017, at 11:32, Esteban Lorenzano wrote: > > >> On 3 Aug 2017, at 11:24, Herby Vojčík wrote: >> >> Esteban Lorenzano wrote: >>> Hi, >>> >>> can I have a reproduc

Re: [Pharo-users] CodeImporter. 256 literals limit

2017-08-30 Thread Esteban Lorenzano
you can try the new (still experimental) packaging for Pharo: CentOS 6.8: # Add the repo $ yum-config-manager --add-repo http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/CentOS_6/devel:languages:pharo:latest.repo # Install 32bit packages (with X11 dependency for *-ui o