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

PBE - Updated -2.8 - overlapping windows
by Daniel Roe May 27, 2015

May 27, 2015

PBE- Updated Section 2.8 This section asks you to open both a Playground and a Transcripts window but wants the Playground window just overlapping the Transcript window. I do that with a Transcript show: 3 + 4 entry in the Playground and, sure enough, a 7 appears in the Transcript window. But... what was the point of asking you to overlap the windows? What have I missed? As an aside, the answers and helpful hints I have received from my questions have been really "helpful". What a concept. Dan

3 2

Roassal-Woden on mouse events
by Lusa Nicolas May 26, 2015

May 26, 2015

Hi, until now was working with the interaction on roassal-woden only with the RWMouseButtonDown event, but I would like to distinguish the left from the right click (which right now is not possible, correct me if I am wrong please). I took a look to the code which is handling the mouse events but it looks like I have to modify classes of roassal-woden itself if I want that to work. Any hint/tip on how to do it trying not to impact your classes? Cheers, Nicolas

2 2

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

May 26, 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

6 11

PharoCommonTools methods
by Matthieu Lacaton May 25, 2015

May 25, 2015

Hello everyone, It's probably a silly question but there is something I don't understand in the PharoCommonTools class. There are many methods in this class that i can't find in the image. For example, *PharoCommonTools >> workspaceTool* refers to "*self workspace*" but I can't find any method named workspace in this class or its super classes. And it is the same for all the other tools. What am I missing ? :s Thanks, Matthieu

4 4

Accessibility?
by Avdi Grimm May 25, 2015

May 25, 2015

Some of the discussions we've had here, particularly with regard to pointing-and-clicking being the primary, and sometimes only, way to do something, made me wonder: are there any projects in progress for making Pharo accessible to the blind or vision-impaired? -- Avdi Grimm http://avdi.org

3 2

Lectures in africa :)
by stepharo May 25, 2015

May 25, 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

5 5

Not Pharo related - how does one respond to a message
by Daniel Roe May 25, 2015

May 25, 2015

Please allow me this one non-Pharo message. I am not that familiar with these message boards. When I see a message that I want to respond to how do I do that? I've been going to my email program - hotmail - and pasting in the subject line - copying and pasting any text that I want to include in my reply - writing a reply and then sending it. I can't believe that there's now a much more efficient way to do this. Enlighten me, please. Dan

4 3

PBE - Updated - section 2.10 System Browser
by Daniel Roe May 25, 2015

May 25, 2015

I am running Pharo 4.0, I think. I go to section 2.10 of the updated PBE (claimed to be for Pharo 4.0) which deals with The System Browser. I click on the background and get the World menu - I click on System Browser and get Nautilus instead of the System Browser (???). OK, so I search around and eventually find my way to printString. Two questions: 1) What is Nautilus - did I miss something here?, and 2) What are the shaded right facing triangles pointing to various menu entries trying to tell me? I tried to warn you - get ready for just a truck load of noobie questions. Dan

3 3

Garage and SQLite file databases, general project structure
by Torsten Bergmann May 25, 2015

May 25, 2015

Hi Guille, I had a short look at Garage [1]. Nice initiative! Looks like using a file is not supported for the SQLite3 backend in Garage: GADriver fromConnectionString: 'sqlite3://file://C:/temp/test.db' GADriver fromConnectionString: 'sqlite3://C:/temp/test.db' Maybe GASqlite3Driver>>fromConnectionString: could be adopted, but the conversion to a Zn URL already removes some stuff. (Ab)using the schema in the URL as a driverID is nice - but prevents the use of file:// schema. How can one construct a file db? Also I do not understand: while "Garage-Postgres" uses the Postgres project PostgresV2 as a backend the "Garage-Sqlite3" does not use NBSqlite3 or SQlite3 projects as backend. So "GASqlite3FFI" copies many methods of the original NBSQLite3 project from Pierce and myself and is therefore like an own fork now. Also the name FFI is misleading as it uses NativeBoost instead of FFI ... Also it would be good if the project would be layered, we could have a "Garage-Core" and "Garage-Tests-Core" with "Garage-Mysql" and "Garage-Tests-Mysql" for the fixtures. The idea is always to be able to load runtime code without tests for production code. Thanks Torsten [1] http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2015-May/01919…

5 10

Is the Playground the Workspace?â
by Daniel Roe May 24, 2015

May 24, 2015

That little black arrow... Aha! Now I have learned something useful. I realize that the updating of Pharo is important but it would only be better if the documentation could be kept current as well. Thanks again... Dan

2 1