- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Moose-dev] Pillar 2.0.0: Introduction of PetitPillar

by Ferlicot D. Cyril

Le 11/09/2015 15:49, Alexandre Bergel a Ã©crit : > Hi Cyril, > > I use Pillar for AgileVisualization. One problem I have is that the book contains many code snippets. How can I run all the code snippet in order to spot error? Is there an easy way for that? > > Alexandre > > > You mean you you use a lot of scripts with a "eval=true" parameter ? If you want an easy way to debug code into scripts you can remove the "--headless" parameter of the "pharo" script will you test your chapter. During the export if you have an exception the image will open a debugger with the context of the script. -- Cheers Cyril

Sept. 11, 2015

Re: [Pharo-dev] Running a test method in Nautilus

by Peter UhnÃ¡k

> > If the test fail, it does not open a debugger. This happens when I click on the button next to the _class_, however I've never experienced such problem with the button next to a _method_. Peter On Fri, Sep 11, 2015 at 4:21 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > I can run a test method by pressing the button located on the left hand > side of the method name. If the test fail, it does not open a debugger. I > need to run it a second time. This is a rather odd behavior. > Am I the only one to experience this? > > Side question: > I try to check on the bug tracker if there is something about that, but I > was not able to find it. I entered in the search input field the tree > keywords: test button nautilus > The result is > https://pharo.fogbugz.com/f/search/?sSearchFor=test+button+nautilus > However, this indicates many closed issues. How can I filter out the close > issues? > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

Sept. 11, 2015

Catalog does not update to include MessageFlowBrowser

by Torsten Bergmann

Hi, ConfigurationOfMessageFlowBrowser is in http://smalltalkhub.com/#!/~Pharo/MetaRepoForPharo50 for a week now but still not included in http://catalog.pharo.org According to the description there is a daily catalog job - but so far no results. It is not included although the config includes the necessary catalog methods. - Is MetaRepoForPharo50 already recognized? - Is it possible to "manually" trigger the catalog generation in case a new project is done? Anyone able to look into this? Thx T.

Sept. 11, 2015

Running a test method in Nautilus

by Alexandre Bergel

Hi! I can run a test method by pressing the button located on the left hand side of the method name. If the test fail, it does not open a debugger. I need to run it a second time. This is a rather odd behavior. Am I the only one to experience this? Side question: I try to check on the bug tracker if there is something about that, but I was not able to find it. I entered in the search input field the tree keywords: test button nautilus The result is https://pharo.fogbugz.com/f/search/?sSearchFor=test+button+nautilus However, this indicates many closed issues. How can I filter out the close issues? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 11, 2015

Re: [Pharo-dev] [Moose-dev] Pillar 2.0.0: Introduction of PetitPillar

by Peter UhnÃ¡k

On Fri, Sep 11, 2015 at 3:49 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi Cyril, > > I use Pillar for AgileVisualization. One problem I have is that the book > contains many code snippets. How can I run all the code snippet in order to > spot error? Is there an easy way for that? > > Alexandre This probably doesn't apply since you have your scripts directly in the pillar files... but for the Layout chapter scripts I've used this (It goes through all "Layout/figures/*.st" files, compiles them and executes them.) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |root scripts| root := '/home/peter/prog/agilevisualization/book-skeleton' asFileReference. scripts := (root / 'Layout' / 'figures') children select: [ :each | each name endsWith: '.st' ]. scripts do: [ :each | Transcript logCr: each name. nil class compiler source: each contents; evaluate ]. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Peter

Sept. 11, 2015

Re: [Pharo-dev] [Moose-dev] Pillar 2.0.0: Introduction of PetitPillar

by Alexandre Bergel

Hi Cyril, I use Pillar for AgileVisualization. One problem I have is that the book contains many code snippets. How can I run all the code snippet in order to spot error? Is there an easy way for that? Alexandre > On Sep 11, 2015, at 9:06 AM, Ferlicot D. Cyril <cyril.ferlicot(a)gmail.com> wrote: > > Hi everyone! > Yes, a new version of Pillar, again! > > With this version we removed the old parser of Pillar to introduce > PetitPillar base on PetitParser. > This parser is slower than the previous one but we will be able to > improve his speed. > We will also be able to improve Pillar at the parser level, which was > impossible before. So we will be able to remove some hacks and improve > the experience of the users. > If you are good in parser and you want to contribute to his improvement, > feel free to help, we have a lot of tests to help. This is my first > parser so I am sure it have a lot of rooms for improvement. > > -- > Cheers > Cyril > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 11, 2015

Re: [Pharo-dev] Bootstrap dependency, System-Announcements --> PragmaCollector

by Ben Coman

On Fri, Sep 11, 2015 at 5:01 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > I think SystemNavigation should essentially dissolve in the near future. What timeline do you consider *near* ? ;) Should we go with my last proposal in the meantime? > Moose used to have one of these some 10 years ago, and now all queries are > implemented as fluent APIs distributed throughout the model classes. Could you clue me in on the "model" classes? cheers -ben > On Thu, Sep 10, 2015 at 8:29 PM, stepharo <stepharo(a)free.fr> wrote: >> >> Pragma should not depend on SystemNavigation. The inverse >> >> >> Le 10/9/15 19:44, Ben Coman a Ã©crit : >> >>> On Fri, Sep 11, 2015 at 12:43 AM, Max Leske <maxleske(a)gmail.com> wrote: >>>>> >>>>> On 10 Sep 2015, at 17:22, Ben Coman <btc(a)openInWorld.com> wrote: >>>>> >>>>> The bootstrap-dependency graph and report [1] mark dependency >>>>> System-Announcements --> PragmaCollector for pruning. This is due to... >>>>> >>>>> SystemAnnouncer>>restoreAllNotifications >>>>> | collector | >>>>> self reset. >>>>> collector := PragmaCollector filter: [ :pragma | >>>>> pragma keyword = #systemEventRegistration ]. >>>>> collector reset. >>>>> collector do: [ :pragma | >>>>> pragma methodClass theNonMetaClass perform: pragma >>>>> selector ] >>>>> >>>>> Browsing around I came to understand that PragmaCollector is useful as >>>>> a pragma cache, but here the collector is thrown away, so that >>>>> facility is not needed. A key part is "collector reset" which does... >>>>> self class allSystemPragmas >>>>> do: [:pragma | self addPragma: pragma] >>>>> >>>>> where the #addPragma: evaluates the initialize'd #filter: block. Now >>>>> it seems that #allSystemPragmas might fit nicely on Pragma rather than >>>>> PragmaCollector >>>>> such that the following should be equivalent... >>>>> >>>>> SystemAnnouncer>>restoreAllNotifications >>>>> | systemPragmas | >>>>> self reset. >>>>> systemPragmas := Pragma allSystemPragmas collect: [ :pragma | >>>>> pragma keyword = #systemEventRegistration ]. >>>>> systemPragmas do: [ :pragma | >>>>> pragma methodClass theNonMetaClass perform: pragma >>>>> selector >>>>> >>>> Cool. I like that better. >>>> >>>>> However #allSystemPragmas depends on SystemNavigation, so is it be >>>>> okay for Pragma to depend on SystemNavigation? >>>> >>>> Spontaneously Iâd say that SystemNavigation should depend on Pragma or >>>> PragmaCollector for looking up pragmas, not the other way around. >>> >>> So you mean something like... >>> >>> SystemAnnouncer>>restoreAllNotifications >>> self reset. >>> SystemNavigation allPragmasNamed: #systemEventRegistration do: >>> [ :pragma | >>> pragma methodClass theNonMetaClass perform: pragma >>> selector ]. >>> >>> where... >>> >>> SystemNavigation>>allPragmasNamed: symbol do: aBlock >>> | systemPragmas | >>> systemPragmas := >>> self allSystemPragmas collect: [ :pragma | pragma keyword >>> = symbol ]. >>> systemPragmas do: [ :pragma | >>> pragma methodClass theNonMetaClass perform: pragma >>> selector >>> >>> SystemNavigation>>allSystemPragmas >>> ^ (Array >>> streamContents: [:stream | >>> self allBehaviorsDo: [:behavior | >>> Pragma >>> withPragmasIn: behavior >>> do: [:pragma | stream nextPut: pragma]]]) >>> >>> cheers -ben >>> >>> >>>>> Actually, class side of Pragma has several #named:in: like methods, so >>>>> something like the following would be neat... >>>>> SystemAnnouncer>>restoreAllNotifications >>>>> self reset. >>>>> Pragma allNamed: #systemEventRegistration do: [ :pragma | >>>>> pragma methodClass theNonMetaClass perform: pragma >>>>> selector ].

Sept. 11, 2015

Pillar 2.0.0: Introduction of PetitPillar

by Ferlicot D. Cyril

Hi everyone! Yes, a new version of Pillar, again! With this version we removed the old parser of Pillar to introduce PetitPillar base on PetitParser. This parser is slower than the previous one but we will be able to improve his speed. We will also be able to improve Pillar at the parser level, which was impossible before. So we will be able to remove some hacks and improve the experience of the users. If you are good in parser and you want to contribute to his improvement, feel free to help, we have a lot of tests to help. This is my first parser so I am sure it have a lot of rooms for improvement. -- Cheers Cyril

Sept. 11, 2015

[pharo-project/pharo-core]

by GitHub

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

Sept. 11, 2015

[pharo-project/pharo-core] 127a47: 50320

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 127a47eee1c4b21d93a52699da70b0ab2343f23e https://github.com/pharo-project/pharo-core/commit/127a47eee1c4b21d93a52699… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-11 (Fri, 11 Sep 2015) Changed paths: M ConfigurationOfVersionner.package/ConfigurationOfVersionner.class/instance/symbolic versions/stable_.st A ConfigurationOfVersionner.package/ConfigurationOfVersionner.class/instance/versions/version2134_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50319.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50320.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50319.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50320.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Versionner-Core-Commands.package/VSBrowseVersionCommand.class/instance/execute/execute.st M Versionner-Core-Commands.package/VSSaveProjectCommand.class/instance/execute/execute.st M Versionner-Core-DependenciesModel.package/MCModel2MTModelVisitor.class/instance/visiting/visitMCVersion_.st M Versionner-Core-DependenciesModel.package/MTProject.class/definition.st A Versionner-Core-DependenciesModel.package/MTProject.class/instance/accessing/announcer.st M Versionner-Core-DependenciesModel.package/VersionnerToolBox.class/instance/spec creation/projectSpecFromRequiredProject_.st M Versionner-Core-Model.package/MBConfigurationRoot.class/definition.st A Versionner-Core-Model.package/MBConfigurationRoot.class/instance/accessing/announcer.st A Versionner-Core-Model.package/MBConfigurationRoot.class/instance/initialize-release/initialize.st M Versionner-Spec-Browser.package/VersionnerSpecBrowser.class/instance/accessing/title.st A Versionner-Spec-Browser.package/VersionnerSpecBrowser.class/instance/accessing/toolName.st A Versionner-Spec-Browser.package/VersionnerSpecBrowser.class/instance/api/aboutText.st A Versionner-Spec-Browser.package/VersionnerSpecBrowser.class/instance/api/aboutTitle.st M Versionner-Tests-Core-Commands.package/VSReleaseDevelopmentVersionCommandTest.class/instance/expected results/expectedTestResolveSymbolicVersionInResult.st Log Message: ----------- 50320 16546 Integrate Versionner https://pharo.fogbugz.com/f/cases/16546 http://files.pharo.org/image/50/50320.zip

Sept. 11, 2015