- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] b304de: 30515

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: b304de07315905f321112d7762afa3e226c14aa7 https://github.com/pharo-project/pharo-core/commit/b304de07315905f321112d77… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-10-22 (Tue, 22 Oct 2013) Changed paths: M Morphic-Base.package/HaloMorph.class/instance/private/addNameBeneath_string_.st R Morphic-Base.package/TextMorph.class/instance/anchors/adjustTextAnchor_.st M Morphic-Core.package/Morph.class/instance/private/privateFullMoveBy_.st A Nautilus.package/PackageTreeModel.class/instance/drag and drop/acceptDroppingMorph_event_inMorph_.st A Nautilus.package/PackageTreeModel.class/instance/drag and drop/wantsDroppedMorph_event_inMorph_.st R NautilusCommon.package/extension/RBBrowserEnvironment/instance/packageOrganizer.st R NautilusCommon.package/extension/RBBrowserEnvironmentWrapper/instance/packages.st A Refactoring-Environment.package/RBBrowserEnvironment.class/instance/private/packageOrganizer.st A Refactoring-Environment.package/RBBrowserEnvironmentWrapper.class/instance/accessing/packages.st A Refactoring-Environment.package/RBSelectorEnvironment.class/instance/accessing/packages.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script170.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30515.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30515 11970 simplify #privateFullMoveBy: and fix Halos https://pharo.fogbugz.com/f/cases/11970 11971 PackageTreeNautilus drag and drop on the package tree https://pharo.fogbugz.com/f/cases/resolve/11971 11795 RBBrowserEnvironment packages method is too broad https://pharo.fogbugz.com/f/cases/11795 http://files.pharo.org/image/30/30515.zip

Oct. 22, 2013

[pharo-project/pharo-core]

by GitHub

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

Oct. 22, 2013

VM for Athens Graphics

by J.F. Rick

I'm excited about the upcoming move to Athens graphics and would like to support that effort. It seems like the base is still under heavy development and that I should use an up-to-date Pharo 3.0 to properly use it. Let me know if that is incorrect. I was wondering for what VMs Athens is applicable. Would it automatically work on Linux? I've also been using Pharo / Squeak on the iPad. Would Athens work there or would the VM have to be changed? Cheers, Jeff -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

Oct. 22, 2013

Re: [Pharo-dev] Bisect with Pharo Launcher / Git

by Goubier Thierry

Le 22/10/2013 15:55, Bruni camillo a Ã©crit : > This is exactly the reason I started exporting everything to git and > archiving all the images in an accessible way :-P. It certainly was very helpfull and I'll use it again sooner or later. Would you happen to have a get.pharo.org way of getting a given image number? > it would be definitely nice to have this more automated. > On Oct 22, 2013 11:50 AM, <btc(a)openinworld.com > <mailto:btc@openinworld.com>> wrote: > > I am probably not working on it anytime soon, but btw I logged the > idea last week of enhancing Pharo Launcher with some kind of support > for bisect operations. > https://pharo.fogbugz.com/__default.asp?11927 > <https://pharo.fogbugz.com/default.asp?11927>. > > cheers -ben > > Goubier Thierry wrote: > > Hi all, > > I want to thank the combination of Pharo Launcher and the > pharo-core github repo for earching a specific bug in Pharo 3, > linked to https://pharo.fogbugz.com/f/__cases/11949/ > <https://pharo.fogbugz.com/f/cases/11949/> : > > I noticed that the bug was introduced between 30450 and 30490. > With the Pharo launcher, I then went through a ad-hoc bisecting > (loading the right image version / launching it / testing) : > > Start point is 30450 No bug, 30490 bug. > > 30470 No bug > 30480 No > 30485 Bug > 30483 No > 30484 Bug > > Then I tried to view the changes in Morphic for the bug out of > the Monticello tools... Didn't work :( It's hard to guess which > versions have changed and when in relation to the image version > number. > > So I went to github/pharo-core and I searched for the relevant > commit: > > https://github.com/pharo-__project/pharo-core/commit/__5034553d07f342a5a0e5… > <https://github.com/pharo-project/pharo-core/commit/5034553d07f342a5a0e51275…> > > > And a file that could be relevant: > > https://github.com/pharo-__project/pharo-core/commit/__5034553d07f342a5a0e5… > <https://github.com/pharo-project/pharo-core/commit/5034553d07f342a5a0e51275…> > > > And there I could see things in relation with MorpTreeMorph... > Bug solved shortly thereafter. Damn Rectangle stuff :( > > Thanks again > > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Oct. 22, 2013

Re: [Pharo-dev] Bisect with Pharo Launcher / Git

by Bruni camillo

On Oct 22, 2013 4:01 PM, "Goubier Thierry" <thierry.goubier(a)cea.fr> wrote: > > > > Le 22/10/2013 15:55, Bruni camillo a Ã©crit : > >> This is exactly the reason I started exporting everything to git and >> archiving all the images in an accessible way :-P. > > > It certainly was very helpfull and I'll use it again sooner or later. > > Would you happen to have a get.pharo.org way of getting a given image number? Not yet, that is something we have to add. >> it would be definitely nice to have this more automated. > > > > >> On Oct 22, 2013 11:50 AM, <btc(a)openinworld.com >> <mailto:btc@openinworld.com>> wrote: >> >> I am probably not working on it anytime soon, but btw I logged the >> idea last week of enhancing Pharo Launcher with some kind of support >> for bisect operations. >> https://pharo.fogbugz.com/__default.asp?11927 >> <https://pharo.fogbugz.com/default.asp?11927>. >> >> >> cheers -ben >> >> Goubier Thierry wrote: >> >> Hi all, >> >> I want to thank the combination of Pharo Launcher and the >> pharo-core github repo for earching a specific bug in Pharo 3, >> linked to https://pharo.fogbugz.com/f/__cases/11949/ >> >> <https://pharo.fogbugz.com/f/cases/11949/> : >> >> I noticed that the bug was introduced between 30450 and 30490. >> With the Pharo launcher, I then went through a ad-hoc bisecting >> (loading the right image version / launching it / testing) : >> >> Start point is 30450 No bug, 30490 bug. >> >> 30470 No bug >> 30480 No >> 30485 Bug >> 30483 No >> 30484 Bug >> >> Then I tried to view the changes in Morphic for the bug out of >> the Monticello tools... Didn't work :( It's hard to guess which >> versions have changed and when in relation to the image version >> number. >> >> So I went to github/pharo-core and I searched for the relevant >> commit: >> >> https://github.com/pharo-__project/pharo-core/commit/__5034553d07f342a5a0e5… >> >> < https://github.com/pharo-project/pharo-core/commit/5034553d07f342a5a0e51275… > >> >> >> And a file that could be relevant: >> >> https://github.com/pharo-__project/pharo-core/commit/__5034553d07f342a5a0e5… >> >> < https://github.com/pharo-project/pharo-core/commit/5034553d07f342a5a0e51275… > >> >> >> And there I could see things in relation with MorpTreeMorph... >> Bug solved shortly thereafter. Damn Rectangle stuff :( >> >> Thanks again >> >> >> > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

Oct. 22, 2013

Re: [Pharo-dev] Bisect with Pharo Launcher / Git

by Bruni camillo

This is exactly the reason I started exporting everything to git and archiving all the images in an accessible way :-P. it would be definitely nice to have this more automated. On Oct 22, 2013 11:50 AM, <btc(a)openinworld.com> wrote: > I am probably not working on it anytime soon, but btw I logged the idea > last week of enhancing Pharo Launcher with some kind of support for bisect > operations. > https://pharo.fogbugz.com/**default.asp?11927<https://pharo.fogbugz.com/default.asp?11927> > . > > cheers -ben > > Goubier Thierry wrote: > >> Hi all, >> >> I want to thank the combination of Pharo Launcher and the pharo-core >> github repo for earching a specific bug in Pharo 3, linked to >> https://pharo.fogbugz.com/f/**cases/11949/<https://pharo.fogbugz.com/f/cases/11949/>: >> >> I noticed that the bug was introduced between 30450 and 30490. With the >> Pharo launcher, I then went through a ad-hoc bisecting (loading the right >> image version / launching it / testing) : >> >> Start point is 30450 No bug, 30490 bug. >> >> 30470 No bug >> 30480 No >> 30485 Bug >> 30483 No >> 30484 Bug >> >> Then I tried to view the changes in Morphic for the bug out of the >> Monticello tools... Didn't work :( It's hard to guess which versions have >> changed and when in relation to the image version number. >> >> So I went to github/pharo-core and I searched for the relevant commit: >> >> https://github.com/pharo-**project/pharo-core/commit/** >> 5034553d07f342a5a0e512757a04e6**afec677d96<https://github.com/pharo-project/pharo-core/commit/5034553d07f342a5a0e51275…> >> >> And a file that could be relevant: >> >> https://github.com/pharo-**project/pharo-core/commit/** >> 5034553d07f342a5a0e512757a04e6**afec677d96#diff-** >> 8582177f7215f3cef75a8ce52f5ef0**12<https://github.com/pharo-project/pharo-core/commit/5034553d07f342a5a0e51275…> >> >> And there I could see things in relation with MorpTreeMorph... Bug solved >> shortly thereafter. Damn Rectangle stuff :( >> >> Thanks again >> > > >

Oct. 22, 2013

Re: [Pharo-dev] The new fogbugz mails look nice :)

by Benjamin

that would be cool ;) Ben On Oct 22, 2013, at 3:10 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > One would almost start fixing things, just to see them ;-) > > On 22 Oct 2013, at 15:08, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > >> Just to say :P >> >> Ben >> > >

Oct. 22, 2013

Re: [Pharo-dev] The new fogbugz mails look nice :)

by Sven Van Caekenberghe

One would almost start fixing things, just to see them ;-) On 22 Oct 2013, at 15:08, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > Just to say :P > > Ben >

Oct. 22, 2013

The new fogbugz mails look nice :)

by Benjamin

Just to say :P Ben

Oct. 22, 2013

[pharo-project/pharo-core]

by GitHub

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

Oct. 22, 2013