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

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

by Benjamin

Oct. 4, 2013

[update 3.0] #30448

by Marcus Denker

Oct. 4, 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… 3 regressions found. KernelTests.Classes.ClassHierarchyTest.testSubclasses Spec.Tests.SpecInterpreterTest.testBuildWidgetForWithSpec Spec.Tests.SpecInterpreterTest.testInterpretASpecModelMorphAssociation

Oct. 4, 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… 3 regressions found. KernelTests.Classes.ClassHierarchyTest.testSubclasses Spec.Tests.SpecInterpreterTest.testBuildWidgetForWithSpec Spec.Tests.SpecInterpreterTest.testInterpretASpecModelMorphAssociation

Oct. 4, 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=li… 3 regressions found. KernelTests.Classes.ClassHierarchyTest.testSubclasses Spec.Tests.SpecInterpreterTest.testBuildWidgetForWithSpec Spec.Tests.SpecInterpreterTest.testInterpretASpecModelMorphAssociation

Oct. 4, 2013

Re: [Pharo-dev] [ANN] Mustache templates

by Tudor Girba

Very nice! Doru On Fri, Oct 4, 2013 at 1:47 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 04 Oct 2013, at 12:58, Norbert Hartl <norbert(a)hartl.name> wrote: > > > > > Am 04.10.2013 um 12:32 schrieb Alexandre Bergel <alexandre.bergel(a)me.com > >: > > > >> What is a mustache template? > >> > > > http://norbert.hartl.name/blog/2013/10/03/mustache-templates-for-smalltalk/ > > Nice! > > > Norbert > > > >> On 4 Oct 2013, at 03:56, Torsten Bergmann <astares(a)gmx.de> wrote: > >> > >>>> I like to announce my smalltalk port of mustache templates. > >>> > >>> Cool! > >>> > >>>> To load it do > >>> > >>> Consider making a copy into MetaRepoForPharo20 or MetaReporForPharo30 > >>> if it is working in these versions. > >>> > >>> That way it is easily accessible via Config browser. > >>> > >>> Thx > >>> T. > >>> > >> > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 4, 2013

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

by Tudor Girba

Hi, On Fri, Oct 4, 2013 at 1:41 PM, Goubier Thierry <thierry.goubier(a)cea.fr>wrote: > Hi Tudor, > > I found your visualisation very interesting, and wondered about one thing > linked to your blog post and if I got it right. > > The visualisation you're showing is able to show, at the single class > level, if a class is more or less regular (i.e. tidy == well designed?) but > you show that it will loose very shortly it's tidy shape if the classes it > joins to are added to the visualisation. And I wondered if this was a > choice on the graph layout algorithm you've choosen, i.e. that maintaining > the tidiness of the class could be done with a different layout algorithm? > Maybe one which has a measure of tidiness of the class at the local level, > and weight it against the position and attraction of its links to the other > components in the application? > My argumentation is that if we look at a class isolated it will have a certain shape, and because we are exposed to this view (the IDE is always showing me only that) all the time we will optimize it such that the shape is tidy. But if we look at the class in the context of its interactions the shape will be less recognizable. The chosen layout is a very simple one, and the goal is not to say whether the structure is good or bad. This is neither good nor bad. It simply argues how steering the architecture has to take these forces into account. In the mean time, I'm slowly discovering we have amazing software > architecture visualisation tools :) They really are amazing :). If you want to get more information about it, you can join the Moose mailing list: http://www.moosetechnology.org/about/contact Would really like to setup a project on that if I get the chance. > What do you mean? What kind of a project? Cheers, Doru Regards, > > Thierry > > Le 03/10/2013 23:34, Tudor Girba a Ã©crit : > >> 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/<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 <http://www.tudorgirba.com> >> >> >> "Every thing has its own flow" >> > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 4, 2013

Re: [Pharo-dev] References to Obsolete classes

by Sebastian Tleye

I agree, If you want to reference an obsolete class after removing the class A, then the source code of the method should also change, and say "AnObsoleteA" instead of "A" if the source code says "A" then i do not like to have a reference to "AnObsoleteA" 2013/10/4 Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> > Hi, > > I run into the same problem last week and endend up in reloading my code > in a new image. I prefer your suggestion. > > Sabine > > > Von meinem iPad gesendet > > Am 04.10.2013 um 12:04 schrieb Noury Bouraqadi <bouraqadi(a)gmail.com>: > > > Hi, > > > > Consider the following scenario: > > 1- create class A > > 2- create class B with a method m that references class A > > 3- delete class A . As a result B>>#m holds a reference to ObsoleteA > > 4- create a new class A. > > > > B>>#m continues to hold a reference to ObsoleteA. This is even more > disturbing, since the source of B>>#m displays A. > > > > Is this behavior desired? If yes, in which situations. because I'd > rather prefer to have B>>#m updated. This can be done, by moving the > association of a removed class (or global in the general case) from the > system dictionary to the Undeclared. > > > > Side note: just noticed that Undeclared is a dictionary. I was expecting > it to be a WeakSet. > > > > Noury > > Ecole des Mines de Douai > > http://car.mines-douai.fr/noury > > -- > > > > > > > > > > Afin de contribuer au respect de l'environnement, > > merci de n'imprimer ce courriel qu'en cas de necessite > > > > Please consider the environment before you print > > > > > > > > > >

Oct. 4, 2013

Re: [Pharo-dev] [ANN] Mustache templates

by Sven Van Caekenberghe

On 04 Oct 2013, at 12:58, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 04.10.2013 um 12:32 schrieb Alexandre Bergel <alexandre.bergel(a)me.com>: > >> What is a mustache template? >> > http://norbert.hartl.name/blog/2013/10/03/mustache-templates-for-smalltalk/ Nice! > Norbert > >> On 4 Oct 2013, at 03:56, Torsten Bergmann <astares(a)gmx.de> wrote: >> >>>> I like to announce my smalltalk port of mustache templates. >>> >>> Cool! >>> >>>> To load it do >>> >>> Consider making a copy into MetaRepoForPharo20 or MetaReporForPharo30 >>> if it is working in these versions. >>> >>> That way it is easily accessible via Config browser. >>> >>> Thx >>> T. >>> >> >

Oct. 4, 2013

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

by Goubier Thierry

Hi Tudor, I found your visualisation very interesting, and wondered about one thing linked to your blog post and if I got it right. The visualisation you're showing is able to show, at the single class level, if a class is more or less regular (i.e. tidy == well designed?) but you show that it will loose very shortly it's tidy shape if the classes it joins to are added to the visualisation. And I wondered if this was a choice on the graph layout algorithm you've choosen, i.e. that maintaining the tidiness of the class could be done with a different layout algorithm? Maybe one which has a measure of tidiness of the class at the local level, and weight it against the position and attraction of its links to the other components in the application? In the mean time, I'm slowly discovering we have amazing software architecture visualisation tools :) Would really like to setup a project on that if I get the chance. Regards, Thierry Le 03/10/2013 23:34, Tudor Girba a Ã©crit : > 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 <http://www.tudorgirba.com> > > "Every thing has its own flow" -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Oct. 4, 2013