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

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

by Mariano Martinez Peck

On Thu, Nov 7, 2013 at 1:12 PM, Camillo Bruni <camillobruni(a)gmail.com>wrote: > I do not like it either... but if there are more than one repository group > (like before 1 per package) we have to make sure the repositories are > unique > per URL, otherwise you end up with different repositories which look the > same > but for instance do not have the same credentials, which was the problem we > had back then. > Cami, Say I have 2 different packages. Both have the PharoInbox and Pharo20 as repos. If I edit and add a password to the ones of the package1 and then I go to package2, the password is kept. And this is the case even for 2.0. So maybe you are saying a different scenario? > > I remember that whenever we added a SLICE the inbox repository got > duplicated > causing qutie a bit of confusion, since you had to re-enter your password > twice > or more... > > > On 2013-11-07, at 17:09, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > > So we were discussing this here in the sprint. People say this is a > feature. To be this is a bug. > > > > The change is in > > > > repositoryGroup > > ^ workingCopy > > ifNil: [MCRepositoryGroup default] > > ifNotNil: [workingCopy repositoryGroup] > > > > which right now it is as > > > > repositoryGroup > > ^ MCRepositoryGroup default > > > > So we will probably put a setting for the moment because we cannot agree. > > > > Cheers, > > > > > > > > > > On Sun, Nov 3, 2013 at 7:48 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > > Ben > > > > this is good to share repositories :) > > I got burned so many times while integrating changes back in Squeak 3.9 > that this is the first things I did for the scriptLoader. > > Now I do not see why when we select a package we should see the ones > that are not associated with the package. > > > > Stef > > > > On 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) > > > > We can try to do something during the sprint thursday. > > > > > >> 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?" > >>> > >>> > >> > > > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

Nov. 7, 2013

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

by Camillo Bruni

I do not like it either... but if there are more than one repository group (like before 1 per package) we have to make sure the repositories are unique per URL, otherwise you end up with different repositories which look the same but for instance do not have the same credentials, which was the problem we had back then. I remember that whenever we added a SLICE the inbox repository got duplicated causing qutie a bit of confusion, since you had to re-enter your password twice or more... On 2013-11-07, at 17:09, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > So we were discussing this here in the sprint. People say this is a feature. To be this is a bug. > > The change is in > > repositoryGroup > ^ workingCopy > ifNil: [MCRepositoryGroup default] > ifNotNil: [workingCopy repositoryGroup] > > which right now it is as > > repositoryGroup > ^ MCRepositoryGroup default > > So we will probably put a setting for the moment because we cannot agree. > > Cheers, > > > > > On Sun, Nov 3, 2013 at 7:48 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Ben > > this is good to share repositories :) > I got burned so many times while integrating changes back in Squeak 3.9 that this is the first things I did for the scriptLoader. > Now I do not see why when we select a package we should see the ones that are not associated with the package. > > Stef > > On 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) > > We can try to do something during the sprint thursday. > > >> 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?" >>> >>> >> > > > > > -- > Mariano > http://marianopeck.wordpress.com

Nov. 7, 2013

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

by Mariano Martinez Peck

So we were discussing this here in the sprint. People say this is a feature. To be this is a bug. The change is in repositoryGroup ^ workingCopy ifNil: [MCRepositoryGroup default] ifNotNil: [workingCopy repositoryGroup] which right now it is as repositoryGroup ^ MCRepositoryGroup default So we will probably put a setting for the moment because we cannot agree. Cheers, On Sun, Nov 3, 2013 at 7:48 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > Ben > > this is good to share repositories :) > I got burned so many times while integrating changes back in Squeak 3.9 > that this is the first things I did for the scriptLoader. > Now I do not see why when we select a package we should see the ones that > are not associated with the package. > > Stef > > On 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) > > > We can try to do something during the sprint thursday. > > > 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?" > > > > > -- Mariano http://marianopeck.wordpress.com

Nov. 7, 2013

[pharo-project/pharo-core] 86fb0e: 30551

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 86fb0e5ae8999d15ddc7fa7f895f6d8aad6e6a2f https://github.com/pharo-project/pharo-core/commit/86fb0e5ae8999d15ddc7fa7f… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-11-07 (Thu, 07 Nov 2013) Changed paths: A HudsonBuildTools20.package/HDTestReport.class/instance/private/beginTestCase_runBlock_.st R HudsonBuildTools20.package/HDTestReport.class/instance/private/beginTestCase_time_.st M HudsonBuildTools20.package/HDTestReport.class/instance/running/runCase_.st M HudsonBuildTools20.package/HDTestReport.class/instance/running/tearDown.st A Ring-Core-Containers.package/RGPackage.class/instance/printing/printOn_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script206.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30551.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Tools.package/MessageBrowser.class/instance/private/wrapItem_.st M System-Support.package/SystemNavigation.class/instance/private/createMethodNamed_realParent_.st Log Message: ----------- 30551 - Issue 12088: Show the package in the senders and implementors window https://pharo.fogbugz.com/f/cases/12088/ - Issue 12060: The Quit menu entry is not asking for a confirmation anymore? https://pharo.fogbugz.com/f/cases/12060/ Smalltalk tools userManager currentUser permissions canSaveImage: true - Issue 12079: HDTestReport improvements https://pharo.fogbugz.com/f/cases/12079/ http://files.pharo.org/image/30/30551.zip

Nov. 7, 2013

[pharo-project/pharo-core]

by GitHub

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

Nov. 7, 2013

[update 3.0] #30551

by StÃ©phane Ducasse

30551 ----- >From buenos aires sprint - Issue 12088: Show the package in the senders and implementors window https://pharo.fogbugz.com/f/cases/12088/ - Issue 12060: The Quit menu entry is not asking for a confirmation anymore? https://pharo.fogbugz.com/f/cases/12060/ Smalltalk tools userManager currentUser permissions canSaveImage: true - Issue 12079: HDTestReport improvements https://pharo.fogbugz.com/f/cases/12079/ Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Support-StephaneDucass… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Tools-StephaneDucasse.15… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Ring-Core-Containers-Stephane… http://smalltalkhub.com/mc/Pharo/Pharo30/main/HudsonBuildTools20-StephaneDu…

Nov. 7, 2013

Opal, Pharo 3.0 and popup raising for none existing methods

by Mariano Martinez Peck

Hi guys, In Pharo 2.0 we have the setting #warningAllowed in Parser. This allow us to disable the popups each time you save a method with a selector that doesn't exist. In Pharo 3.0 with the new Opal this setting doesn't exist anymore. Is there a way to get this behavior??? Thanks, -- Mariano http://marianopeck.wordpress.com

Nov. 7, 2013

Re: [Pharo-dev] extracting a pier book into pillar files

by Tudor Girba

I know the syntax is the same. I was just asking if there is a ready made script that *just* do the migration :). Should I understand that you are working on this? Any timeline? Doru On Thu, Nov 7, 2013 at 2:45 PM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > I put the Magritte/Pier mailing list on copy. > > On Wed, Nov 6, 2013 at 2:24 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > > Is there existing support to extract an existing Pier-based book into > Pillar > > files? > > > > I would be interested in moving the Moose book to this format. > > > I'm not finished yet with the Pier-Book migration to Pillar. But the > format (i.e., wiki syntax) is exactly the same. So, you *just* need to > extract each Pier-Book chapter to a separate file. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 7, 2013

Re: [Pharo-dev] Checking RB rules? manifest browser?

by Camille Teruel

On 6 nov. 2013, at 22:43, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > We have some rules we would like to check against our code (Amber slime rules). How can we do that? > Do we need the manifest browser? How to load it? I searched for "manifest" in smalltalkhub and I got no result. Your rules should already appear in the critic browser under the category 'Unclassified rules'. You can put them in the category you want by implementing #category. > Help appreciated. > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Nov. 7, 2013

Re: [Pharo-dev] [FEEDBACK] Install Pharo on MacOSX

by kilon alios

just go to system preferences and check to download the sources automatically, that advice worked for me should work for you. Damien I will try the new dmg when I get home, cause all my macs are home. On Thu, Nov 7, 2013 at 4:42 PM, Matias Garcia Isaia <mgarciaisaia(a)gmail.com>wrote: > Hi there! > > Worked like a charm in Mavericks here. > > The Pharo Loader looks superb :) > > > I've installed the app with no trouble, and downloaded the latest Pharo2 > image. After launching it, the image showed a notification with this > message: > > "Information > Pharo cannot locate the sources file named /Applications/PharoV20.sources. > > Please check that the file is named properly and is in the > same directory as this image. > Make sure the sources file is not an Alias." > > > I hope that says to you more than it says to me :) > > Feel free to ask for clarification, if you need any. > > > On Thu, Nov 7, 2013 at 10:36 AM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > >> On Tue, Nov 5, 2013 at 12:10 PM, Mark Bestley <news{(a)bestley.co.uk> >> wrote: >> > This is due to Gatekeeper I think. I managed to open it by choosing Open >> > in the right click menu in Finder. see >> > <http://support.apple.com/kb/ht5290> I think you need to sign the app >> >> >> thank you for the reference. I will have a look. I wanted to put the >> application on the Mac App Store, but it looks I would have to pay >> Apple and I don't want to. Hope your solution doesn't require that. >> >> > The Launcher looks for and save images in ~/Library/Preferences/Pharo >> > This is wrong it should be ~/Library/Application/Support/Pharo for >> > general use, there is a case for using ~/Library/Containers to fit in >> > with Apple's sandboxing. >> >> >> I wanted to do that already. Thanks for the directory names. Do you >> have an url where Apple discusses such directories? >> >> >> > Or better allow us to chnage the directory >> >> >> That's on my todo. As always, I need help. This is the kind of change >> people can do easily (the preference mechanism is already in place). >> So, if you want to hack on the launcher, this would be a good start. >> >> >> > The icons are odd, trying to get a new Pharo 3 image it says hit refresh >> > icon which took me some time to find. Although I am bad at all icons so >> > might just be me. >> >> It's not just you. I see 2 solutions: >> >> - have a menu item to refresh when right clicking on the "hit refresh >> button" message. >> - automatically download the content when expanding the tree. >> >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." >> Winston Churchill >> >> >

Nov. 7, 2013