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

Re: [Pharo-dev] [Pharo-users] [Moose-dev] Pillar 0.56 : New features, new syntax

by Cyril Ferlicot

No problem! Think like this happen easily. Yeah that's right. I think I know where is the error. I'll correct that tomorrow if I have time. Thank you for your feedback! On 25 May 2015 at 04:03, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > Aah silly me, I still had the old version of Pillar. Many apologies! > > Now it works, but I found a bug: do a find for âshown in Section 5.3.3â in the same html file. The section title there is V.3.C. So it should say âshown in Section V.3.C.â, right? > >> On May 24, 2015, at 22:17, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: >> >> Hi, >> 2 possibility: >> - You have an old version of Pillar >> - You check the wrong file. >> >> With the version 0.47 of Pillar we changed the way files was generated. >> Before if you had a file foo.pillar exported foo.pillar.html >> but since the version 0.47 you get foo.html only. >> >> So check if you have a file "Fuel.html" and if you don't have it just >> execute ./download.sh before the ./compile.sh >> >> You should get that : >> https://ci.inria.fr/pharo-contribution/view/Books/job/EnterprisePharoBook/l… >> >> :) > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > > -- Cheers Cyril Ferlicot

May 25, 2015

Re: [Pharo-dev] [Moose-dev] [Pharo-users] Pillar 0.56 : New features, new syntax

by Johan Fabry

Aah silly me, I still had the old version of Pillar. Many apologies! Now it works, but I found a bug: do a find for âshown in Section 5.3.3â in the same html file. The section title there is V.3.C. So it should say âshown in Section V.3.C.â, right? > On May 24, 2015, at 22:17, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > Hi, > 2 possibility: > - You have an old version of Pillar > - You check the wrong file. > > With the version 0.47 of Pillar we changed the way files was generated. > Before if you had a file foo.pillar exported foo.pillar.html > but since the version 0.47 you get foo.html only. > > So check if you have a file "Fuel.html" and if you don't have it just > execute ./download.sh before the ./compile.sh > > You should get that : > https://ci.inria.fr/pharo-contribution/view/Books/job/EnterprisePharoBook/l… > > :) ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

May 25, 2015

Re: [Pharo-dev] [Pharo-users] Pillar 0.56 : New features, new syntax

by Cyril Ferlicot

Hi, 2 possibility: - You have an old version of Pillar - You check the wrong file. With the version 0.47 of Pillar we changed the way files was generated. Before if you had a file foo.pillar exported foo.pillar.html but since the version 0.47 you get foo.html only. So check if you have a file "Fuel.html" and if you don't have it just execute ./download.sh before the ./compile.sh You should get that : https://ci.inria.fr/pharo-contribution/view/Books/job/EnterprisePharoBook/l… :) On 25 May 2015 at 03:10, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > Cyril, thanks for doing all of this, but now the links seem to be broken, at least for the html export on my machine. :-( I am working on the Fuel chapter, and I see that inter-file links are broken in the first paragraph, and intra-file links are broken e.g. figure 6.1. Example of changes to a class. > > Could you have a look? The pillar file is in github, the Fuel.pillar.html result of ./compile.sh is here: > https://dl.dropboxusercontent.com/u/31426460/Fuel.pillar.html > > Thanks in advance! > >> On May 22, 2015, at 18:12, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: >> >> I already changed the links on Enterprise Pharo (you can find a table >> with the list of the inter-files links on the README.md) >> >> On last thing for the people who write book for SquareBracketAssociates: >> It would be good to have some conventions, so if you create anchors >> use this form : >> @sec:nameOfSection for a section >> @cha:nameOfTheChapter for a title of chapter >> @fig:nameOfFigure for a figure >> @spt:nameOfTheScript for a script > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > > -- Cheers Cyril Ferlicot

May 25, 2015

Re: [Pharo-dev] [Pharo-users] Pillar 0.56 : New features, new syntax

by Johan Fabry

Cyril, thanks for doing all of this, but now the links seem to be broken, at least for the html export on my machine. :-( I am working on the Fuel chapter, and I see that inter-file links are broken in the first paragraph, and intra-file links are broken e.g. figure 6.1. Example of changes to a class. Could you have a look? The pillar file is in github, the Fuel.pillar.html result of ./compile.sh is here: https://dl.dropboxusercontent.com/u/31426460/Fuel.pillar.html Thanks in advance! > On May 22, 2015, at 18:12, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > I already changed the links on Enterprise Pharo (you can find a table > with the list of the inter-files links on the README.md) > > On last thing for the people who write book for SquareBracketAssociates: > It would be good to have some conventions, so if you create anchors > use this form : > @sec:nameOfSection for a section > @cha:nameOfTheChapter for a title of chapter > @fig:nameOfFigure for a figure > @spt:nameOfTheScript for a script ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

May 25, 2015

Depending on a project with baseline

by Yuriy Tymchuk

Hi, for some time now I was using baseline in my projects for basing dependency support and git tags for versioning the releases. Then Iâve just pointed to the releases from a configuration to be able to put my project in the conf. browser. Now when I what to depend on a project which has a baseline, can I depend directly, or should I make a configuration. In my opinion the latter one is a pain, as essentially I just putt a version methods and then provide there urls with same name git tags. Cheers! Uko

May 24, 2015

Re: [Pharo-dev] [Reflectivity] Progress for Breakpoints

by Marcus Denker

> - code gen for the complex hooks (need to add name analysis for hooks for that) > This is now in 50063. It does work (for now) only for for #object as a parameter and not yet on all kinds of nodes, but the machinery is workingâ¦ For a very simple example, see #testLinkWithMetaArg: We can define a Metalink were we hand over reified information from the base level to the meta object: link := MetaLink new metaObject: self; âmeta object is the test class itself" selector: #tagExec:; âwe call that method, it just stored the parameter in an ivar tag" arguments: #(object). âarguments are defined by symbols, there is plug architecture to define them" in this case, it is the object at runtime of the method where we install the link in. Lets grab a send node: sendNode := (ReflectivityExamples>>#exampleMethod) ast body statements first value. install the link: sendNode link: link. #tagExec: is just recording the parameter, so this will be green: instance := ReflectivityExamples new. self assert: (instance exampleMethod = 5). self assert: (tag = instance). And it works! TODO next: - add all possible reifications (#arguments, #context, #newvalue, #nameâ¦. depending on where the link is installed on, we are interesting in different things). Marcus

May 24, 2015

[pharo-project/pharo-core]

by GitHub

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

May 24, 2015

[pharo-project/pharo-core] 60ac1f: 50063

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 60ac1fad1c47ef3f3225063e73988b3562d2228e https://github.com/pharo-project/pharo-core/commit/60ac1fad1c47ef3f3225063e… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-05-24 (Sun, 24 May 2015) Changed paths: M OpalCompiler-Core.package/OCASTTranslator.class/instance/visitor/visitNode_.st M Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tagging/tagExec.st A Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tagging/tagExec_.st A Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - links/testLinkWithMetaArg.st M Reflectivity.package/HookGenerator.class/instance/ast manipulation/encloseInBlock_.st A Reflectivity.package/RFReification.class/instance/acccessing/node_.st R Reflectivity.package/RFReification.class/instance/acccessing/optimize.st R Reflectivity.package/RFReification.class/instance/accesing/node_.st A Reflectivity.package/RFReification.class/instance/generate/genForRBMessageNode.st A Reflectivity.package/RFReification.class/instance/testing/optimize.st M Reflectivity.package/RFSemanticAnalyzer.class/instance/visiting/visitNode_.st M Reflectivity.package/extension/BlockClosure/instance/ctxtEnsure_.st A Reflectivity.package/extension/RBProgramNode/instance/afterHooks.st A Reflectivity.package/extension/RBProgramNode/instance/beforeHooks.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50062.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50063.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50062.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50063.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50063 15599 enable code generation for arguments passed to meta objects https://pharo.fogbugz.com/f/cases/15599 http://files.pharo.org/image/50/50063.zip

May 24, 2015

Re: [Pharo-dev] [Pharo-users] Lectures in africa :)

by Tudor Girba

This is a fantastic effort! Thanks a lot, Doru On Sun, May 24, 2015 at 5:27 PM, Sergio Fedi <sergio.fedi(a)gmail.com> wrote: > Awesome! > > > On Sun, May 24, 2015 at 5:44 AM, Alexandre Bergel <alexandre.bergel(a)me.com > > wrote: > >> Excellent! >> Thanks to share this impressive effort with us >> >> cheers, >> Alexandre >> >> >> > On May 24, 2015, at 7:47 AM, stepharo <stepharo(a)free.fr> wrote: >> > >> > Hi guys >> > >> > I m back to europe after one week to senegal. >> > There I gave lectures to Dakar 3 h >> > OO advanced design >> > seaside >> > and met Pr. Alassane Bah an old Smalltalker that is eager to push Pharo. >> > I gave him my lectures and we will see what we will do. >> > >> > Then at Saint-Louis I gave lectures two times 3 h. >> > They want to have an advanced oop lectures. >> > >> > Students loved it. >> > >> > I gave a presentation of Pharo to all the reseach group leader of the >> LIRIMA a lab join with inria and several countries. >> > People from Yaounde want to do something with Pharo :) >> > >> > So be ready to get newbies soon. >> > >> > Stef >> > >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> > -- www.tudorgirba.com "Every thing has its own flow"

May 24, 2015

Re: [Pharo-dev] New Collections for Pharo

by stepharo

Hi did you write tests? did your implementation propose APIs that are compatible with the Collection API? Stef

May 24, 2015