June 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [pharo-project/pharo-core] ec95a6: 50074

by Marcus Denker

> On 01 Jun 2015, at 12:30, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > > > I see only changes about configuration when click on provided link too: > â > Â screencapture-github-com-pharo-project-pharo-co... <https://docs.google.com/file/d/0B-bMBVDOi3oTbTNINTFUZXlGU28/edit?usp=drive_…>â > Maybe it happens because you Marcus and Esteban are members of Pharo repo on github? > > No, I think it means that this update just updated the config but did not load anything. Marcus

June 1, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] ec95a6: 50074

by Sven Van Caekenberghe

> On 01 Jun 2015, at 12:30, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > > > I see only changes about configuration when click on provided link too: > â > screencapture-github-com-pharo-project-pharo-co... I think that is all that changed in that commit ;-) Taking one that contains code that I did myself: Commit: cf919fc630785f19768ebcbb5b41ef80c1f3526b https://github.com/pharo-project/pharo-core/commit/cf919fc630785f19768ebcbb… I can see each and every change at the method level. > â > Maybe it happens because you Marcus and Esteban are members of Pharo repo on github? > > > Cheers, > Alex > > > On Mon, Jun 1, 2015 at 11:59 AM, Esteban Lorenzanostebanlm(a)gmail.com> wrote: > >> On 01 Jun 2015, at 10:08, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >>> On 29 May 2015, at 22:32, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: >>> >>> >>> >>> 2015-05-29 18:43 GMT+02:00 Henrik Johansen <henrik.s.johansen(a)veloxit.no>: >>> Hey, at least the commit link to where one can inspect the actual changes is on the top now! >>> With better log messages, and the rest removed, it would actually almost be helpful... >>> >>> Cheers, >>> Henry >>> >>> >>> But that's the point: if you follow the github link, then you just observe: >>> - the changes about the configuration, >>> - the links to the issue tracker, through ScriptLoader >>> - a link to the smalltalkhub repository which is not really browsable >>> Not really the codeâ¦ >> >> >> ? If I click on >> >> https://github.com/pharo-project/pharo-core/commit/ec95a6bbb53327bccec2f4b8… >> >> I see the diff for this update. > > me too > >> >>> Untill all the projects are moved to github, this is somehow a regression. >>> >>>> On 29 May 2015, at 6:37 , Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: >>>> >>>> All the verbiage is just to announce that the real work is happening elsewhere. >>>> Maybe that's already informative enough to keep these message flowing ;) >>>> >>>> 2015-05-29 15:53 GMT+02:00 GitHub <noreply(a)github.com>: >>>> Branch: refs/heads/5.0 >>>> Home: https://github.com/pharo-project/pharo-core >>>> Commit: ec95a6bbb53327bccec2f4b8ebf8abc2f416c9b7 >>>> https://github.com/pharo-project/pharo-core/commit/ec95a6bbb53327bccec2f4b8… >>>> Author: Jenkins Build Server <board(a)pharo-project.org> >>>> Date: 2015-05-29 (Fri, 29 May 2015) >>>> >>>> Changed paths: >>>> A ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/baselines/baseline21_.st >>>> M ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/symbolic versions/development_.st >>>> M ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/symbolic versions/stable_.st >>>> A ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/versions/version1215_.st >>>> R ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/versions/version13_.st >>>> R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50073.st >>>> A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50074.st >>>> R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50073.st >>>> A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50074.st >>>> M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st >>>> >>>> Log Message: >>>> ----------- >>>> 50074 >>>> a MC >>>> >>>> http://files.pharo.org/image/50/50074.zip >>>> >>>> >>>> >>> >>> >> > >

June 1, 2015

Re: [Pharo-dev] shortcut change in pharo 50075

by Sean P. DeNigris

Nicolai Hess wrote > I hope we change that in PharoShortcuts, we should use one "Meta/Command" > key name, that is mapped to > Ctrl for win/linux > and > Cmd fo mac After re-reading the key descriptions on Wikipedia: http://en.wikipedia.org/wiki/Meta_key http://en.wikipedia.org/wiki/Command_key http://en.wikipedia.org/wiki/Windows_key IMO #meta is the only sensible name for "the appropriate key on Xyz platform", as it is not in use by modern keyboards and thus can be thought of abstractly. Command, which I too initially thought might work, doesn't seem like a great candidate because it means cmd on Mac ("command" is written on the key on my Macbook Air), so Windows users may naturally think that translates to the Win key, which appears in the same place on Windows keyboards, but serves a somewhat different function. ----- Cheers, Sean -- View this message in context: http://forum.world.st/shortcut-change-in-pharo-50075-tp4829460p4829746.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 1, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] ec95a6: 50074

by Aliaksei Syrel

I see only changes about configuration when click on provided link too: â screencapture-github-com-pharo-project-pharo-co... <https://docs.google.com/file/d/0B-bMBVDOi3oTbTNINTFUZXlGU28/edit?usp=drive_…> â Maybe it happens because you Marcus and Esteban are members of Pharo repo on github? Cheers, Alex On Mon, Jun 1, 2015 at 11:59 AM, Esteban Lorenzanostebanlm(a)gmail.com <estebanlm(a)gmail.com>> wrote: > > On 01 Jun 2015, at 10:08, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > On 29 May 2015, at 22:32, Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > > 2015-05-29 18:43 GMT+02:00 Henrik Johansen <henrik.s.johansen(a)veloxit.no>: > >> Hey, at least the commit link to where one can inspect the actual changes >> is on the top now! >> With better log messages, and the rest removed, it would actually almost >> be helpful... >> >> Cheers, >> Henry >> >> > But that's the point: if you follow the github link, then you just observe: > - the changes about the configuration, > - the links to the issue tracker, through ScriptLoader > - a link to the smalltalkhub repository which is not really browsable > Not really the codeâ¦ > > > > ? If I click on > > > https://github.com/pharo-project/pharo-core/commit/ec95a6bbb53327bccec2f4b8… > > I see the diff for this update. > > > me too > > > Untill all the projects are moved to github, this is somehow a regression. > > On 29 May 2015, at 6:37 , Nicolas Cellier < >> nicolas.cellier.aka.nice(a)gmail.com> wrote: >> >> All the verbiage is just to announce that the real work is happening >> elsewhere. >> Maybe that's already informative enough to keep these message flowing ;) >> >> 2015-05-29 15:53 GMT+02:00 GitHub <noreply(a)github.com>: >> >>> Branch: refs/heads/5.0 >>> Home: https://github.com/pharo-project/pharo-core >>> Commit: ec95a6bbb53327bccec2f4b8ebf8abc2f416c9b7 >>> >>> https://github.com/pharo-project/pharo-core/commit/ec95a6bbb53327bccec2f4b8… >>> Author: Jenkins Build Server <board(a)pharo-project.org> >>> Date: 2015-05-29 (Fri, 29 May 2015) >>> >>> Changed paths: >>> A >>> ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/baselines/baseline21_.st >>> M >>> ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/symbolic >>> versions/development_.st >>> M >>> ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/symbolic >>> versions/stable_.st >>> A >>> ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/versions/version1215_.st >>> R >>> ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/versions/version13_.st >>> R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/ >>> script50073.st >>> A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/ >>> script50074.st >>> R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/ >>> update50073.st >>> A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/ >>> update50074.st >>> M >>> ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st >>> >>> Log Message: >>> ----------- >>> 50074 >>> a MC >>> >>> http://files.pharo.org/image/50/50074.zip >>> >>> >>> >> >> > > >

June 1, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] ec95a6: 50074

by Esteban Lorenzano

> On 01 Jun 2015, at 10:08, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 29 May 2015, at 22:32, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com <mailto:nicolas.cellier.aka.nice@gmail.com>> wrote: >> >> >> >> 2015-05-29 18:43 GMT+02:00 Henrik Johansen <henrik.s.johansen(a)veloxit.no <mailto:henrik.s.johansen@veloxit.no>>: >> Hey, at least the commit link to where one can inspect the actual changes is on the top now! >> With better log messages, and the rest removed, it would actually almost be helpful... >> >> Cheers, >> Henry >> >> >> But that's the point: if you follow the github link, then you just observe: >> - the changes about the configuration, >> - the links to the issue tracker, through ScriptLoader >> - a link to the smalltalkhub repository which is not really browsable >> Not really the codeâ¦ > > > ? If I click on > > https://github.com/pharo-project/pharo-core/commit/ec95a6bbb53327bccec2f4b8… <https://github.com/pharo-project/pharo-core/commit/ec95a6bbb53327bccec2f4b8…> > > I see the diff for this update. me too > >> Untill all the projects are moved to github, this is somehow a regression. >> >>> On 29 May 2015, at 6:37 , Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com <mailto:nicolas.cellier.aka.nice@gmail.com>> wrote: >>> >>> All the verbiage is just to announce that the real work is happening elsewhere. >>> Maybe that's already informative enough to keep these message flowing ;) >>> >>> 2015-05-29 15:53 GMT+02:00 GitHub <noreply(a)github.com <mailto:noreply@github.com>>: >>> Branch: refs/heads/5.0 >>> Home: https://github.com/pharo-project/pharo-core <https://github.com/pharo-project/pharo-core> >>> Commit: ec95a6bbb53327bccec2f4b8ebf8abc2f416c9b7 >>> https://github.com/pharo-project/pharo-core/commit/ec95a6bbb53327bccec2f4b8… <https://github.com/pharo-project/pharo-core/commit/ec95a6bbb53327bccec2f4b8…> >>> Author: Jenkins Build Server <board(a)pharo-project.org <mailto:board@pharo-project.org>> >>> Date: 2015-05-29 (Fri, 29 May 2015) >>> >>> Changed paths: >>> A ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/baselines/baseline21_.st >>> M ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/symbolic versions/development_.st >>> M ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/symbolic versions/stable_.st >>> A ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/versions/version1215_.st >>> R ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/versions/version13_.st >>> R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50073.st <http://script50073.st/> >>> A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50074.st <http://script50074.st/> >>> R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50073.st <http://update50073.st/> >>> A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50074.st <http://update50074.st/> >>> M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st >>> >>> Log Message: >>> ----------- >>> 50074 >>> a MC >>> >>> http://files.pharo.org/image/50/50074.zip <http://files.pharo.org/image/50/50074.zip> >>> >>> >>> >> >> >

June 1, 2015

Re: [Pharo-dev] untypeable key combination

by Henrik Johansen

> On 30 May 2015, at 5:20 , Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > 2015-05-30 16:01 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com <mailto:sean@clipperadams.com>>: > Nicolai Hess wrote > > I don't fully understand what to change. > > If Spur will be ready for the next release, why don't we just wait... > > I would like to better understand what is the problem and I am sure > there is some kind of software pattern to prevent this > circular reference situation. A block usually references its outer context.* The default subscriber of a block is the object that defines it. Thus, if added to a Weak SubscriptionDictionary, the value/block (which is held strongly) references the key/subscriber (held weakly), and it never gets garbage collected. While the big selling point of ephemerons is to get notifications when an object is *about* to be GC'd instead of after it has been GC'd (so instead of the executor being a shadow copy of an object, the executor can be the object itself), they also solves the above by disregarding any references to the key from the value when checking liveliness. Cheers, Henry * The exception being "clean" blocks that do not reference inst vars / temps declared outside the block (which aren't of much use for announcements)

June 1, 2015

Re: [Pharo-dev] Metacello and #stable

by Stephan Eggermont

On 01/06/15 10:56, Andrei Chis wrote: > Moose still has a stable version that loads ok in Pharo 3. There is also > a jenkins build: https://ci.inria.fr/moose/job/moose-5.0/ > ConfigurationOfMoose is in the main moose repo > (http://www.smalltalkhub.com/#!/~Moose/Moose) Yes, we've done some work to ensure that the stable works. That is because none of the dependencies have already declared a new version stable that only works in Pharo4. At that moment, we need to introduce platform to get the right stable version in Pharo3. As we'll have multiple releases of Moose on Pharo 5, it makes sense to start getting more precise there. Stephan

June 1, 2015

Re: [Pharo-dev] Metacello and #stable

by Andrei Chis

Hi Dale, Thanks for your answer. Did not know stable is not a good choice for more complex configurations. Moose still has a stable version that loads ok in Pharo 3. There is also a jenkins build: https://ci.inria.fr/moose/job/moose-5.0/ ConfigurationOfMoose is in the main moose repo ( http://www.smalltalkhub.com/#!/~Moose/Moose) For now I fixed the issues we had by deleting a few versions from ConfigurationOfGlamour (ConfigurationOfGlamour-AndreiChis.211) Cheers, Andrei On Fri, May 29, 2015 at 12:14 AM, Dale Henrichs < dale.henrichs(a)gemtalksystems.com> wrote: > Andrei, > > 1) The old configuration load api is non-deterministic, especially when > used with large configurations, Metacello will not downgrade a package, so > if (using the old api) Metacello decides that a newer version of a > configuration is present, then it will use the newer (and possibly > incorrect version). Keep in mind that pre-loaded packages in Pharo can > influence this non-deterministic calculation. > > I don't know for certain that using the old API is the culprit. The only > way for me to understand where the issue might lie is for me to look at the > Transcript output of a load. > > 2) I'm not sure that Moose is loadable in Pharo3.0 ... If things are not > actively tested then they are likely to quit working over time and I'd > guess this is the case for Pharo3.0 and Moose. > > 3) using #stable is a very inaccurate way of specifying a symbolic > version. The Seaside folks have started using version-based symbolic > versions like: #'release3', #'release3.1', #'release3.2' a while ago and I > think this is a very good way to leverage symbolic versions ... #stable can > be changed and in the mind of the developer #stable is now version 4.0.0, > while a number of older configurations will consider #stable to be version > 3.0.0 ... it doesn't take long the #stable version universe to be > completely confused ... > > While I suspect that the current #stable version of Moose does not run on > Pharo3.0, if version-based symbolic versions had been used back then the > configurations would likely still be usable ... > > Again, I am just guessing ... analysis of the Transcript output would give > me better clues ... > > Using the new Metacello scripting API: > > Metacello new > configuration: 'Moose'; > version: #stable; > repository: '???'; > load > > does a load without without calculating the #currentVersion and should be > deterministic with respect to loaded versions ... this only addresses the > first point above. If points 2 or 3 are involved, then it may be more > difficult to solve the problem ... > > BTW, sorry for taking so long to get back to you ... in the last month > I've taken a long overdue vacation (and did not even open my laptop:) and > have been working exclusively on GemStone 3.3 ... I'm nearly finished with > my main commitments for GemStone 3.3 and as I come up for air, I'm working > off my email backlog:) > > Dale > > On 5/18/15 5:56 AM, Andrei Chis wrote: > >> Hi, >> >> If I specify a stable version for a platform (spec for: #'pharo3.x' >> version: '3.0.6'.), shouldn't Metacello load that version? >> >> Concrete use-case: loading ConfigurationOfMoose in Pharo 3 >> - ConfigurationOfMoose specifies version 5.0 as stable for Pharo 3 >> - ConfigurationOfMoose version 5.0 loads ConfigurationOfGlamour #stable >> - ConfigurationOfGlamour specifies version 3.0.6 as stable for Pharo 3 >> (spec for: #'pharo3.x' version: '3.0.6') >> >> Loading ConfigurationOfMoose [1] in Pharo 3 loads version 3.0.9 for >> ConfigurationOfGlamour. >> Updating Monticello leads to the same result. >> >> Did I misunderstood something about how monticello works? >> Any idea how to debug this? >> >> Cheers, >> Andrei >> >> [1] (ConfigurationOfMoose project version: #'stable') record loadDirective >> >> > >

June 1, 2015

Re: [Pharo-dev] styling in spotter preview broken ?

by Nicolai Hess

2015-06-01 10:39 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: > Does this happen, too, when you turn off AST based highlighting? > Yes, I think this is an issue on rubric. 50064 15605 Update Rubric > > > > On 30 May 2015, at 12:55, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > since 50064 some methods lost syntaxhighlight when previewed > > in spotter. > > This does not happens for all methods (but most of them) and I can not > see a pattern. > > Styling is lost on short and or long methods > >

June 1, 2015

Re: [Pharo-dev] styling in spotter preview broken ?

by Marcus Denker

Does this happen, too, when you turn off AST based highlighting? > On 30 May 2015, at 12:55, Nicolai Hess <nicolaihess(a)web.de> wrote: > > since 50064 some methods lost syntaxhighlight when previewed > in spotter. > This does not happens for all methods (but most of them) and I can not see a pattern. > Styling is lost on short and or long methods

June 1, 2015