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

[fuel] should we integrate 12052

by StÃ©phane Ducasse

Hi Fuelers should I integrate https://pharo.fogbugz.com/f/cases/12052/Fuel-could-store-LargeNegativeInteg… Stef

Nov. 3, 2013

Feature request poll

by Yuriy Tymchuk

Hi everyone, Iâve just got an idea (not something extra ordinary) to try out. Maybe we can make some kind of poll where community will be able to add new feature requests and vote for them. This way we can get an idea what is important to most of people. Eg. see how many votes are for the stateful traits and how many for the ability to quit image without prompt for saving. After writing last sentence Iâve figured out that itâs a good idea to be able also to vote down :) But I think that this can be a nice experiment. Also as we are promoting and idea that âPharo is made by youâ, then new feature poll is nice to have. Cheers. Uko

Nov. 3, 2013

Re: [Pharo-dev] Github and Pharo

by StÃ©phane Ducasse

one of you should write a blog entry on Git support and the process :) Because we will get this repeat that often. Stef On Nov 3, 2013, at 2:11 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > ok it was my bad, i had not correctly initialized my git repo. Now it works fine. Thanks for the help this awesome. > > > On Sun, Nov 3, 2013 at 2:56 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > I installed OSProcess but I get a new Error : Git Error : bad default revision 'Head' > > just to clarify i try to commit to an existing git repo that I have create manually via terminal. > > > MCFileTreeGitRepository(Object)>>error: > MCFileTreeGitRepository>>gitVersions > MCFileTreeGitRepository>>loadAncestry > MCFileTreeGitRepository>>loadAllFileNames in Block: [ :bar | ... > BlockClosure>>cull: > Job>>run in Block: [ result := block cull: self ] > BlockClosure>>on:do: > Job>>run in Block: [ ... > BlockClosure>>ensure: > Job>>run > MorphicUIManager(UIManager)>>displayProgress:from:to:during: > ByteString(String)>>displayProgressFrom:to:during: > MCFileTreeGitRepository>>loadAllFileNames > MCFileTreeGitRepository>>allFileNames > MCFileTreeGitRepository>>readableFileNames > MCFileTreeGitRepository(MCFileTreeRepository)>>allFileNamesForVersionNamed: > MCFileTreeGitRepository(MCDirectoryRepository)>>includesVersionNamed: > MCWorkingCopy>>uniqueVersionNameIn: in Block: [ ... > BlockClosure>>cull: > Job>>run in Block: [ result := block cull: self ] > BlockClosure>>on:do: > Job>>run in Block: [ ... > BlockClosure>>ensure: > Job>>run > MorphicUIManager(UIManager)>>displayProgress:from:to:during: > ByteString(String)>>displayProgressFrom:to:during: > MCWorkingCopy>>uniqueVersionNameIn: > MCWorkingCopy>>newVersionIn: > MCWorkingCopyBrowser>>basicSaveVersionIn: in Block: [ ... > WorldState>>runStepMethodsIn: > > > > On Sun, Nov 3, 2013 at 2:40 PM, GOUBIER Thierry <thierry.goubier(a)cea.fr> wrote: > Oh sorry, the OSProcess dependency is missing :( > > You can install OSProcess from the configuration browser in your Pharo image or, on the command line : > > $ pharo Pharo.image config http://ss3.gemstone.com/ss/MetaRepoForPharo20 ConfigurationOfOSProcess --install=stable > > Thierry > > De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de kilon alios [kilon.alios(a)gmail.com] > Date d'envoi : dimanche 3 novembre 2013 13:30 > > Ã : Pharo Development List > Objet : Re: [Pharo-dev] Github and Pharo > > look like it cant find PipeableOSProcess on Macos, any idea where I can find this object ? > > UndefinedObject(Object)>>doesNotUnderstand: #command: > MCFileTreeGitRepository>>gitVersions > MCFileTreeGitRepository>>loadAncestry > MCFileTreeGitRepository>>loadAllFileNames in Block: [ :bar | ... > BlockClosure>>cull: > Job>>run in Block: [ result := block cull: self ] > BlockClosure>>on:do: > Job>>run in Block: [ ... > BlockClosure>>ensure: > Job>>run > MorphicUIManager(UIManager)>>displayProgress:from:to:during: > ByteString(String)>>displayProgressFrom:to:during: > MCFileTreeGitRepository>>loadAllFileNames > MCFileTreeGitRepository>>allFileNames > MCFileTreeGitRepository>>readableFileNames > MCFileTreeGitRepository(MCFileTreeRepository)>>allFileNamesForVersionNamed: > MCFileTreeGitRepository(MCDirectoryRepository)>>includesVersionNamed: > MCWorkingCopy>>uniqueVersionNameIn: in Block: [ ... > BlockClosure>>cull: > Job>>run in Block: [ result := block cull: self ] > BlockClosure>>on:do: > Job>>run in Block: [ ... > BlockClosure>>ensure: > Job>>run > MorphicUIManager(UIManager)>>displayProgress:from:to:during: > ByteString(String)>>displayProgressFrom:to:during: > MCWorkingCopy>>uniqueVersionNameIn: > MCWorkingCopy>>newVersionIn: > MCWorkingCopyBrowser>>basicSaveVersionIn: in Block: [ ... > WorldState>>runStepMethodsIn: > > > > On Sun, Nov 3, 2013 at 12:41 PM, GOUBIER Thierry <thierry.goubier(a)cea.fr> wrote: > This is where you use GitFileTree. > > GitFileTree will do you the commit, browsing the git logs and accessing all versions of your package in the git repo (browsing, loading, changes with the same GUI and look as a smalltalkhub repo). It won't do the push, however(*). It will show you the current branch in the repo too (**). > > For pharo3, GitFileTree is available with: > > $ pharo Pharo.image eval --save Gofer new url: \'http://smalltalkhub.com/mc/ThierryGoubier/MonticelloFileTree-Git/main\'\; package: \'MonticelloFileTree-Git\'\; load > > For pharo2, there is a group named 'MonticelloFileTree-Git' in FileTree configuration. > > Feel free to ask if you have any questions or suggestions on it! > > Thierry > > (*) It would be easy to do commit + push in one go, but, I'm not sure I'd like to do a push each time I do a commit. I tend to prefer a push a day. Maybe something like a marker in the repository inspector to remind me I have something to push? > (**) It doesn't change branches, and there is no support for branches in Monticello... This tend to trigger bugs in MC package cache. > > De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de kilon alios [kilon.alios(a)gmail.com] > Date d'envoi : dimanche 3 novembre 2013 10:16 > Ã : Pharo Development List > Objet : Re: [Pharo-dev] Github and Pharo > > Thank you for your efforts , I have installed filetree using the instructions provided in the github pages for pharo 3. I was also successful into generating the local files for my packages that I have inserted to my git folder. I can manually git commit and git push them from terminal but how I do this from inside Monticello-Filetree ? > > > On Sun, Nov 3, 2013 at 9:53 AM, GOUBIER Thierry <thierry.goubier(a)cea.fr> wrote: > Hi, > > I've used github and work_owned git repositories as primary workplaces for more than a year. First with FileTree, then I wrote GitFileTree to make that process simpler. > > Thierry > De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de kilon alios [kilon.alios(a)gmail.com] > Date d'envoi : samedi 2 novembre 2013 14:59 > Ã : Pharo Development List > Objet : [Pharo-dev] Github and Pharo > > So any information on how Pharo can be used with Github ? > > all I have is this > > https://github.com/dalehenrich/FSGit > > I dont need much, just basic git pull, push, clone, add and rm should do fine for starter. > > But of course I am interesting into learning what can be done, what is available , who needs help with what. Github is something really important for me, so I am willing to contribute as much I can into bringing Pharo closer to it. > > My interest is using Github in place of smalltalkhub and squeaksource. I was planning to implement something like an App Store (not the purchase system) for Pharo libraries and I would love to use github as a backend to it and git of course. > > > >

Nov. 3, 2013

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

by StÃ©phane Ducasse

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?" >> >> >

Nov. 3, 2013

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

by phil＠highoctane.be

See also https://pharo.fogbugz.com/default.asp?10263 Phil On Sun, Nov 3, 2013 at 11:21 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Thanks. > > Doru > > > On Sun, Nov 3, 2013 at 11:02 PM, Alexandre Bergel <alexandre.bergel(a)me.com > > wrote: > >> >> https://pharo.fogbugz.com/f/cases/12064/Selecting-a-package-in-the-Monticel… >> >> Alexandre >> >> >> On Nov 3, 2013, at 6:55 PM, Benjamin < >> benjamin.vanryseghem.pharo(a)gmail.com> wrote: >> >> > 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" >> > >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> 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

Thanks. Doru On Sun, Nov 3, 2013 at 11:02 PM, Alexandre Bergel <alexandre.bergel(a)me.com>wrote: > > https://pharo.fogbugz.com/f/cases/12064/Selecting-a-package-in-the-Monticel… > > Alexandre > > > On Nov 3, 2013, at 6:55 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> > wrote: > > > 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" > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 3, 2013

Re: [Pharo-dev] Cannot browse package within the monticello browser anymore

by Alexandre Bergel

Okay Alexandre On Nov 3, 2013, at 7:10 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I think you are in a Moose image. There, the Moose implementation of flatCollect: causes a problem when working with SortedCollection. Once the fix for issue 12056/flatCollect-should-return-the-same-species will be included, this problem will not happen in the Moose image either. > > https://pharo.fogbugz.com/f/cases/12056/flatCollect-should-return-the-same-… > > Cheers, > Doru > > > On Nov 3, 2013, at 11:04 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > >> 1 - Open a monticello browser >> 2 - select a package >> 3 - click the browse button, and you get an error (at:put: should not have been implemented on SortedCollection). >> >> https://pharo.fogbugz.com/f/cases/12065/Cannot-browse-package-within-the-mo… >> >> cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > > -- > www.tudorgirba.com > > "Being happy is a matter of choice." > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 3, 2013

Re: [Pharo-dev] Cannot browse package within the monticello browser anymore

by Tudor Girba

Hi, I think you are in a Moose image. There, the Moose implementation of flatCollect: causes a problem when working with SortedCollection. Once the fix for issue 12056/flatCollect-should-return-the-same-species will be included, this problem will not happen in the Moose image either. https://pharo.fogbugz.com/f/cases/12056/flatCollect-should-return-the-same-… Cheers, Doru On Nov 3, 2013, at 11:04 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > 1 - Open a monticello browser > 2 - select a package > 3 - click the browse button, and you get an error (at:put: should not have been implemented on SortedCollection). > > https://pharo.fogbugz.com/f/cases/12065/Cannot-browse-package-within-the-mo… > > cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- www.tudorgirba.com "Being happy is a matter of choice."

Nov. 3, 2013

Cannot browse package within the monticello browser anymore

by Alexandre Bergel

1 - Open a monticello browser 2 - select a package 3 - click the browse button, and you get an error (at:put: should not have been implemented on SortedCollection). https://pharo.fogbugz.com/f/cases/12065/Cannot-browse-package-within-the-mo… cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 3, 2013

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

by Alexandre Bergel

https://pharo.fogbugz.com/f/cases/12064/Selecting-a-package-in-the-Monticel… Alexandre On Nov 3, 2013, at 6:55 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > 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" > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 3, 2013