- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

July 6, 2016

[pharo-project/pharo-core] 382ab2: 60139

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 382ab247b7ff419185670b875e426a6d80765eab https://github.com/pharo-project/pharo-core/commit/382ab247b7ff419185670b87… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-07-06 (Wed, 06 Jul 2016) Changed paths: R Glamour-Morphic-Brick.package/GLMBrick.class/instance/brick-structure-testing/isFirstInOwner.st M Glamour-Morphic-Brick.package/GLMBrickStructureTrait.class/instance/brick-structure-testing/isFirstInOwner.st M Glamour-Morphic-Brick.package/GLMBrickStructureTrait.class/instance/brick-structure-testing/isLastInOwner.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60138.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60139.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60138.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60139.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Slot.package/AbstractClassModification.class/instance/accessing/layout_.st M Slot.package/extension/Behavior/instance/layout.st M Slot.package/extension/Behavior/instance/layout_.st M Traits.package/TBehavior.class/instance/accessing/typeOfClass.st Log Message: ----------- 60139 16636 Rename layout to classLayout (step 4 deprecate) https://pharo.fogbugz.com/f/cases/16636 18449 Glamour: "Do not use #ifNotNilDo:ifNil:, #ifNil:ifNotNilDo:, #ifNotNilDo:" https://pharo.fogbugz.com/f/cases/18449 http://files.pharo.org/image/60/60139.zip

July 6, 2016

Re: [Pharo-dev] Pharo Launcher ?

by Damien Cassou

Sven Van Caekenberghe <sven(a)stfx.eu> writes: > So I finally started using Pharo Launcher (yes I know, too late) and it is really great ! > > Where is the documentation for it ? > > Why is it not mentioned on the main download page ? > > Where is its landing page, quick reference, 1-2-3 getting started web page ? > > I went via http://files.pharo.org/platform/launcher/ but that is highly technical and certainly not for first time users. > > We have to promote this better. http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

July 6, 2016

Pharo Launcher ?

by Sven Van Caekenberghe

Hi, So I finally started using Pharo Launcher (yes I know, too late) and it is really great ! Where is the documentation for it ? Why is it not mentioned on the main download page ? Where is its landing page, quick reference, 1-2-3 getting started web page ? I went via http://files.pharo.org/platform/launcher/ but that is highly technical and certainly not for first time users. We have to promote this better. Sven

July 6, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

by Sven Van Caekenberghe

> On 06 Jul 2016, at 13:51, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > > On Wed, Jul 6, 2016 at 12:28 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > yes, I do not agree either but is true there where problems. > but IMO this would be solved just by putting a timeout in 1-2s (and then run in background, and cache results) > not turning it off. > in for my experience, turning something off is equivalent to remove the feature (but then is worst, because it becomes dead code inside image). > > This is how it's currently implemented but it doesn't solve all issues: > https://pharo.fogbugz.com/f/cases/18281/NetNameResolver-class-addressForNam… Yes, that is the core issue. We need a reliable, non-blocking way to determine (or discover) if we have network or not. Then we can react properly at the application level. > Anyway, any taker, to solve this in a proper way? > > Esteban > > > On 06 Jul 2016, at 12:13, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > > > >> On 06 Jul 2016, at 10:12, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> > >> > >>> On 06 Jul 2016, at 09:52, GitHub <noreply(a)github.com> wrote: > >>> > >>> 18674 Turn spotter catalog off by default > >>> https://pharo.fogbugz.com/f/cases/18674 > >> > >> We did not agree on this, at all, there was no public discussion, no vote. > >> > > > > I only know that there where problems. > > > > Marcus > > > > >

July 6, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

by Andrei Chis

On Wed, Jul 6, 2016 at 12:28 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > yes, I do not agree either but is true there where problems. > but IMO this would be solved just by putting a timeout in 1-2s (and then > run in background, and cache results) > not turning it off. > in for my experience, turning something off is equivalent to remove the > feature (but then is worst, because it becomes dead code inside image). > This is how it's currently implemented but it doesn't solve all issues: https://pharo.fogbugz.com/f/cases/18281/NetNameResolver-class-addressForNam… > > Anyway, any taker, to solve this in a proper way? > > Esteban > > > On 06 Jul 2016, at 12:13, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > > > >> On 06 Jul 2016, at 10:12, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> > >> > >>> On 06 Jul 2016, at 09:52, GitHub <noreply(a)github.com> wrote: > >>> > >>> 18674 Turn spotter catalog off by default > >>> https://pharo.fogbugz.com/f/cases/18674 > >> > >> We did not agree on this, at all, there was no public discussion, no > vote. > >> > > > > I only know that there where problems. > > > > Marcus > > > > >

July 6, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

by Esteban Lorenzano

yes, I do not agree either but is true there where problems. but IMO this would be solved just by putting a timeout in 1-2s (and then run in background, and cache results) not turning it off. in for my experience, turning something off is equivalent to remove the feature (but then is worst, because it becomes dead code inside image). Anyway, any taker, to solve this in a proper way? Esteban > On 06 Jul 2016, at 12:13, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 06 Jul 2016, at 10:12, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> >>> On 06 Jul 2016, at 09:52, GitHub <noreply(a)github.com> wrote: >>> >>> 18674 Turn spotter catalog off by default >>> https://pharo.fogbugz.com/f/cases/18674 >> >> We did not agree on this, at all, there was no public discussion, no vote. >> > > I only know that there where problems. > > Marcus >

July 6, 2016

Re: [Pharo-dev] confused about the "image opening session"

by Esteban Lorenzano

> On 06 Jul 2016, at 09:00, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > > yes, what is bad now is that there is âno crash detectorâ. > If you quit an image without saving, you will get the epicea browser. I do not want it in this case. When I do not save, it is on purpose. > Maybe a flag should be set when you quit the image (by saving or not). This way, if the flag is not present at image startup, you could guess a crash. +100 > >> Le 5 juil. 2016 Ã 21:50, stepharo <stepharo(a)free.fr> a Ã©crit : >> >> Hi >> >> I saw that we have a new cool feature that presents changes that would have been loaded but not save in the image. >> >> Now I got confused because several times I prompted with this list and I do not see how I ended up having it >> >> since I save my image and did not get crash (or idea that I lost changes). >> >> Is it me that do not understand correctly this feature? >> >> At the minimum it would be nice to have a little bit more explanation about what is happening. >> >> Because I imagine new guys coming and seeing this list without any further explanation could be confused. >> >> Stef >> >> > >

July 6, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

by Marcus Denker

> On 06 Jul 2016, at 10:12, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > >> On 06 Jul 2016, at 09:52, GitHub <noreply(a)github.com> wrote: >> >> 18674 Turn spotter catalog off by default >> https://pharo.fogbugz.com/f/cases/18674 > > We did not agree on this, at all, there was no public discussion, no vote. > I only know that there where problems. Marcus

July 6, 2016

[pharo-project/pharo-core]

by GitHub

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

July 6, 2016