July 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Calendar Events?

by Norbert Hartl

> Am 25.07.2015 um 18:22 schrieb Esteban A. Maringolo <emaringolo(a)gmail.com>: > > This is great. > > A lot of value is not easily discoverable in SmalltakHub!!! > > With the reliability of Pharo images you can have an image running as cron server :) > Of course. I use it to execute things every 10 minutes. Norbert > > > Esteban A. Maringolo > > 2015-07-25 7:03 GMT-03:00 Norbert Hartl <norbert(a)hartl.name>: >> You mean Scheduler? >> >> http://smalltalkhub.com/#!/~TorstenBergmann/Scheduler >> >> Norbert >>> Am 25.07.2015 um 09:24 schrieb stepharo <stepharo(a)free.fr>: >>> >>> Hi >>> >>> I would like to schedule some events automatically. I know that there was a package doing something like that. >>> Any pointers? >>> >>> Stef >

July 25, 2015

Re: [Pharo-dev] QualityAssistant in Pharo5

by Dimitris Chloupis

you say in github that QualityAssistance comes with Pharo5 but I must be having an old image (19-07-15) because I dont see it. Anyway installing it now through conf browser, I love your work, keep it coming. On Thu, Jul 23, 2015 at 6:47 PM Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Dear all, > > QualityAssistant was integrated in Pharo5. You can read more about its > functionality there: > https://github.com/Uko/QualityAssistant#quality-assistant- > If you will spot any bug please let me know, or report here: > https://github.com/Uko/QualityAssistant/issues > > Write a good quality code! > Uko >

July 25, 2015

Re: [Pharo-dev] About nextPutAll: $(

by Max Leske

> On 25 Jul 2015, at 21:31, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > >> On 25 Jul 2015, at 19:40, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> (From my vacations) >> >> Doesn't this solves the problem? >> >> stream << $( << name << $) >> >> It is already there :) > > Yes, indeed: > > String streamContents: [ :out | > out <<$( << 'test-' << 123 << $) ] > > (But it is not perfect, there is still confusion there) I agree. Iâve never liked that operator. Apart from #// and #\\ there are pretty much no selectors that make you guess their meaning. The meaning is in all other cases transported through wording, which I feel very comfortable with. Yes, itâs convenient to write but, as Sven points out, I actually find it less readable. I like Hernanâs idea better. > > We are trying to reduce the String and Stream API, so any addition should be really important/significant. > >> Now I comeback to watch the see... >> >> >> >> >> >> On 25 Jul 2015, at 18:39, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >> >>> In BioSmalltalk I use this pattern a lot: >>> >>> aStream >>> nextPutAll: self name >>> between: $[ -> $]. >>> >>> so yes, that would be a nice inclusion for me :) >>> >>> Cheers, >>> >>> HernÃ¡n >>> >>> >>> >>> >>> 2015-07-24 17:48 GMT-03:00 stepharo <stepharo(a)free.fr>: >>> HI >>> >>> while working on a lecture I saw that we have about 75 cases like: >>> >>> aStream nextPut: $(. >>> .... >>> aStream nextPut: $). >>> >>> >>> >>> storeOn: aStream >>> "Store a description of the elements of the complement rather than self." >>> >>> aStream nextPut: $(. >>> absent storeOn: aStream. >>> aStream nextPut: $); space; nextPutAll: #complement. >>> >>> >>> printElementsOn: aStream >>> aStream nextPut: $(. >>> self size > 100 >>> ifTrue: [aStream nextPutAll: 'size '. >>> self size printOn: aStream] >>> ifFalse: [self keysSortedSafely >>> do: [:key | aStream print: key; >>> nextPutAll: '->'; >>> print: (self at: key); >>> space]]. >>> aStream nextPut: $) >>> >>> we have surroundedBy: aString >>> >>> surroundedBy: aString >>> ^ self class streamContents: [ :s| >>> s nextPutAll: aString. >>> s nextPutAll: self. >>> s nextPutAll: aString ]. >>> >>> But only working on aString. >>> To me it looks like it ia class for having it on stream. >>> >>> What do you think? >>> >>> >>> >>> >>> > >

July 25, 2015

Re: [Pharo-dev] About nextPutAll: $(

by Sven Van Caekenberghe

> On 25 Jul 2015, at 19:40, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > (From my vacations) > > Doesn't this solves the problem? > > stream << $( << name << $) > > It is already there :) Yes, indeed: String streamContents: [ :out | out <<$( << 'test-' << 123 << $) ] (But it is not perfect, there is still confusion there) We are trying to reduce the String and Stream API, so any addition should be really important/significant. > Now I comeback to watch the see... > > > > > > On 25 Jul 2015, at 18:39, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > >> In BioSmalltalk I use this pattern a lot: >> >> aStream >> nextPutAll: self name >> between: $[ -> $]. >> >> so yes, that would be a nice inclusion for me :) >> >> Cheers, >> >> HernÃ¡n >> >> >> >> >> 2015-07-24 17:48 GMT-03:00 stepharo <stepharo(a)free.fr>: >> HI >> >> while working on a lecture I saw that we have about 75 cases like: >> >> aStream nextPut: $(. >> .... >> aStream nextPut: $). >> >> >> >> storeOn: aStream >> "Store a description of the elements of the complement rather than self." >> >> aStream nextPut: $(. >> absent storeOn: aStream. >> aStream nextPut: $); space; nextPutAll: #complement. >> >> >> printElementsOn: aStream >> aStream nextPut: $(. >> self size > 100 >> ifTrue: [aStream nextPutAll: 'size '. >> self size printOn: aStream] >> ifFalse: [self keysSortedSafely >> do: [:key | aStream print: key; >> nextPutAll: '->'; >> print: (self at: key); >> space]]. >> aStream nextPut: $) >> >> we have surroundedBy: aString >> >> surroundedBy: aString >> ^ self class streamContents: [ :s| >> s nextPutAll: aString. >> s nextPutAll: self. >> s nextPutAll: aString ]. >> >> But only working on aString. >> To me it looks like it ia class for having it on stream. >> >> What do you think? >> >> >> >> >>

July 25, 2015

[pharo-project/pharo-core] 7c72fe: 50190

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 7c72fee59c167ca5050045ec380c03cd077962b9 https://github.com/pharo-project/pharo-core/commit/7c72fee59c167ca5050045ec… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-07-25 (Sat, 25 Jul 2015) Changed paths: R AST-Core.package/RBClassReference.class/README.md R AST-Core.package/RBClassReference.class/definition.st M AST-Core.package/extension/CompiledMethod/instance/parseTree.st R Morphic-Core.package/PasteUpMorph.class/instance/wiw support/shouldGetStepsFrom_.st M Morphic-Core.package/WorldState.class/instance/stepping/runLocalStepMethodsIn_.st M OpalCompiler-Core.package/CCompilationContext.class/instance/accessing/parserClass.st M OpalCompiler-Core.package/CompilationContext.class/instance/accessing/parserClass.st A OpalCompiler-Core.package/OCASTClosureAnalyzer.class/instance/variables/changeVariableClass_.st M OpalCompiler-Core.package/OCASTClosureAnalyzer.class/instance/visiting/visitVariableNode_.st M OpalCompiler-Core.package/OpalCompiler.class/instance/public access/parseLiterals_.st M OpalCompiler-Core.package/OpalCompiler.class/instance/public access/parseSelector_.st M OpalCompiler-Tests.package/OCASTCheckerTest.class/instance/testing - simple/testSemanticAnalysisOnNonMethodNode.st A OpalCompiler-Tests.package/OCVariableSpecialisatioTest.class/README.md A OpalCompiler-Tests.package/OCVariableSpecialisatioTest.class/definition.st A OpalCompiler-Tests.package/OCVariableSpecialisatioTest.class/instance/tests/testVarTemp.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50189.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50190.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50189.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50190.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50190 16025 clean up: shouldGetStepsFrom: https://pharo.fogbugz.com/f/cases/16025 10916 RBParser missparse some temporary variables https://pharo.fogbugz.com/f/cases/10916 16023 RBClassReference can be removed https://pharo.fogbugz.com/f/cases/16023 http://files.pharo.org/image/50/50190.zip

July 25, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50190 Home: https://github.com/pharo-project/pharo-core

July 25, 2015

Re: [Pharo-dev] Calendar Events?

by stepharo

Clearly not. But you see when there is not even a "forgot your password".... Stef > This is great. > > A lot of value is not easily discoverable in SmalltakHub!!! > > With the reliability of Pharo images you can have an image running as > cron server :) > > > > Esteban A. Maringolo > > 2015-07-25 7:03 GMT-03:00 Norbert Hartl <norbert(a)hartl.name > <mailto:norbert@hartl.name>>: > > You mean Scheduler? > > http://smalltalkhub.com/#!/~TorstenBergmann/Scheduler > <http://smalltalkhub.com/#%21/%7ETorstenBergmann/Scheduler> > > Norbert > Am 25.07.2015 um 09:24 schrieb stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > >> Hi >> >> I would like to schedule some events automatically. I know that >> there was a package doing something like that. >> Any pointers? >> >> Stef >> >

July 25, 2015

Re: [Pharo-dev] About nextPutAll: $(

by Esteban Lorenzano

(From my vacations) Doesn't this solves the problem? stream << $( << name << $) It is already there :) Now I comeback to watch the see... > On 25 Jul 2015, at 18:39, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > In BioSmalltalk I use this pattern a lot: > > aStream > nextPutAll: self name > between: $[ -> $]. > > so yes, that would be a nice inclusion for me :) > > Cheers, > > HernÃ¡n > > > > > 2015-07-24 17:48 GMT-03:00 stepharo <stepharo(a)free.fr>: >> HI >> >> while working on a lecture I saw that we have about 75 cases like: >> >> aStream nextPut: $(. >> .... >> aStream nextPut: $). >> >> >> >> storeOn: aStream >> "Store a description of the elements of the complement rather than self." >> >> aStream nextPut: $(. >> absent storeOn: aStream. >> aStream nextPut: $); space; nextPutAll: #complement. >> >> >> printElementsOn: aStream >> aStream nextPut: $(. >> self size > 100 >> ifTrue: [aStream nextPutAll: 'size '. >> self size printOn: aStream] >> ifFalse: [self keysSortedSafely >> do: [:key | aStream print: key; >> nextPutAll: '->'; >> print: (self at: key); >> space]]. >> aStream nextPut: $) >> >> we have surroundedBy: aString >> >> surroundedBy: aString >> ^ self class streamContents: [ :s| >> s nextPutAll: aString. >> s nextPutAll: self. >> s nextPutAll: aString ]. >> >> But only working on aString. >> To me it looks like it ia class for having it on stream. >> >> What do you think? >

July 25, 2015

Re: [Pharo-dev] About nextPutAll: $(

by HernÃ¡n Morales Durand

In BioSmalltalk I use this pattern a lot: aStream nextPutAll: self name between: $[ -> $]. so yes, that would be a nice inclusion for me :) Cheers, HernÃ¡n 2015-07-24 17:48 GMT-03:00 stepharo <stepharo(a)free.fr>: > HI > > while working on a lecture I saw that we have about 75 cases like: > > aStream nextPut: $(. > .... > aStream nextPut: $). > > > > storeOn: aStream > "Store a description of the elements of the complement rather than > self." > > aStream nextPut: $(. > absent storeOn: aStream. > aStream nextPut: $); space; nextPutAll: #complement. > > > printElementsOn: aStream > aStream nextPut: $(. > self size > 100 > ifTrue: [aStream nextPutAll: 'size '. > self size printOn: aStream] > ifFalse: [self keysSortedSafely > do: [:key | aStream print: key; > nextPutAll: '->'; > print: (self at: key); > space]]. > aStream nextPut: $) > > we have surroundedBy: aString > > surroundedBy: aString > ^ self class streamContents: [ :s| > s nextPutAll: aString. > s nextPutAll: self. > s nextPutAll: aString ]. > > But only working on aString. > To me it looks like it ia class for having it on stream. > > What do you think? > > > > >

July 25, 2015

Re: [Pharo-dev] Calendar Events?

by Esteban A. Maringolo

This is great. A lot of value is not easily discoverable in SmalltakHub!!! With the reliability of Pharo images you can have an image running as cron server :) Esteban A. Maringolo 2015-07-25 7:03 GMT-03:00 Norbert Hartl <norbert(a)hartl.name>: > You mean Scheduler? > > http://smalltalkhub.com/#!/~TorstenBergmann/Scheduler > > Norbert > Am 25.07.2015 um 09:24 schrieb stepharo <stepharo(a)free.fr>: > > Hi > > I would like to schedule some events automatically. I know that there was > a package doing something like that. > Any pointers? > > Stef > >

July 25, 2015