- Pharo-users - lists.pharo.org

Pharo running on Pi - video
by Torsten Bergmann May 27, 2015

May 27, 2015

Made a video of Pharo running on a Raspberry Pi with small Tontec 3,5'' display: https://www.youtube.com/watch?t=16&v=sfxFqQIuawg

1 0

Pointer drawing method?
by Laura Risani May 27, 2015

May 27, 2015

Hi all, Is there a method that returns a diagonal arrow like the ambient's pointer? Best, Laura

4 5

How to update to Pharo 5 in Ubuntu 14.04 ?
by Dimitris Chloupis May 27, 2015

May 27, 2015

I have tried to use sudo apt-get update , but when i open pharolauncher using the pharo command in the terminal i see no option to download a pharo 5 image, Any clue how I can update it ?

2 2

Fwd: [cormas] [Cormas] Proposition de stage en informatique
by Serge Stinckwich May 27, 2015

May 27, 2015

Hi all, this is a proposal from a student internship in Pharo in order to build a specific UML editor for multi-agent simulation. Sorry this is only in French and Spanish, but english-speaking student are welcome also. Regards, ---------- Forwarded message ---------- From: Pierre Bommel <bommel(a)cirad.fr> Date: 2015-05-27 1:26 GMT+02:00 Subject: [cormas] [Cormas] Proposition de stage en informatique To: Cormas <cormas(a)cirad.fr> Bonjour, hello, hola, Please find a proposal for an internship in Computer Science to work on a UML editor for Cormas. Sorry but it is in french and in spanish.. Pierre ______ FranÃ§ais ______ Proposition de stage en informatique â Conception dâun Ã©diteur de diagramme de classes UML pour lâimplÃ©mentation de modÃ¨les multi-agents - Dans le cadre du dÃ©veloppement de sa plateforme de modÃ©lisation et simulation multi-agent, Cormas (http://cormas.cirad.fr) lâUnitÃ© de Recherche GREEN du Cirad (http://ur-green.cirad.fr) propose un stage indemnisÃ© de 6 mois pour un Ã©tudiant en informatique pour dÃ©velopper un module de Cormas. Ce dÃ©veloppement informatique consiste Ã mettre au point un Ã©diteur graphique permettant de dessiner un diagramme de classes UML et de gÃ©nÃ©rer du code SmallTalk (en Pharo, langage de programmation open-source) de la structure du modÃ¨le en se rÃ©fÃ©rant au standard "Executable UML" (xUML) proposÃ© par Mellor & Balcer (2002) and adoptÃ© par lâOMG (2008). Pour ce travail, nous ne cherchons pas un Ã©diteur exhaustif intÃ©grant tous les Ã©lÃ©ments dÃ©crits par UML2. Pour cet Ã©diteur, les Ã©lÃ©ments du mÃ©ta-modÃ¨le proposÃ©s seront limitÃ©s Ã : la classe, ses attributs et ses mÃ©thodes (dÃ©claration), la spÃ©cialisation de classes et les associations. Les associations sont simples (uniquement binaires) et sont dÃ©finies par leur nom et par leurs extrÃ©mitÃ©s qui comportent chacune un nom de rÃ´le, une valeur de multiplicitÃ© et la navigabilitÃ©. Cormas Ã©tant un framework, le modÃ¨le crÃ©Ã© par un utilisateur doit sâancrer sur des classes prÃ©dÃ©finies disponibles dans Cormas. A la fin de la conception de son modÃ¨le, lâutilisateur devra Ãªtre invitÃ© Ã rattacher les classes quâil a crÃ©Ã©es aux classes prÃ©dÃ©finies. Dans ce cas, les propriÃ©tÃ©s hÃ©ritÃ©es (mÃ©thodes, associations, attributs, ...) devront Ãªtre spÃ©cifiÃ©es dans le diagramme conceptuel de lâutilisateur qui pourra Ãªtre affichÃ© de faÃ§on indÃ©pendante du framework. Outre la crÃ©ation dynamique du squelette des classes, le stagiaire devra porter une attention particuliÃ¨re aux associations entre classes uni ou bi-directionnelles qui seront traduites en attributs nommÃ©s selon le rÃ´le de lâextrÃ©mitÃ© de lâassociation (on parle parfois dâassociation dÃ©gÃ©nÃ©rÃ©e pour laquelle le rÃ´le de lâextrÃ©mitÃ© opposÃ©e est traduit en attribut). Ne seront pas prises en compte les classes-associations, ni les associations n-aires, ni les associations qualifiÃ©es. Cet Ã©diteur permettra Ã©galement de rÃ©-afficher un modÃ¨le dÃ©jÃ sauvegarder mais aussi de proposer de gÃ©nÃ©rer un nouveau diagramme Ã partir dâun modÃ¨le dÃ©jÃ implÃ©mentÃ© (rÃ©tro-ingÃ©nierie). Par ailleurs, un Ã©diteur de diagramme dâactivitÃ© xUML est dÃ©jÃ disponible dans Cormas (bommel et al, 2014). En sÃ©lectionnant une mÃ©thode de son diagramme de classes, lâutilisateur pourra alors dessiner le comportement de cette mÃ©thode en dÃ©crivant la succession des activitÃ©s et des conditions boolÃ©ennes. Le dÃ©veloppement de lâÃ©diteur UML devra se faire sous Roassal, un moteur puissant de visualisation (http://objectprofile.com/Roassal.html) disponible pour Pharo. En option et si le stagiaire en a le temps, cette application pourra aussi Ãªtre traduite en VisualWorks : un autre langage Smalltalk sur lequel Cormas tourne actuellement. Avec la sortie rÃ©cente de Roassal2, la mise au point de ce module UML permettra dâaccÃ©lÃ©rer la migration de Cormas sous Pharo. Enfin, le stagiaire sera libre de gÃ©nÃ©rer le code XML (XMI) dâun modÃ¨le pour pouvoir le lire dans un autre Ã©diteur. ______ DurÃ©e : 6 mois (ou moins si nÃ©cessaire) Gratification : 485,10 â¬ par mois. Lieu : pas dâaccueil prÃ©vu au Cirad. LâÃ©tudiant travaillera dans son laboratoire mais des contacts rÃ©guliers seront proposÃ©s. Contacts : Pierre Bommel (bommel(a)cirad.fr) et GrÃ©goire Leclerc (Leclerc(a)cirad.fr) Profil de candidature : Etudiant en Informatique, License ou Master, ayant un goÃ»t pour la modÃ©lisation et la simulation. LâÃ©tudiant doit avoir de bonnes connaissances des concepts de la modÃ©lisation objet et dâUML. Des compÃ©tences en programmation Smalltalk devront Ãªtre acquises. ______ EspaÃ±ol ______ Propuesta de prÃ¡ctica de informÃ¡tica - DiseÃ±o de un editor de diagramas de clases UML para la implementaciÃ³n de modelos multi-agentes - Como parte del desarrollo de su plataforma de modelizaciÃ³n y simulaciÃ³n multi-agente, Cormas (http://cormas.cirad.fr) la Unidad de InvestigaciÃ³n Green del CIRAD (http://ur-green.cirad.fr) ofrece una prÃ¡ctica remunerada por 6 meses por un estudiante de informÃ¡tica para desarrollar un mÃ³dulo de Cormas. Este desarrollo consiste en crear un editor grÃ¡fico para deseÃ±ar un diagrama de clases UML y generar cÃ³digo SmallTalk (en VisualWorks Cincom y/o en Pharo, de cÃ³digo abierto) de la estructura del modelo refiriÃ©ndose al estÃ¡ndar "ejecutable UML" (xUML) propuesto por Mellor y Balcer (2002) y adoptado por el OMG (2008). Para este trabajo, no buscamos un editor global que integre todos los elementos descritos por UML2. Sin embargo, este editor deberÃ¡ estar simples y integrar los elementos del meta-modelo limitados a: clases, atributos y mÃ©todos, especializaciÃ³n de clases y asociaciones. Las asociaciones son simples (solo binaria) y se definen por su nombre y sus extremos que tienen cada uno un nombre de rol, un valor de multiplicidad y navegabilidad. AsÃ que Cormas es un framework, el modelo creado por un usuario deben heredar de las clases predefinidas en Cormas. Al final del diseÃ±o de su modelo, el usuario se le pedirÃ¡ para vincular las clases que creÃ³ con las clases predefinidas. En este caso, las caracterÃsticas (mÃ©todos, asociaciones, atributos, ...) deben ser especificados en el diagrama conceptual del usuario que se puede mostrar de forma independiente de la estructura heredada. AdemÃ¡s de la creaciÃ³n dinÃ¡mica del esqueleto de las clases, el estudiante debe prestar especial atenciÃ³n a las asociaciones entre clases uni o bi-direccional para traducirse en atributos nombrados en el rol al final de la asociaciÃ³n (a veces llamada asociaciÃ³n degenerada para el que se traduce el rol del extremo opuesto en el atributo). No se tendrÃ¡n en cuenta las clases-asociaciones o las asociaciones n-arias o asociaciones calificadas. Este editor tambiÃ©n podrÃa re-mostrar un modelo ya salvado, sino proponer de generar un nuevo diagrama de un modelo ya implantado (ingenierÃa inversa). AdemÃ¡s, un editor de diagrama de actividad xUML ya estÃ¡ disponible en Cormas. Mediante la selecciÃ³n de un mÃ©todo de su diagrama de clases, el usuario puede desiÃ±ar el comportamiento de este mÃ©todo mediante la descripciÃ³n de la secuencia de actividades y condiciones booleanas. Aunque la distribuciÃ³n de VisualWorks se acompaÃ±a de algunas herramientas de ida y vuelta entre el cÃ³digo y diagramas UML Smalltalk (ADvance, Gipa, BOOST, MetaEdit+, DoME, UMLForSmalltalk ou Umbrello,..), el desarrollo del editor UML estarÃ¡ construido a partir de Roassal. De hecho, con el reciente lanzamiento de Roassal2, un poderoso motor de visualizaciÃ³n (http://objectprofile.com/Roassal.html) disponible tanto para VisualWorks y Pharo, el enfoque de este mÃ³dulo UML permitirÃ¡ de acelerar la migraciÃ³n de Cormas en Pharo. Opcionalmente, serÃ¡ interesante de generar cÃ³digo XML (XMI) de un modelo que serÃ¡ legible con otros editores. DuraciÃ³n: 6 meses (o menos si es necesario) GratificaciÃ³n: â¬ 485,10 por mes. LocalizaciÃ³n: no hay recepciÃ³n prevista en el CIRAD. El estudiante trabajarÃ¡ en su laboratorio, pero contactos regulares serÃ¡n necesarios. Contactos: Pierre Bommel (bommel(a)cirad.fr) y Gregoire Leclerc (Leclerc(a)cirad.fr) Perfil del candidato: Estudiante en Ciencias de la ComputaciÃ³n, licencia o maestra, con un gusto para la modelizaciÃ³n y simulaciÃ³n. El estudiante debe tener un buen conocimiento de los conceptos de modelizaciÃ³n objetos y UML. Conocimientos de programaciÃ³n Smalltalk deben adquirirse. Bommel, P., Dieguez, F., Bartaburu, D., Duarte, E., Montes, E., Pereira, M., Corral, J., Lucena, C. de and Morales Grosskopf, H. (2014). A Further Step Towards Participatory Modelling. Fostering Stakeholder Involvement in Designing Models by Using Executable UML. Journal of Artificial Societies and Social Simulation 17 (1) 6 <http://jasss.soc.surrey.ac.uk/17/1/6.html>. Mellor, S. J., & Balcer, M. J. (2002). Executable UML : a foundation for model-driven architecture. Boston; San Francisco; New York: Addison-Wesley. OMG. (2008). Model Driven Architecture, MDA Guide Version 1.0.1 -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

3 4

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