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

Re: [Pharo-dev] Selecting a package in the Monticello browser

by Benjamin

Nope :( Ben On 03 Nov 2013, at 22:52, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Strange. Pharo 2.0 does not seem to have the replication of repository instances problem. Any idea what introduced this? > > Doru > > > On Sun, Nov 3, 2013 at 10:49 PM, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > The thing is you use to have one instance of the same MCRepository per package. > By example, the Pharo repository was in fact #{packageNumber} instances. > > So the change you make on one (by example, string your password) was not reflected to the others. > And it seems that during the fix of this, this issue was introduced. > > (I think the easy solution taken was to have the same repositories for everything). > Itâs indeed kind of a paint o deal with, but a smaller one that it use to be :) > > Definitely itâs a bug, not a feature :) > We should wait tip Guillermoâs answer since he was the one fixing this painful behaviour (2 sprints ago) > > Ben > > On 03 Nov 2013, at 22:44, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> I do not understand what the password has to do with showing only the relevant repositories for a selected package. Could you explain? >> >> Doru >> >> >> On Nov 3, 2013, at 10:39 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >> >>> The idea was that repositories were shared among packages. >>> >>> Otherwise, you have to type your password a billion times >>> >>> Ben >>> >>> On 03 Nov 2013, at 21:49, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>>> Indeed, I wanted to raise this issue as well. The Monticello browser is a rather terrible interface, but at least the scoping of repositories was useful. Is the change intentional, or is it a bug? >>>> >>>> Doru >>>> >>>> >>>> On Sun, Nov 3, 2013 at 9:46 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>> Hi! >>>> >>>> Before, when one selects a package (left list), then only the set of relevant repositories are displayed (right list). This is now not the case anymore. I think I have seen somewhere a MC package is not associated to a repository anymore. What is the idea behind this? I find this rather convenient... >>>> >>>> Alexandre >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Every thing has its own flow" >>> >> >> -- >> www.tudorgirba.com >> >> "What is more important: To be happy, or to make happy?" >> >> > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Nov. 3, 2013

Re: [Pharo-dev] Selecting a package in the Monticello browser

by Tudor Girba

Strange. Pharo 2.0 does not seem to have the replication of repository instances problem. Any idea what introduced this? Doru On Sun, Nov 3, 2013 at 10:49 PM, Benjamin < Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > The thing is you use to have one instance of the same MCRepository per > package. > By example, the Pharo repository was in fact #{packageNumber} instances. > > So the change you make on one (by example, string your password) was not > reflected to the others. > And it seems that during the fix of this, this issue was introduced. > > (I think the easy solution taken was to have the same repositories for > everything). > Itâs indeed kind of a paint o deal with, but a smaller one that it use to > be :) > > Definitely itâs a bug, not a feature :) > We should wait tip Guillermoâs answer since he was the one fixing this > painful behaviour (2 sprints ago) > > Ben > > On 03 Nov 2013, at 22:44, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > I do not understand what the password has to do with showing only the > relevant repositories for a selected package. Could you explain? > > Doru > > > On Nov 3, 2013, at 10:39 PM, Benjamin < > benjamin.vanryseghem.pharo(a)gmail.com> wrote: > > The idea was that repositories were shared among packages. > > Otherwise, you have to type your password a billion times > > Ben > > On 03 Nov 2013, at 21:49, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Indeed, I wanted to raise this issue as well. The Monticello browser is a > rather terrible interface, but at least the scoping of repositories was > useful. Is the change intentional, or is it a bug? > > Doru > > > On Sun, Nov 3, 2013 at 9:46 PM, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > Hi! > > Before, when one selects a package (left list), then only the set of > relevant repositories are displayed (right list). This is now not the case > anymore. I think I have seen somewhere a MC package is not associated to a > repository anymore. What is the idea behind this? I find this rather > convenient... > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > > -- > www.tudorgirba.com > > "What is more important: To be happy, or to make happy?" > > > > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 3, 2013

Re: [Pharo-dev] Selecting a package in the Monticello browser

by Benjamin

The thing is you use to have one instance of the same MCRepository per package. By example, the Pharo repository was in fact #{packageNumber} instances. So the change you make on one (by example, string your password) was not reflected to the others. And it seems that during the fix of this, this issue was introduced. (I think the easy solution taken was to have the same repositories for everything). Itâs indeed kind of a paint o deal with, but a smaller one that it use to be :) Definitely itâs a bug, not a feature :) We should wait tip Guillermoâs answer since he was the one fixing this painful behaviour (2 sprints ago) Ben On 03 Nov 2013, at 22:44, Tudor Girba <tudor(a)tudorgirba.com> wrote: > I do not understand what the password has to do with showing only the relevant repositories for a selected package. Could you explain? > > Doru > > > On Nov 3, 2013, at 10:39 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > >> The idea was that repositories were shared among packages. >> >> Otherwise, you have to type your password a billion times >> >> Ben >> >> On 03 Nov 2013, at 21:49, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >>> Indeed, I wanted to raise this issue as well. The Monticello browser is a rather terrible interface, but at least the scoping of repositories was useful. Is the change intentional, or is it a bug? >>> >>> Doru >>> >>> >>> On Sun, Nov 3, 2013 at 9:46 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>> Hi! >>> >>> Before, when one selects a package (left list), then only the set of relevant repositories are displayed (right list). This is now not the case anymore. I think I have seen somewhere a MC package is not associated to a repository anymore. What is the idea behind this? I find this rather convenient... >>> >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >> > > -- > www.tudorgirba.com > > "What is more important: To be happy, or to make happy?" > >

Nov. 3, 2013

Re: [Pharo-dev] Selecting a package in the Monticello browser

by Tudor Girba

I do not understand what the password has to do with showing only the relevant repositories for a selected package. Could you explain? Doru On Nov 3, 2013, at 10:39 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > The idea was that repositories were shared among packages. > > Otherwise, you have to type your password a billion times > > Ben > > On 03 Nov 2013, at 21:49, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Indeed, I wanted to raise this issue as well. The Monticello browser is a rather terrible interface, but at least the scoping of repositories was useful. Is the change intentional, or is it a bug? >> >> Doru >> >> >> On Sun, Nov 3, 2013 at 9:46 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> Hi! >> >> Before, when one selects a package (left list), then only the set of relevant repositories are displayed (right list). This is now not the case anymore. I think I have seen somewhere a MC package is not associated to a repository anymore. What is the idea behind this? I find this rather convenient... >> >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" > -- www.tudorgirba.com "What is more important: To be happy, or to make happy?"

Nov. 3, 2013

Re: [Pharo-dev] Selecting a package in the Monticello browser

by Benjamin

The idea was that repositories were shared among packages. Otherwise, you have to type your password a billion times Ben On 03 Nov 2013, at 21:49, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Indeed, I wanted to raise this issue as well. The Monticello browser is a rather terrible interface, but at least the scoping of repositories was useful. Is the change intentional, or is it a bug? > > Doru > > > On Sun, Nov 3, 2013 at 9:46 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > Before, when one selects a package (left list), then only the set of relevant repositories are displayed (right list). This is now not the case anymore. I think I have seen somewhere a MC package is not associated to a repository anymore. What is the idea behind this? I find this rather convenient... > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Nov. 3, 2013

Re: [Pharo-dev] Selecting a package in the Monticello browser

by Tudor Girba

Indeed, I wanted to raise this issue as well. The Monticello browser is a rather terrible interface, but at least the scoping of repositories was useful. Is the change intentional, or is it a bug? Doru On Sun, Nov 3, 2013 at 9:46 PM, Alexandre Bergel <alexandre.bergel(a)me.com>wrote: > Hi! > > Before, when one selects a package (left list), then only the set of > relevant repositories are displayed (right list). This is now not the case > anymore. I think I have seen somewhere a MC package is not associated to a > repository anymore. What is the idea behind this? I find this rather > convenient... > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 3, 2013

Re: [Pharo-dev] Traits question

by Tudor Girba

The way you use Traits on the class side is to define class-side methods in the Trait. Doru On Sun, Nov 3, 2013 at 9:39 PM, phil(a)highoctane.be <phil(a)highoctane.be>wrote: > I have a TXXLog Trait where I have defined the following methods instance > side. > > info: aString > warn: aString > debug: aString > error: aString > > This worked well with my services where I had XXService uses: TXXLog > > services have a default class side method that return the Default instance. > > Now, I had a class where I wanted to use the trait from the class side as > well. > > But then, after Googling a bit, I found that there was the instance side > trait and the class side trait. > > What is the best practice when one wants to use, say, the TXXLog trait on > the class side? > > For my particular case, I put the info: warn: ... methods on the class > side of my trait and the instance side one do a self class info: aString > etc. > > Is that the right way to do it? > > Phil > > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 3, 2013

Selecting a package in the Monticello browser

by Alexandre Bergel

Hi! Before, when one selects a package (left list), then only the set of relevant repositories are displayed (right list). This is now not the case anymore. I think I have seen somewhere a MC package is not associated to a repository anymore. What is the idea behind this? I find this rather convenient... Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 3, 2013

Re: [Pharo-dev] Quit is not asking for a confirmation anymore?

by Alexandre Bergel

Apparently, this is related to the user permission or something Alexandre On Nov 3, 2013, at 2:15 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Nov 3, 2013, at 5:32 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > >> I opened a bug entry: >> >> https://pharo.fogbugz.com/f/cases/12060/The-Quit-menu-entry-is-not-asking-f… >> >> Would be great to discuss about this. > > We should get warned. There is no discussion :) > > >> >> Alexandre >> >> On Nov 3, 2013, at 1:19 PM, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >> >>> Better not miss the menu option... >>> >>> >>> >>> >>> >>> >>> On Sun, Nov 3, 2013 at 3:36 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> Really a bug? And I was liking it :) >>> >>> Doru >>> >>> On Sun, Nov 3, 2013 at 2:12 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> no, is a bug. >>> I already reported also, but maybe a bug report would help :) >>> >>> >>> On Sun, Nov 3, 2013 at 10:09 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>> Hi! >>> >>> When I quit Pharo 3.0, no confirmation is asked anymore? Is this really intended? >>> >>> Cheers, >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 3, 2013

Traits question

by phil＠highoctane.be

I have a TXXLog Trait where I have defined the following methods instance side. info: aString warn: aString debug: aString error: aString This worked well with my services where I had XXService uses: TXXLog services have a default class side method that return the Default instance. Now, I had a class where I wanted to use the trait from the class side as well. But then, after Googling a bit, I found that there was the instance side trait and the class side trait. What is the best practice when one wants to use, say, the TXXLog trait on the class side? For my particular case, I put the info: warn: ... methods on the class side of my trait and the instance side one do a self class info: aString etc. Is that the right way to do it? Phil

Nov. 3, 2013