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

[pharo-project/pharo-core] e19fa7: 50070
by GitHub May 28, 2015

May 28, 2015

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: e19fa76f110ca08beb2a22cd7e6454caf35839bf https://github.com/pharo-project/pharo-core/commit/e19fa76f110ca08beb2a22cd… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-05-28 (Thu, 28 May 2015) Changed paths: A AST-Core.package/RBVariableNode.class/instance/testing/hasIncompleteIdentifier.st A Refactoring-Core.package/RBRemoveClassRefactoring.class/class/error messages/cannotRemoveTopLevelClassErrorMesssage.st A Refactoring-Core.package/RBRemoveClassRefactoring.class/instance/preconditions/environmentWithReferencesTo_.st A Refactoring-Core.package/RBRemoveClassRefactoring.class/instance/preconditions/environmentWithUsersOf_.st A Refactoring-Core.package/RBRemoveClassRefactoring.class/instance/preconditions/preconditionHasNoReferences_.st A Refactoring-Core.package/RBRemoveClassRefactoring.class/instance/preconditions/preconditionHasNoSubclasses_.st A Refactoring-Core.package/RBRemoveClassRefactoring.class/instance/preconditions/preconditionHasNoUsers_.st A Refactoring-Core.package/RBRemoveClassRefactoring.class/instance/preconditions/preconditionIsNotMetaclass_.st M Refactoring-Core.package/RBRemoveClassRefactoring.class/instance/preconditions/preconditions.st R Refactoring-Tests-Core.package/RBRemoveClassTest.class/instance/failure tests/testBadName.st A Refactoring-Tests-Core.package/RBRemoveClassTest.class/instance/failure tests/testRemoveClassWithBadNameRaisesRBRefactoringError.st A Refactoring-Tests-Core.package/RBRemoveClassTest.class/instance/failure tests/testRemoveClassWithReferencesRaisesRBRefactoringError.st R Refactoring-Tests-Core.package/RBRemoveClassTest.class/instance/failure tests/testRemoveReferenced.st A Refactoring-Tests-Core.package/RBRemoveClassTest.class/instance/private/resumeOnCannotRemoveTopLevelClassError_.st A Refactoring-Tests-Core.package/RBRemoveClassTest.class/instance/tests/testRaisesRBRefactoringErrorWhenRemovingClassWithSubclasses.st M Refactoring-Tests-Core.package/RBRemoveClassTest.class/instance/tests/testRemoveClass.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50069.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50070.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50069.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50070.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Shout.package/SHRBTextStyler.class/instance/private/resolveStyleFor_.st R Shout.package/SHRBTextStyler.class/instance/visiting rb nodes/visitClassReferenceNode_.st M Shout.package/SHRBTextStyler.class/instance/visiting rb nodes/visitVariableNode_.st M System-Caching.package/TTLCache.class/instance/removing/removeStaleValues.st Log Message: ----------- 50070 15575 AST syntax highlight: clean up variable resolving a bit https://pharo.fogbugz.com/f/cases/15575 15614 TTLCache>>#removeStaleValues should use the proper #isStale: test https://pharo.fogbugz.com/f/cases/15614 15076 RBRemoveClassRefactoring slightly broken https://pharo.fogbugz.com/f/cases/15076 http://files.pharo.org/image/50/50070.zip

1 0

Inconsistent number comparison?
by Sean P. DeNigris May 28, 2015

May 28, 2015

Why does "1 = 1.0" but "273.15 ~= (5463/20)"? You must send #asFloat to the fraction to answer true... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Inconsistent-number-comparison-tp4828795.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

4 8

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

translateBy: vs translatedBy:
by Serge Stinckwich May 27, 2015

May 27, 2015

In Pharo 4.0, there is a Rectangle>>translateBy: aFactor method. The same method in VW is called translatedBy: In Pharo, there is also a translatedToBeWithin: and translatedAndSquishedToBeWithin: and scaledBy: Just to be consistent, this is maybe better to use translatedBy: instead of translateBy: ? -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

5 7

[Request]: Review Issue 15399: SmalltalkImage: Thin Proliferation of File Access Messages
by Sean P. DeNigris May 27, 2015

May 27, 2015

https://pharo.fogbugz.com/default.asp?15399 Fix in inbox: SLICE-Issue-15399-SmalltalkImage-Thin-Proliferation-of-File-Access-Messages-SeanDeNigris.2 ### Motivation There was a proliferation of methods in SmalltalkImage for accessing files like sources, changes, and image. The problems were twofold: 1. The interface was complicated with the only benefit being saving a few characters of typing - not worth it! In particular, #vmDirectory instead of "vm directory" seems particularly not-worth-it. 2. It was encouraging strange code, like in ScriptLoader, where the name was taken, and because we were dealing with strings instead of real file objects, #basenameWithoutIndicator was reimplemented `Smalltalk shortImageName copyUpToLast: $.`. And then CodeHolder `sourcesName := Smalltalk sourcesName asFileReference basename.` was using it to reconstruct a real file object which could easily have been gotten via #imageFile. ### Changes #### This version - Deprecate #changesName, #shortImageName, #sourcesName, #vmBinary, and #vmDirectory. Saving a few characters of typing is not worth the complication of interface. - Move all deprecated methods into Deprecated50 package - Update all users - clean up inconsistently named protocols - [OT]: Enhance #basenameWithoutExtension comment #### v. 1 - deprecated SmalltalkImage>>imageName - removed duplicated primitive - changed wrong comment ----- Cheers, Sean -- View this message in context: http://forum.world.st/Request-Review-Issue-15399-SmalltalkImage-Thin-Prolif… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

1 0

Parser missing something
by Stephan Eggermont May 27, 2015

May 27, 2015

50069 When the cursor is between the parenthesis, I get a MNU RBParseErrorNode>>addParenthesis: when typing anything drawOn: aCanvas |lines| super drawOn: aCanvas. lines := segments size - 1. 1 to: lines do: [:index | |x| x :=self extent x + ( ) aCanvas line: self extent x+ (index* to: color: self defaultBorderColor

2 1

Incorrect Class Variable Highlighting?
by Sean P. DeNigris May 27, 2015

May 27, 2015

Looks like a bug... Shall I open an issue? <http://forum.world.st/file/n4828900/Screenshot_2015-05-27_09.png> ----- Cheers, Sean -- View this message in context: http://forum.world.st/Incorrect-Class-Variable-Highlighting-tp4828900.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

2 1

OSWindow VM event creation
by stepharo May 27, 2015

May 27, 2015

Hi guys with alain we are looking for the place where events are created in OSWindow. We are looking for the the event created by the visitor on top of SDL2 event but for the compatible version ie the event created by the default vm. We are looking for the place where the event created by the vm are passed to OSWindow. We saw that there is OSVMDriver and friends but we could not see how the OSVM is fed with the default inputSensor or inputFetcherEvent of Pharo. Stef

1 1

strange code in RBRefactoringTest
by Christophe Demarey May 27, 2015

May 27, 2015

hi, Does anyone knows if there is a particular reason to write this kind of code (snippet from RBRefactoringTest>>setUp assoc := RBRefactoringManager classPool associationAt: #Instance ifAbsent: [RBRefactoringManager classPool associationAt: 'Instance']. manager := assoc value. Thanks, Christophe

4 3

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/

2 2