March 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] diff'ing with metacello

by Ben Coman

Can you provide a concrete case of two versions you want to compare? cheers -ben On Tue, Mar 28, 2017 at 8:51 PM, Siemen Baader <siemenbaader(a)gmail.com> wrote: > > > Sent from my iPhone > > On 28/03/2017, at 13.52, Ben Coman <btc(a)openinworld.com> wrote: > >> Do you mean the difference between two "ConfigurationXXX....mcz" files? > > I didn't know there were 'ConfigurationOfX.mcz' files. What do they contain? > > What I want to see is what code has changed between two releases. In Git I would do it with a diff of the two releases' checksums. In other words, I want to see for releases described with metacello what the > Monticello browser can show us for versions of packages. Does this make sense? It seems like a very common use case to me, people must be doing it all the time, or...? > > cheers, > Siemen > > >> As a workaround, perhaps load one and then from Monticello, >> "start" to merge the other from Monticello and you will see a diff between them. >> >> cheers -ben >> >> On Tue, Mar 28, 2017 at 7:06 PM, Siemen Baader <siemenbaader(a)gmail.com> wrote: >>> Hi all, >>> >>> is there a tool to diff two Metacello versions with different baselines? I >>> tried MetacelloBrowser >>> (http://www.squeaksource.com/@6xz1bzmNF75EduBA/vZ263dVA) but it does not >>> install on Pharo 5.0. >>> >>> I need it to see what has changed when I install a new release of PharoJS >>> and to bisect in search for regressions. >>> >>> thanks, >>> Siemen >> >

March 28, 2017

Re: [Pharo-users] diff'ing with metacello

by Siemen Baader

Sent from my iPhone On 28/03/2017, at 13.52, Ben Coman <btc(a)openinworld.com> wrote: > Do you mean the difference between two "ConfigurationXXX....mcz" files? I didn't know there were 'ConfigurationOfX.mcz' files. What do they contain? What I want to see is what code has changed between two releases. In Git I would do it with a diff of the two releases' checksums. In other words, I want to see for releases described with metacello what the Monticello browser can show us for versions of packages. Does this make sense? It seems like a very common use case to me, people must be doing it all the time, or...? cheers, Siemen > As a workaround, perhaps load one and then from Monticello, > "start" to merge the other from Monticello and you will see a diff between them. > > cheers -ben > > On Tue, Mar 28, 2017 at 7:06 PM, Siemen Baader <siemenbaader(a)gmail.com> wrote: >> Hi all, >> >> is there a tool to diff two Metacello versions with different baselines? I >> tried MetacelloBrowser >> (http://www.squeaksource.com/@6xz1bzmNF75EduBA/vZ263dVA) but it does not >> install on Pharo 5.0. >> >> I need it to see what has changed when I install a new release of PharoJS >> and to bisect in search for regressions. >> >> thanks, >> Siemen >

March 28, 2017

Re: [Pharo-users] diff'ing with metacello

by Ben Coman

Do you mean the difference between two "ConfigurationXXX....mcz" files? As a workaround, perhaps load one and then from Monticello, "start" to merge the other from Monticello and you will see a diff between them. cheers -ben On Tue, Mar 28, 2017 at 7:06 PM, Siemen Baader <siemenbaader(a)gmail.com> wrote: > Hi all, > > is there a tool to diff two Metacello versions with different baselines? I > tried MetacelloBrowser > (http://www.squeaksource.com/@6xz1bzmNF75EduBA/vZ263dVA) but it does not > install on Pharo 5.0. > > I need it to see what has changed when I install a new release of PharoJS > and to bisect in search for regressions. > > thanks, > Siemen

March 28, 2017

meaning of orange losange beside a protocol

by Ahdach Mohamed

Hi, Whats the meaning of an orange losange at the left of a protocol, actually initialization Is there a list of the meanings of the icons one sees at the left of packages, classes, protocols and methods? Mohamed

March 28, 2017

diff'ing with metacello

by Siemen Baader

Hi all, is there a tool to diff two Metacello versions with different baselines? I tried MetacelloBrowser ( http://www.squeaksource.com/@6xz1bzmNF75EduBA/vZ263dVA) but it does not install on Pharo 5.0. I need it to see what has changed when I install a new release of PharoJS and to bisect in search for regressions. thanks, Siemen

March 28, 2017

Re: [Pharo-users] SSL Exception on running the first example of Live Object Programming mooc

by Sven Van Caekenberghe

> On 28 Mar 2017, at 11:36, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > I hope your journey will be cool! > >> On 28 Mar 2017, at 11:28, Ahdach Mohamed <ahdach(a)gmail.com> wrote: >> >> Hi All, >> >> Newbie to Pharo (48 hours). I'm going through the excellent mooc by Stephane D. and his team. >> >> I've installed Pharo and run into an error when trying to run my second expression. >> >> Here it is: >> >> (ZnEasy getPng:'http://pharo.org/web/files/pharo.png') asMorph openInWindow >> >> And I have the following error: "SSL Exception: connect failed". >> >> What am I missing? >> > > there is nothing missing. > Currently we have a problem in our web site (that uses a non-supported encrypt method), we are going to fix it soon, but for now please use this alternative: > > (ZnEasy getPng:'http://files.pharo.org/media/logo/logo-flat-small.png') asMorph openInWindow. Or this alternative (lose the 'web' part): (ZnEasy getPng:'http://pharo.org/files/pharo.png') asMorph openInWindow > cheers! > Esteban > >> Mohamed >>

March 28, 2017

Re: [Pharo-users] loading petitParser

by Stephane Ducasse

I will update the book because this pointer does not work either http://www.themoosebook.org/book/internals/petit-parser On Tue, Mar 28, 2017 at 11:48 AM, Christophe Demarey < christophe.demarey(a)inria.fr> wrote: > yes because the current way to load projects is: > > Metacello new > configuration: 'PetitParser'; > smalltalkhubUser: 'Moose' project: 'PetitParser'; > load. > > if you want to load a specific group, you should use the #load: message > (current groups are Core, Tests, Parser and ParserIDE). Default will load > all. > > Le 28 mars 2017 Ã 10:02, Stephane Ducasse <stepharo.self(a)gmail.com> a > Ã©crit : > > Hi > > in the deep into pharo book it is written > > Gofer new > > smalltalkhubUser: 'Moose' project: 'PetitParser'; package: > 'ConfigurationOfPetitParser'; > > load. > > (Smalltalk at: #ConfigurationOfPetitParser) perform: #loadDefault > > > But this is not correct. There is no loadDefault. > > Should I change it? > > > Stef > > >

March 28, 2017

Re: [Pharo-users] Smacc debugger

by Thierry Goubier

Le 28/03/2017 Ã 11:50, Stephane Ducasse a Ã©crit : > OK > I loaded Smacc from github as mentioned by thierry. > > Metacello new > baseline: 'SmaCC'; > repository: 'github://ThierryGoubier/SmaCC'; > load > > Are there two configurationOfSmacc? > May be we should only have one no? > > I have the impression that even thierry and jason working heavily with > Smacc do not know that. I know there are two configurations of SmaCC. I told you, probably two days ago, that some syntax extensions for grammars may only be supported on one of those. > And we should not force them to use Moose. At least we do not have to win > anything with it. Thierry > Stef > > On Mon, Mar 27, 2017 at 6:31 PM, Tudor Girba <tudor(a)tudorgirba.com > <mailto:tudor@tudorgirba.com>> wrote: > > They come with the ConfigurationOfSmaCC which is already in the > Moose image. > > Doru > > > > On Mar 27, 2017, at 4:52 PM, Stephane Ducasse > <stepharo.self(a)gmail.com <mailto:stepharo.self@gmail.com>> wrote: > > > > Hi > > > > where can I load the Smacc gt extension and debugger extensions? > > > > Stef > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > www.feenk.com <http://www.feenk.com> > > "Speaking louder won't make the point worthier." > > >

March 28, 2017

Re: [Pharo-users] Smacc debugger

by Stephane Ducasse

OK I loaded Smacc from github as mentioned by thierry. Metacello new baseline: 'SmaCC'; repository: 'github://ThierryGoubier/SmaCC'; load Are there two configurationOfSmacc? May be we should only have one no? I have the impression that even thierry and jason working heavily with Smacc do not know that. And we should not force them to use Moose. At least we do not have to win anything with it. Stef On Mon, Mar 27, 2017 at 6:31 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > They come with the ConfigurationOfSmaCC which is already in the Moose > image. > > Doru > > > > On Mar 27, 2017, at 4:52 PM, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > > > > Hi > > > > where can I load the Smacc gt extension and debugger extensions? > > > > Stef > > -- > www.tudorgirba.com > www.feenk.com > > "Speaking louder won't make the point worthier." > > >

March 28, 2017

Re: [Pharo-users] loading petitParser

by Christophe Demarey

yes because the current way to load projects is: Metacello new configuration: 'PetitParser'; smalltalkhubUser: 'Moose' project: 'PetitParser'; load. if you want to load a specific group, you should use the #load: message (current groups are Core, Tests, Parser and ParserIDE). Default will load all. > Le 28 mars 2017 Ã 10:02, Stephane Ducasse <stepharo.self(a)gmail.com> a Ã©crit : > > Hi > > in the deep into pharo book it is written > > Gofer new > > smalltalkhubUser: 'Moose' project: 'PetitParser'; package: 'ConfigurationOfPetitParser'; > > load. > > (Smalltalk at: #ConfigurationOfPetitParser) perform: #loadDefault > > > > But this is not correct. There is no loadDefault. > > Should I change it? > > > > Stef >

March 28, 2017