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

[pharo-project/pharo-core]

by GitHub

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

Nov. 5, 2014

[pharo-project/pharo-core] 01ad41: 40354

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 01ad41d66b44006aacf98786d3ec0d379a524bfc https://github.com/pharo-project/pharo-core/commit/01ad41d66b44006aacf98786… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-11-05 (Wed, 05 Nov 2014) Changed paths: A FileSystem-Core.package/AbstractFileReference.class/instance/accessing/item.st A Kernel.package/Point.class/instance/arithmetic/max.st A Kernel.package/Point.class/instance/arithmetic/min.st A Kernel.package/Point.class/instance/geometry/angle.st A Kernel.package/Point.class/instance/point functions/angleWith_.st A Kernel.package/Point.class/instance/point functions/directionToLineFrom_to_.st A Kernel.package/Point.class/instance/point functions/reflectedAbout_.st A Morphic-Base.package/SystemProgressItemMorph.class/instance/API/changed.st A Morphic-Base.package/TextMorph.class/instance/drawing/drawNullTextOn_.st A Morphic-Base.package/TextMorph.class/instance/drawing/drawOn_.st A Morphic-Base.package/TextMorph.class/instance/event handling/basicKeyStroke_.st A Morphic-Base.package/TextMorph.class/instance/event handling/keyStroke_.st A Morphic-Base.package/TextMorph.class/instance/testing/enabled.st A Morphic-Base.package/TransformMorph.class/instance/accessing/clipSubmorphs.st A Morphic-Base.package/TransformMorph.class/instance/accessing/extent_.st R NECompletion.package/extension/TextMorph/instance/basicKeyStroke_.st R NECompletion.package/extension/TextMorph/instance/enabled.st R NECompletion.package/extension/TextMorph/instance/keyStroke_.st A NewValueHolder.package/CollectionValueHolder.class/instance/protocol/remove_.st M OpalCompiler-Core.package/IRPushClosureCopy.class/instance/accessing/tempVectorNamed_.st A OpalCompiler-Core.package/IRPushClosureCopy.class/instance/private/blockHasTempVector_.st A OpalCompiler-Core.package/IRPushClosureCopy.class/instance/private/sequenceHasTempVector_.st M OpalCompiler-Core.package/IRPushClosureCopy.class/instance/testing/hasTempVector_.st M OpalCompiler-Core.package/OCCopyingTempVariable.class/instance/debugging/indexInTempVectorFromIR_.st M OpalCompiler-Core.package/OCVectorTempVariable.class/instance/debugging/readFromContext_scope_.st M OpalCompiler-Core.package/OCVectorTempVariable.class/instance/debugging/writeFromContext_scope_value_.st A OpalCompiler-Tests.package/MethodMapExamples.class/instance/examples/defineCopiedVarBecomeDeadContext.st A OpalCompiler-Tests.package/MethodMapExamples.class/instance/examples/exampleCopiedVarFromDeadContext.st A OpalCompiler-Tests.package/MethodMapExamples.class/instance/examples/exampleTempNamedTempVectorInlinedLoop.st A OpalCompiler-Tests.package/MethodMapTests.class/instance/testing - temp access/testCopiedVarFromDeadContext.st A OpalCompiler-Tests.package/MethodMapTests.class/instance/testing - temp access/testExampleTempNamedTempVectorInlinedLoop.st R Polymorph-Geometry.package/extension/Point/instance/directionToLineFrom_to_.st A Polymorph-Tools-Diff.package/DiffMorph.class/instance/updating/themeChanged.st R Polymorph-Widgets.package/extension/AbstractFileReference/instance/item.st R Polymorph-Widgets.package/extension/DiffMorph/instance/themeChanged.st R Polymorph-Widgets.package/extension/Point/instance/angle.st R Polymorph-Widgets.package/extension/Point/instance/angleWith_.st R Polymorph-Widgets.package/extension/Point/instance/max.st R Polymorph-Widgets.package/extension/Point/instance/min.st R Polymorph-Widgets.package/extension/Point/instance/reflectedAbout_.st R Polymorph-Widgets.package/extension/SystemProgressItemMorph/instance/changed.st R Polymorph-Widgets.package/extension/TextMorph/instance/drawNullTextOn_.st R Polymorph-Widgets.package/extension/TextMorph/instance/drawOn_.st R Polymorph-Widgets.package/extension/TransformMorph/instance/clipSubmorphs.st R Polymorph-Widgets.package/extension/TransformMorph/instance/extent_.st R Polymorph-Widgets.package/extension/UIManager/instance/theme.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script354.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40354.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40354 13260 inspecting variables in the debugger fails in some cases https://pharo.fogbugz.com/f/cases/13260 14393 CollectionValueHolder>>remove: does not annnounce change https://pharo.fogbugz.com/f/cases/14393 14397 reduce polymorph extension methods https://pharo.fogbugz.com/f/cases/14397 http://files.pharo.org/image/40/40354.zip

Nov. 5, 2014

Test Pharo website with Nibbler

by Torsten Bergmann

http://nibbler.silktide.com/en/reports/pharo.org

Nov. 5, 2014

Re: [Pharo-dev] Browse anObject?

by Marcus Denker

> On 05 Nov 2014, at 13:04, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > > 2014-11-05 12:29 GMT+01:00 Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>>: > Sean P. DeNigris wrote: > Ben Coman wrote > I think this shows its fairly well established that 'Browse' on its own means "view the object's code" > > I still vote to change it to more clearly reveal the intention. While > perhaps not particularly significant in itself, all these little "gotchas" > pile up for newbies, and rob mental energy from everyone's creative > expression. Alan Kay ballparked Squeak at "Encyclopedia Brittanica" LOC, > down from Windows' "Empire State Building" LOC, but IMHO mastering an entire > Encyclopedia is hard enough without a lot of special cases. > > > > ----- > Cheers, > Sean > > I thought more on this during the day and came to the conclusion that the least surprising would be... > > Object>>#browseClass > ^ self systemNavigation browseClass: self class > > Object>>#browse > self browseClass > > I find > > Object>>#browse > self class browse > > perfectly clear as well. And removes one unneeded selector on Object. > Yes, that is good.

Nov. 5, 2014

Re: [Pharo-dev] pane for repositories in the Configuration Browser

by Torsten Bergmann

Hi, when I initially created the config browser my idead was that (especially for newbees) the packages/frameworks/projects are easy to load. Key to success is easy access to things. One should not have to know or fight with Metacello, Gofer, ... in the first place. Things should just work ("click, load and run"). Advances users know about the script way of loading things or build configs with dependencies on their own. So in the beginning there was only ONE repo in the Config browser that should include the configs that are known to run in a specific Pharo version (therefore MetaRepoForPharo20, MetaRepoForPharo30, MetaRepoForPharo40, ... After that we found out it will be usefull to load also from older repos (like loading from MetaRepoForPharo30 when in Pharo 4) or also allow custom repos. Thats why I fixed it after the request from Sean: https://pharo.fogbugz.com/default.asp?13941 Now people seem to use this as well and would like to make the different repos more transparent. No problem with the additional pane. @Luc: I like your extension as with the config browser now people can see the other repos, load from them when in newer Pharo versions or use custom ones. But a newbee might easily be confused which repo to use and may end up in non-working loading. This is the opposite to what was the original intention of the tool. So we need to support both cases, but IMHO should keep things initially simple (according to the original idea). So I would like to see: - add a toggle to the menu ("Show repositories") to switch the preference also in config browser - hide the pane by default This way a newbee can just load without getting into (for him complicated) questions like "from what repo", "why is it not working" (when loading from the wrong), ... and an advanced user can set the preference according to his need as he might have checked the menus or preferences. Bye T.

Nov. 5, 2014

Re: [Pharo-dev] Browse anObject?

by Thierry Goubier

2014-11-05 12:29 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > Sean P. DeNigris wrote: > >> Ben Coman wrote >> >>> I think this shows its fairly well established that 'Browse' on its own >>> means "view the object's code" >>> >> >> I still vote to change it to more clearly reveal the intention. While >> perhaps not particularly significant in itself, all these little "gotchas" >> pile up for newbies, and rob mental energy from everyone's creative >> expression. Alan Kay ballparked Squeak at "Encyclopedia Brittanica" LOC, >> down from Windows' "Empire State Building" LOC, but IMHO mastering an >> entire >> Encyclopedia is hard enough without a lot of special cases. >> >> >> >> ----- >> Cheers, >> Sean >> > > I thought more on this during the day and came to the conclusion that the > least surprising would be... > > Object>>#browseClass > ^ self systemNavigation browseClass: self class > > Object>>#browse > self browseClass > I find Object>>#browse self class browse perfectly clear as well. And removes one unneeded selector on Object. Thierry > > > > but its just a passing thought, and not a big deal. > cheers -ben > >

Nov. 5, 2014

Re: [Pharo-dev] Browse anObject?

by Ben Coman

Sean P. DeNigris wrote: > Ben Coman wrote >> I think this shows its fairly well established that 'Browse' on >> its own means "view the object's code" > > I still vote to change it to more clearly reveal the intention. While > perhaps not particularly significant in itself, all these little "gotchas" > pile up for newbies, and rob mental energy from everyone's creative > expression. Alan Kay ballparked Squeak at "Encyclopedia Brittanica" LOC, > down from Windows' "Empire State Building" LOC, but IMHO mastering an entire > Encyclopedia is hard enough without a lot of special cases. > > > > ----- > Cheers, > Sean I thought more on this during the day and came to the conclusion that the least surprising would be... Object>>#browseClass ^ self systemNavigation browseClass: self class Object>>#browse self browseClass but its just a passing thought, and not a big deal. cheers -ben

Nov. 5, 2014

Re: [Pharo-dev] pane for repositories in the Configuration Browser

by Sven Van Caekenberghe

> On 05 Nov 2014, at 11:46, Stephan Eggermont <stephan(a)stack.nl> wrote: > > Hmm. It solves the problem I definitely don't have with the configuration browser. > It is supposed to be helpful and provide simple and working configurations. > That doesn't work as the configurations are not composable > (loading magritte and then loading seaside misses magritte-seaside). That is a totally different problem, unrelated to the subject. It seems legit, but even more a problem of Metacello than of the Configuration Browser. Are groups advertised/available in a config ? How would you even implement what you want ? > As a new user, I don't want to know about multiple locations for repositories. > If I have to, I don't want them to take up half the size of the window, and simultaneously > I don't want them hidden behind a context menu. Why not use a simple drop-down select > for the five repositories? That is a good alternative. > And don't use the full url as a selection name as that doesn't fit. > Just add the full url on hover Yes, good idea. > Can we target the configuration browser please? So no possibility to add your own > metarepo, just a tool that helps people getting started? > > Stephan For me, it solves the limited visibility. The other aspects are worth discussing too. Sven

Nov. 5, 2014

Re: [Pharo-dev] pane for repositories in the Configuration Browser

by kilon alios

I agree with both of you. I think what the Configuration Browser needs is a description pane that first of all gives information about the project and possible sources of documentaion and also has some advanced info for example its main repo, OS supported and Pharo versions supported. Obviously such pane could be made collapsable but on the other hand I find it very hard to believe that a new user wont need at least some basic info about the packages he tried to install. On Wed, Nov 5, 2014 at 12:46 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > Hmm. It solves the problem I definitely don't have with the configuration > browser. > It is supposed to be helpful and provide simple and working configurations. > That doesn't work as the configurations are not composable > (loading magritte and then loading seaside misses magritte-seaside). > > As a new user, I don't want to know about multiple locations for > repositories. > If I have to, I don't want them to take up half the size of the window, > and simultaneously > I don't want them hidden behind a context menu. Why not use a simple > drop-down select > for the five repositories? And don't use the full url as a selection name > as that doesn't fit. > Just add the full url on hover > > Can we target the configuration browser please? So no possibility to add > your own > metarepo, just a tool that helps people getting started? > > Stephan >

Nov. 5, 2014

Re: [Pharo-dev] pane for repositories in the Configuration Browser

by Stephan Eggermont

Hmm. It solves the problem I definitely don't have with the configuration browser. It is supposed to be helpful and provide simple and working configurations. That doesn't work as the configurations are not composable (loading magritte and then loading seaside misses magritte-seaside). As a new user, I don't want to know about multiple locations for repositories. If I have to, I don't want them to take up half the size of the window, and simultaneously I don't want them hidden behind a context menu. Why not use a simple drop-down select for the five repositories? And don't use the full url as a selection name as that doesn't fit. Just add the full url on hover Can we target the configuration browser please? So no possibility to add your own metarepo, just a tool that helps people getting started? Stephan

Nov. 5, 2014