Re: [Pharo-users] Pharo code formatting

2013-12-28 Thread Ihor Mykhalevych
Thanks. I thought what version will be better to use to play with this formatter. On 28.12.13 12:32, Stéphane Ducasse wrote: Not much as far as I know. Hello everyone! Does anyone know if there were some changes to the Pharo code formatter after Pharo version 2.0? Best regards, Ihor Myk

Re: [Pharo-users] Pharo code formatting

2013-12-28 Thread Stéphane Ducasse
Not much as far as I know. > Hello everyone! > > Does anyone know if there were some changes to the Pharo code formatter after > Pharo version 2.0? > > Best regards, > Ihor Mykhalevych >

Re: [Pharo-users] have a question for morphic Designer in pharo.

2013-12-28 Thread Stéphane Ducasse
This is really cool :) I would love to see how we could change the event system used because using thisContext all the time does not work and breaks the idea of not reifying the stack all the time. Once it will be working, it would be really nice to see if we can generate spec specification.

Re: [Pharo-users] Is someone working with Log4s?

2013-12-28 Thread Hernán Morales Durand
Actually, locationInfo could be directly thisContext as used by the log facilities methods: EsLogManagerClass class>>logEvents index := (Time now asMilliSeconds rem: 6) + 1. "pseudo random number" message := messages at: index. "pick a random message" locationInfo := thisCont

[Pharo-users] Smalltalk Meetup in Zürich, January 6th

2013-12-28 Thread jtuc...@objektfabrik.de
Hi lists, you may already have seen it, but just in case you haven't: we're going to sit down for some Burgers or Pizza and beer and all things Smalltalk at Restaurant Steinfels in Zürich[1] on Monday, January 6th, starting at 7pm. So if you are interested in meeting with other Smalltalk dev

Re: [Pharo-users] Is someone working with Log4s?

2013-12-28 Thread Hernán Morales Durand
Yes. I just posted because he could be on vacations time and didn't wanted to wait :) Thanks, Hernán 2013/12/27 jtuc...@objektfabrik.de > #currentClassAndMethod is VAST specific. It was added to VAST for log4s, > afaik. > I am quite sure Donald is interested in hearing about your problems with

Re: [Pharo-users] Is someone working with Log4s?

2013-12-28 Thread Hernán Morales Durand
Do not have a copy of VAST or VisualSmalltalk now but this could make it: currentClassAndMethod ^Association key: self class name asString value: thisContext method selector Hernán 2013/12/28 dmacq > What I posted before just gets the name of the pro

Re: [Pharo-users] have a question for morphic Designer in pharo.

2013-12-28 Thread Tobias Pape
On 28.12.2013, at 10:07, Stéphane Ducasse wrote: > I guess that > > #: should be #’:’ That is one way. In this particular case, self property asMutator was the better version, tho. Best -Tobias PS: Just curious, what was the reason to no longer allow #: ? Or, where can I find

Re: [Pharo-users] Is someone working with Log4s?

2013-12-28 Thread dmacq
What I posted before just gets the name of the process, not the name of the method that is currently executing. I don't know how to do that off the top of my head, but I will look into it this weekend. Suggestions welcome. Donald [|] -- View this message in context: http://forum.world.st/Is-

Re: [Pharo-users] Is there any fundamental technical barrier to compiling to JVM byte codes?

2013-12-28 Thread Clément Bera
Main problems to compile Smalltalk to java bytecode: - there's no context in java. This means our implementation of continuations and exceptions is not valid anymore. This also means we cannot have a debugger with edit-and-continue as we have now. - there's no become:, which is used to keep the sys

Re: [Pharo-users] have a question for morphic Designer in pharo.

2013-12-28 Thread Stéphane Ducasse
I guess that #: should be #’:’ On 27 Dec 2013, at 19:44, Stephan Eggermont wrote: > When trying to load Designer in Pharo 3.0 I find uncompilable code in > Animations: > > 'updateCurrentValue: aValue > > self target ifNil: [^ self]. > > self target > perform