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

[pharo-project/pharo-core]
by GitHub May 25, 2015

May 25, 2015

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

1 0

Why ConfigurationOfAthens is loading XML :(
by stepharo May 25, 2015

May 25, 2015

Hi guys ConfigurationOfAthens should not deal with loading SVG So the XML and SVG part of Athens should be moved to ConfigurationOfAthensSVG Can we remove the XML dependencies from Athens! https://pharo.fogbugz.com/default.asp?15603 Stef

1 0

Gofer upgrade error
by Leo May 25, 2015

May 25, 2015

I have a fresh image of Pharo 4 -just downloaded-. When I try Gofer upgrade I receive a MessageNotUnderstood: receiver of default is nil. What is happening? thanks

2 1

Pillar 0.56 : New features, new syntax
by Cyril Ferlicot May 25, 2015

May 25, 2015

Hello, today I created the version 0.56 of Pillar and with this version we'll need to do some changes, sorry. The first change is the numerator. The old numerator was too limited, so i changed it. Now if you put different files into the pillar.conf the numerator will not be reset at each files. The parameters 'startNumberingAtHeaderLevel:' and 'stopNumberingAtHeaderLevel:' are replace by 'level1:', 'level2:', 'level3:', 'level4:', 'level5:'. For now they can take 3 sub-parameters: 'numbering', 'size' and 'renderAs'. numbering: a boolean that say if this header level need to be take in account by the numerator. size: the number of level we want to render. You can put numbering at true and size at 0 if you want your numerator to be reset at a level without rendering the number of this level. renderAs: can be number, roman, letter or upperLetter. Example: pillar.conf: { 'level1': { 'numbering': true, 'size': 1, 'renderAs': 'roman' }, 'level2': { 'numbering': true, 'size': 2, 'renderAs': 'number' }, 'level3': { 'numbering': true, 'size': 1, 'renderAs': 'upperLetter' }, 'level4': { 'numbering': true, 'size': 2, 'renderAs': letter }, 'level5': { 'numbering': false }, } document.pillar: ! Example !! Introduction !!! Beginning !!! Example - Intro !!!! Example 1 !!!! Example 2 !!!!! With X !!!!! With Y !! Explanation Result: I. Example I.1. Introduction A. Beginning B. Example - Intro B.a. Example 1 B.b. Example 2 With X With Y I.2. Explanation In the future we could also add feature like 'delimiter'. The second main change is the Internal Links. Now when you want to reefer to an anchor, a figure or a script you'll need to use *@anchor* instead of *anchor*. I'm sorry for that but that's the easiest way to implement the inter-files links. And so the last main change is the Inter-files links ! Imagine you're writing a book. You have a directory 'Chapter1' which contains the file 'chapter1.pillar' and a directory 'Chapter2' with a file 'chapter2.pillar'. If you want to make a reference to the chapter 1 in the chapter 2 you can create an interfile link you can now use the syntax: *../Chapter1/chapter1.pillar* But be careful ! Remember that pillar can export in different format. And you can export a group of file as separate output files or as one file. So if you don't use an Alias your link will not be render if you export as one output file in LaTeX. And if you export in LaTeX or HTML or Markdown as one output file and you don't have an anchor on your link, the link will be vanish. So I recommend to use inter file links like this: *Chapter 1>../Chapter1/chapter1.pillar@cha:chapter1* when cha:chapter1 is an anchor you need to create at the beginning of the chapter 1. 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 -- Cheers Cyril Ferlicot

3 6

[pharo-project/pharo-core]
by GitHub May 24, 2015

May 24, 2015

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

1 0

[pharo-project/pharo-core] 60ac1f: 50063
by GitHub May 24, 2015

May 24, 2015

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

1 0

Lectures in africa :)
by stepharo May 24, 2015

May 24, 2015

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

4 3

Re: [Pharo-dev] New Collections for Pharo
by stepharo May 24, 2015

May 24, 2015

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

1 0

Best practice for overwriting methods in other classes
by Kasper Osterbye May 24, 2015

May 24, 2015

I have now twice in two different situations felt a need to "steal" a method in Nautilus and make that method an extension method in my own package. In situation A, I wanted to steal the #buildCommentPane to use a different Morph for class comments, In situation B, Sergio and I needed to redefine #getComments and #addComments:notifying: to fill out behaviour for package comments. What is the kosher way to work and contribute in such situations? I guess it will also pop up in situations outside of Nautilus. -- View this message in context: http://forum.world.st/Best-practice-for-overwriting-methods-in-other-classe… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

4 3

[pharo-project/pharo-core]
by GitHub May 24, 2015

May 24, 2015

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

1 0