December 2013 - Pharo-users

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

by Tobias Pape

On 29.12.2013, at 08:56, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On 28 Dec 2013, at 14:24, Tobias Pape <Das.Linux(a)gmx.de> wrote: > >> >> On 28.12.2013, at 10:07, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> 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 #: ? > > I do not remember but may be this is ansi. > In visualworks #âzork fooâ is the way to have symbol with string with space. Yes, I know the #'anything' form and I am completely ok with it. I just was wondering, because things like #> #< scan directly :) Thanks anyway. Best -Tobias

Dec. 29, 2013

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

by StÃ©phane Ducasse

On 28 Dec 2013, at 14:24, Tobias Pape <Das.Linux(a)gmx.de> wrote: > > On 28.12.2013, at 10:07, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> 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 #: ? I do not remember but may be this is ansi. In visualworks #âzork fooâ is the way to have symbol with string with space. > Or, where can I find the respective discussion, just want to lern. > >> >> On 27 Dec 2013, at 19:44, Stephan Eggermont <stephan(a)stack.nl> 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: (self property, #:) asSymbol >>> with: aValue.' >>> >>> >>> >> >> >

Dec. 29, 2013

Re: [Pharo-users] Pharo code formatting

by 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 Mykhalevych >> >

Dec. 28, 2013

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

by 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 := thisContext. .... 2013/12/28 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> > 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 <dmacq(a)instantiations.com> > >> 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-someone-working-with-Log4s-tp4732633p4732811.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> >

Dec. 28, 2013

Smalltalk Meetup in ZÃ¼rich, January 6th

by jtuchel＠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 developers or to get in touch with old and new friends, this may be your chance. If you'd like to join us, please let me know so that I can reserve a bigger table for the evening. If you want to drop in last minute, please don't hesitate, we're happy to meet you! Joachim [1] http://www.steinfels-zuerich.ch -- ----------------------------------------------------------------------- Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de Fliederweg 1 http://www.objektfabrik.de D-71640 Ludwigsburg http://joachimtuchel.wordpress.com Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1

Dec. 28, 2013

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

by 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 jtuchel(a)objektfabrik.de <jtuchel(a)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 > it. Did you contact him just the other day or some time ago? > > Joachim > > Am 27.12.13 10:53, schrieb HernÃ¡n Morales Durand: > > Because there is a missing method (#currentClassAndMethod) and author >> didn't replied. Maybe I am using it wrong >> >> EsLogManager runForever: '[log4s] >> debugEnabled=''true'' >> quietMode=''false'' >> globalLevel=''All'' >> ;runForever=() >> ;runForever=''75'', ''7'' >> dailyRollingFileAppender=''TestDailyRollingFileAppender'', ''root'', >> ''dallyRollingFileTopOfDay.log'', ''false'', ''All'', '''', ''%-15d [ >> dailyRollingFileAppenderTopOfDay] %-16m'', ''true'', ''topOfDay'' >> ' >> >> Cheers, >> >> HernÃ¡n >> >> > > -- > ----------------------------------------------------------------------- > Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de > Fliederweg 1 http://www.objektfabrik.de > D-71640 Ludwigsburg http://joachimtuchel.wordpress.com > Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 > > >

Dec. 28, 2013

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

by 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 <dmacq(a)instantiations.com> > 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-someone-working-with-Log4s-tp4732633p4732811.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Dec. 28, 2013

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

by Tobias Pape

On 28.12.2013, at 10:07, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> 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 the respective discussion, just want to lern. > > On 27 Dec 2013, at 19:44, Stephan Eggermont <stephan(a)stack.nl> 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: (self property, #:) asSymbol >> with: aValue.' >> >> >> > >

Dec. 28, 2013

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

by 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-someone-working-with-Log4s-tp4732633p4732811.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Dec. 28, 2013

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

by 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. Stef > I was successfull in making Designer start in Pharo 3.0 30659, with some help from > Tobias Pape. Tx tobias. > The following changes were needed (compared to what was needed for Pharo 2.0) > - floodfill2:at: is gone from Form. I replaced it with a simple fillColor: > That it had gone missing was not clear from issue 11570 Do you like method with floodFill23 in their name and not invoked at all :)? > - outsetBy: is deprecated and replaced by expandBy: in a lot of places we also cleaned a lot the logic and added MorphMargin to support polymorphic margins. So may be this is beneficial > - (some symbol or string or something else, #:) asSymbol is replaced by ... asMutator > in a lot of places. > - TranslucentColor is replaced by Color > > <PastedGraphic-1.png> > > TextMorph handleInteraction:forEvent: no longer exists, but gives a different problem in Pharo 2 than in 3 > just replacing it by handleInteraction: does not work. That makes a mess of the selection in > theUiTextLineMorphs in the object inspector. That I have no idea. > > Stephan > >

Dec. 28, 2013