October 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [update 2.0] #20623

by Paul DeBruicker

Thanks Esteban EstebanLM wrote > 20623 > ----- > > 11639 Backport Pharo2.0: Memory leak when using weak announcements with > blocks > https://pharo.fogbugz.com/f/cases/11639 > > (pass 2/2) > > Diff information: > http://ss3.gemstone.com/ss/Pharo20/Collections-Weak-EstebanLorenzano.72.diff > http://ss3.gemstone.com/ss/Pharo20/Announcements-Core-EstebanLorenzano.41.d… -- View this message in context: http://forum.world.st/update-2-0-20623-tp4711941p4712344.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 3, 2013

Re: [Pharo-dev] MNU SpecLayout>>hasSlots

by Camillo Bruni

and resolved... On 2013-10-03, at 22:24, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > btc wrote >> a full bug report > > https://pharo.fogbugz.com/f/cases/11766/MNU-SpecLayout-hasSlots > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/MNU-SpecLayout-hasSlots-tp4712020p4712306.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Oct. 3, 2013

Re: [Pharo-dev] [ann] system attraction view

by Alexandre Bergel

I think this is the nicest looking visualization made so far with Roassal. Consider it for the next Roassal contest next year. Amazing job! Truly beautiful. Alexandre On Oct 3, 2013, at 6:34 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I built a new visualization that has two goals: > > 1. show how the architecture of a system is fluid rather than rigid. > 2. look good and serve as advertisement device for Moose, Roassal and Pharo. > > A description of mainly point 1. can be found here: > http://www.humane-assessment.com/blog/system-attraction/ > > I already used it as a splash screen for a couple of presentations, and it catches the eye. > > The code can be found in Moose, in a separate tiny FAMIXSystemAttraction class. You can invoke it on any class group (note: it can take a long time to render for large groups). > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Oct. 3, 2013

[ann] system attraction view

by Tudor Girba

Hi, I built a new visualization that has two goals: 1. show how the architecture of a system is fluid rather than rigid. 2. look good and serve as advertisement device for Moose, Roassal and Pharo. A description of mainly point 1. can be found here: http://www.humane-assessment.com/blog/system-attraction/ I already used it as a splash screen for a couple of presentations, and it catches the eye. The code can be found in Moose, in a separate tiny FAMIXSystemAttraction class. You can invoke it on any class group (note: it can take a long time to render for large groups). Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

Oct. 3, 2013

Re: [Pharo-dev] MNU SpecLayout>>hasSlots

by Sean P. DeNigris

btc wrote > a full bug report https://pharo.fogbugz.com/f/cases/11766/MNU-SpecLayout-hasSlots ----- Cheers, Sean -- View this message in context: http://forum.world.st/MNU-SpecLayout-hasSlots-tp4712020p4712306.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 3, 2013

[ANN] Mustache templates

by Norbert Hartl

I like to announce my smalltalk port of mustache templates. Mustache is a popular templating engine that is supported in many programming languages. I know at least that is quite common to be used in javascript but see at the languages it supported yourself [1]. A basic usage is something like (just paste it to workspace after loading Mustache): --- templateString := 'Hello {{name}}, this is {{templatingEngine}} for {{recipient}}. {{# cheerUp }} Have fun! {{/ cheerUp }}'. context := { 'name' -> 'pharo community'. 'templatingEngine' -> 'mustache'. 'recipient' -> 'you'. 'cheerUp' -> true } asDictionary. templateString asMustacheTemplate value: context --- Context objects can be Dictionaries or regular objects. It is also easy to feed via json e.g. using NeoJSON templateString asMustacheTemplate value: (NeoJSONReader fromString: â¦) I wrote a blog article about it and the usage in smaltlalk on my blog [2]. The code I have just released on smalltalkhub [3]. Documentation about the syntax to use is available under [4]. To load it do Gofer it smalltalkhubUser: 'NorbertHartl' project: 'Mustache'; configurationOf: 'Mustache'; loadStable. The code is not very old so there might be bugs (this is supposed to be the standard disclaimer). If you find something not working as expected just drop me a note. The engine produces at the moment more whitespaces than you can see in the examples. I need to figure out the rule first and will release a new version. Nevertheless I consider it useful by now. But you decide and hopefully give me feedback. Norbert [1] http://mustache.github.io/ [2] http://norbert.hartl.name/blog/2013/10/03/mustache-templates-for-smalltalk/ [3] http://smalltalkhub.com/#!/~NorbertHartl/Mustache [4] http://mustache.github.io/mustache.5.html

Oct. 3, 2013

Re: [Pharo-dev] [update 3.0] #30444

by Marcus Denker

On Oct 3, 2013, at 9:19 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > marcus for the critics next time please keep them else we will not be able to decide if we used them or not. > This is not three little classes that will change something. Especially when they are part of a large library. > But we don't use them. > Stef > > > >> 30444 >> ----- >> >> 11762 update #cleanUpForProduction >> https://pharo.fogbugz.com/f/cases/11762 >> >> 11764 unload Refactoring-Spelling >> https://pharo.fogbugz.com/f/cases/11764 >> >> 11763 clean up Refactoring-Critics-Unused >> https://pharo.fogbugz.com/f/cases/11763 >> >> 11761 class StrikeFontFixer is undocumented and the only users not called >> https://pharo.fogbugz.com/f/cases/11761 >> >> >> Diff information: >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1288.diff >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Critics-MarcusDen… >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Graphics-Fonts-MarcusDenker.8… >> > >

Oct. 3, 2013

Re: [Pharo-dev] [update 3.0] #30444

by StÃ©phane Ducasse

marcus for the critics next time please keep them else we will not be able to decide if we used them or not. This is not three little classes that will change something. Especially when they are part of a large library. Stef > 30444 > ----- > > 11762 update #cleanUpForProduction > https://pharo.fogbugz.com/f/cases/11762 > > 11764 unload Refactoring-Spelling > https://pharo.fogbugz.com/f/cases/11764 > > 11763 clean up Refactoring-Critics-Unused > https://pharo.fogbugz.com/f/cases/11763 > > 11761 class StrikeFontFixer is undocumented and the only users not called > https://pharo.fogbugz.com/f/cases/11761 > > > Diff information: > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1288.diff > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Critics-MarcusDen… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Graphics-Fonts-MarcusDenker.8… >

Oct. 3, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=ma… 4 regressions found. Manifest.Tests.SmalllintManifestCheckerTest.testCriticsOf Manifest.Tests.SmalllintManifestCheckerTest.testIsFalsePositive Manifest.Tests.SmalllintManifestCheckerTest.testIsToDo Manifest.Tests.SmalllintManifestCheckerTest.testToDoOf

Oct. 3, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=wi… 4 regressions found. Manifest.Tests.SmalllintManifestCheckerTest.testCriticsOf Manifest.Tests.SmalllintManifestCheckerTest.testIsFalsePositive Manifest.Tests.SmalllintManifestCheckerTest.testIsToDo Manifest.Tests.SmalllintManifestCheckerTest.testToDoOf

Oct. 3, 2013