- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] 433393: 50407

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 43339304094c660e251b06951a1e18b00b310103 https://github.com/pharo-project/pharo-core/commit/43339304094c660e251b0695… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-10-27 (Tue, 27 Oct 2015) Changed paths: M Morphic-Core.package/HandMorph.class/instance/caching/releaseCachedState.st M Morphic-Core.package/HandMorph.class/instance/focus handling/keyboardFocus_.st M Morphic-Core.package/HandMorph.class/instance/focus handling/newKeyboardFocus_.st R Morphic-Core.package/HandMorph.class/instance/focus handling/releaseAllFoci.st A Morphic-Core.package/HandMorph.class/instance/focus handling/releaseAllFocus.st M Morphic-Core.package/HandMorph.class/instance/initialization/interrupted.st M Refactoring-Critics.package/RBRefersToClassRule.class/instance/running/basicCheck_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50406.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50407.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50406.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50407.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50407 16874 RBRefersToClassRule should handle classes that are not in method dict https://pharo.fogbugz.com/f/cases/16874 16856 Any KeyboardFocus change in the HandMorph should be announced https://pharo.fogbugz.com/f/cases/16856 http://files.pharo.org/image/50/50407.zip

Oct. 27, 2015

[pharo-project/pharo-core]

by GitHub

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

Oct. 27, 2015

Re: [Pharo-dev] Random access to meta repos?

by Thierry Goubier

Le 27/10/2015 02:22, Yuriy Tymchuk a Ã©crit : > So was this fixed or not? Because if Iâm opening a git repo â it > checks the meta, Iâm saving to git repo â it checks the metaâ¦ Hi Uko, I thought I fixed it; but yes it is checking the meta too much. I'll have a look. Thierry > Uko > > >> On 24 Aug 2015, at 22:05, Thierry Goubier >> <thierry.goubier(a)gmail.com> wrote: >> >> Hi Paul, >> >> do you still see some of this in one of the filetree branches when >> doing metacello integration testing? >> >> Thierry >> >> Le 24/08/2015 19:41, Paul DeBruicker a Ã©crit : >>> per this discussion: >>> https://github.com/dalehenrich/metacello-work/issues/354 >>> >>> You might check that your copy of >>> MCFileRepositoryInspector>>#refresh doesn't refer to a >>> nonexistent instvar >>> >>> >>> >>> Uko2 wrote >>>> Hi, >>>> >>>> Iâve noticed that when I try to open a gitfiletree repo, before >>>> displaying its contents something from meta repos is loaded >>>> (seen on screenshot). Why does it need file names from meta >>>> repos to display contents of the repo which is present on my >>>> machine? >>>> >>>> Uko >>>> >>>> >>>> >>>> >>>> >>>> Screen Shot 2015-08-21 at 19.06.39.png (587K) >>>> <http://forum.world.st/attachment/4845061/0/Screen%20Shot%202015-08-21%20at%2019.06.39.png> >>> >>> >>> >>> >>> >>> >>>> -- >>> View this message in context: >>> http://forum.world.st/Random-access-to-meta-repos-tp4845061p4845346.html >>> >>> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >>> >>> >>> >> >> > > >

Oct. 27, 2015

Re: [Pharo-dev] Finding the reason of merge

by Thierry Goubier

Le 27/10/2015 03:40, Chris Cunningham a Ã©crit : > you could try Merging instead of loading, and then look at the > difference between the newly merged in-image package and version 74. > > Or, you could open the Monticello browser, highlight the package (which > you've already done),and click on Changes to see what you've changed > since version 73. > > Or, maybe gitfiletree has so changed Monticello behaviour that neither > of these work anymore? In that, GitFileTree has not changed Monticello behavior, so those operations should work. Thierry > In any case, if you try to load over your changes, it doesn't give you > any hint as to what it is loading over. > > -cbc > > On Mon, Oct 26, 2015 at 6:14 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com > <mailto:yuriy.tymchuk@me.com>> wrote: > > Ok, Iâm completely exhausted, I have no clue whatâs the problem. > > I have version 73 of my package, I load version 74 an then it says: > âIf you continue, you will loose these changes: â and there is > nothing more, there are no changes that Iâm going to loose. Is there > any way to identify why the merge is happening. Yes, maybe it is > because I am using gitfiletree, but how do I find out the reason of > merge? Monticello is an amazing tool because it keeps my hands tied, > as I cannot really debug why there is a merge (itâs too complex at > least for me). > > Uko > >

Oct. 27, 2015

Re: [Pharo-dev] Finding the reason of merge

by Chris Cunningham

you could try Merging instead of loading, and then look at the difference between the newly merged in-image package and version 74. Or, you could open the Monticello browser, highlight the package (which you've already done),and click on Changes to see what you've changed since version 73. Or, maybe gitfiletree has so changed Monticello behaviour that neither of these work anymore? In any case, if you try to load over your changes, it doesn't give you any hint as to what it is loading over. -cbc On Mon, Oct 26, 2015 at 6:14 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Ok, Iâm completely exhausted, I have no clue whatâs the problem. > > I have version 73 of my package, I load version 74 an then it says: âIf > you continue, you will loose these changes: â and there is nothing more, > there are no changes that Iâm going to loose. Is there any way to identify > why the merge is happening. Yes, maybe it is because I am using > gitfiletree, but how do I find out the reason of merge? Monticello is an > amazing tool because it keeps my hands tied, as I cannot really debug why > there is a merge (itâs too complex at least for me). > > Uko >

Oct. 27, 2015

Re: [Pharo-dev] Loading of Baselines from GitHub in Metacello using pattern matching not working on Windows

by Gabriel Cotelli

Thanks Dale, I can confirm that with the latest version in master this works in Pharo 5. On Mon, Oct 26, 2015 at 9:10 PM, Dale Henrichs < dale.henrichs(a)gemtalksystems.com> wrote: > Gabriel, > > Are you using the latest version of Metacello from github (these > instructions work for versions 3.0 and newer[1])? > > The pattern matching feature is relatively new so unless you've loaded > from github, you are likely not getting the needed support ... > > I think that Pharo5.0 should be built with the latest Metacello drop from > github ... but it must not be happening yet .... > > Dale > > [1] https://github.com/dalehenrich/metacello-work#pharo30 > > > On 10/26/2015 04:37 PM, Gabriel Cotelli wrote: > >> When trying to load a baseline using the Metacello API and version >> pattern matching, using the gituhb:// scheme produces an error because it's >> trying to create a directory with a question mark (?). >> >> To reproduce try in a Pharo4/5 image: >> >> Metacello new >> baseline: 'RenoirSt'; >> repository: 'github://gcotelli/RenoirSt:v1.?/source'; >> load. >> >> Dale, Is this supposed to work? Tomorrow I will give it a try on Linux. >> >> Thanks, >> Gabriel >> > > >

Oct. 27, 2015

Re: [Pharo-dev] Random access to meta repos?

by Yuriy Tymchuk

So was this fixed or not? Because if Iâm opening a git repo â it checks the meta, Iâm saving to git repo â it checks the metaâ¦ Uko > On 24 Aug 2015, at 22:05, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Hi Paul, > > do you still see some of this in one of the filetree branches when doing metacello integration testing? > > Thierry > > Le 24/08/2015 19:41, Paul DeBruicker a Ã©crit : >> per this discussion: https://github.com/dalehenrich/metacello-work/issues/354 >> >> You might check that your copy of MCFileRepositoryInspector>>#refresh >> doesn't refer to a nonexistent instvar >> >> >> >> Uko2 wrote >>> Hi, >>> >>> Iâve noticed that when I try to open a gitfiletree repo, before displaying >>> its contents something from meta repos is loaded (seen on screenshot). Why >>> does it need file names from meta repos to display contents of the repo >>> which is present on my machine? >>> >>> Uko >>> >>> >>> >>> >>> >>> Screen Shot 2015-08-21 at 19.06.39.png (587K) >>> <http://forum.world.st/attachment/4845061/0/Screen%20Shot%202015-08-21%20at%2019.06.39.png> >> >> >> >> >> >> -- >> View this message in context: http://forum.world.st/Random-access-to-meta-repos-tp4845061p4845346.html >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> >> >> > >

Oct. 27, 2015

Finding the reason of merge

by Yuriy Tymchuk

Ok, Iâm completely exhausted, I have no clue whatâs the problem. I have version 73 of my package, I load version 74 an then it says: âIf you continue, you will loose these changes: â and there is nothing more, there are no changes that Iâm going to loose. Is there any way to identify why the merge is happening. Yes, maybe it is because I am using gitfiletree, but how do I find out the reason of merge? Monticello is an amazing tool because it keeps my hands tied, as I cannot really debug why there is a merge (itâs too complex at least for me). Uko

Oct. 27, 2015

Re: [Pharo-dev] Loading of Baselines from GitHub in Metacello using pattern matching not working on Windows

by Gabriel Cotelli

I'm using the version that comes preloaded with Pharo. This also fails in Pharo 5. I will give it a try with the github version and if it works I can prepare a slice to merge this version in Pharo. Thanks On Oct 26, 2015 9:11 PM, "Dale Henrichs" <dale.henrichs(a)gemtalksystems.com> wrote: > Gabriel, > > Are you using the latest version of Metacello from github (these > instructions work for versions 3.0 and newer[1])? > > The pattern matching feature is relatively new so unless you've loaded > from github, you are likely not getting the needed support ... > > I think that Pharo5.0 should be built with the latest Metacello drop from > github ... but it must not be happening yet .... > > Dale > > [1] https://github.com/dalehenrich/metacello-work#pharo30 > > On 10/26/2015 04:37 PM, Gabriel Cotelli wrote: > >> When trying to load a baseline using the Metacello API and version >> pattern matching, using the gituhb:// scheme produces an error because it's >> trying to create a directory with a question mark (?). >> >> To reproduce try in a Pharo4/5 image: >> >> Metacello new >> baseline: 'RenoirSt'; >> repository: 'github://gcotelli/RenoirSt:v1.?/source'; >> load. >> >> Dale, Is this supposed to work? Tomorrow I will give it a try on Linux. >> >> Thanks, >> Gabriel >> > > >

Oct. 27, 2015

Re: [Pharo-dev] Little Meeting at Pittsburg

by Juan Pablo Sandoval Alcocer

I am attending OOPSLA too, It would be a pleasure to be part of the meeting. Juampi 2015-10-25 19:30 GMT-03:00 stepharo <stepharo(a)free.fr>: > Hi > > Guillermo, Andrei, Guido and me are attending OOPSLA so we could have a > small > Pharo meeting. > What about wednesday evening? > > Stef > > -- Saludos, Juan Pablo

Oct. 27, 2015