- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] strange code in RBRefactoringTest

by Christophe Demarey

Le 27 mai 2015 Ã 09:55, Marcus Denker a Ã©crit : > >> On 27 May 2015, at 09:46, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: >> >> 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. >> > > I guess someone wanted to reset the class var without adding a #reset method. > > There is #nuke, though: > > nuke > Instance notNil ifTrue: [ Instance release ]. > Instance := nil > > maybe the test does not want to call #release? > > The reflective API was improved in the meantime, you can just do > > RBRefactoringManagerclassVarNamed: âInstance' put: nil. > > > Marcus ok, thanks

May 27, 2015

Re: [Pharo-dev] Fwd: [cormas] [Cormas] Proposition de stage en informatique

by Serge Stinckwich

Yes, this will be an option to investigate I guess. 2015-05-27 10:25 GMT+02:00 Torsten Bergmann <astares(a)gmx.de>: > Is this related to Dynacase? > http://astares.blogspot.de/2015/03/dynacase-modelling-for-pharo.html > > >> Gesendet: Mittwoch, 27. Mai 2015 um 08:46 Uhr >> Von: "Serge Stinckwich" <serge.stinckwich(a)gmail.com> >> An: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org>, "Moose-related development" <moose-dev(a)iam.unibe.ch>, "smalltalk-fr(a)googlegroups.com" <smalltalk-fr(a)googlegroups.com>, smalltalk-gsoc-students(a)googlegroups.com, "Discusses Development of Pharo" <pharo-dev(a)lists.pharo.org>, smalltalk-research(a)googlegroups.com >> Betreff: [Pharo-dev] Fwd: [cormas] [Cormas] Proposition de stage en informatique >> >> 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/ >> >> > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

May 27, 2015

Re: [Pharo-dev] Fwd: [cormas] [Cormas] Proposition de stage en informatique

by Torsten Bergmann

Is this related to Dynacase? http://astares.blogspot.de/2015/03/dynacase-modelling-for-pharo.html > Gesendet: Mittwoch, 27. Mai 2015 um 08:46 Uhr > Von: "Serge Stinckwich" <serge.stinckwich(a)gmail.com> > An: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org>, "Moose-related development" <moose-dev(a)iam.unibe.ch>, "smalltalk-fr(a)googlegroups.com" <smalltalk-fr(a)googlegroups.com>, smalltalk-gsoc-students(a)googlegroups.com, "Discusses Development of Pharo" <pharo-dev(a)lists.pharo.org>, smalltalk-research(a)googlegroups.com > Betreff: [Pharo-dev] Fwd: [cormas] [Cormas] Proposition de stage en informatique > > 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/ > >

May 27, 2015

Re: [Pharo-dev] Cross platform key modifiers

by Nicolai Hess

2015-05-27 9:29 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com>: > Camillo introduced a while ago the meta modifier: > > $a meta > > $z meta shift > > meta is sensitive to the current environment and is equivalent to what you > where describing above: > - command in mac > - control in windows/unix > > What should be done is to use it in the system :). > Then there is something I don't understand or I don't do it right :) a shortcut defined like: $b meta shift never matches for me (on windows). But $b ctrl shift $b command shift works. (the last on matches on alt+shift+b, but defining a keyshortcut as $b alt shift again does not work). > > Guille > > El lun., 25 de may. de 2015 a la(s) 2:16 p. m., Sean P. DeNigris < > sean(a)clipperadams.com> escribiÃ³: > >> Great OP! We should get this straight for sure... >> >> >> Nicolai Hess wrote >> > Yes, this is what I expected too. >> > ... >> > With that, I would expect "Character arrowLeft command" maps to >> > Ctrl+Left for windows/linux >> > Meta+Left for Mac (If Meta is the Command-Key on a Mac keyboard). >> >> That makes sense to me. "command" seems like it may be the best abstract >> term. Hotkey already has a meaning >> (http://en.wikipedia.org/wiki/Keyboard_shortcut) and it seems meta is >> used >> inconsistently by the platforms - i.e. Mac uses it for commands, but >> Windows >> uses ctrl instead. IIRC we already treat #option and #alt as synonyms... >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: >> http://forum.world.st/Cross-platform-key-modifiers-tp4828113p4828461.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >>

May 27, 2015

Re: [Pharo-dev] Cross platform key modifiers

by Serge Stinckwich

Yes meta key come from Lisp Machine: http://en.wikipedia.org/wiki/Meta_key I guess we should have a look how Emacs solve this keybinding issue regarding multiple platforms. On Wed, May 27, 2015 at 9:29 AM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Camillo introduced a while ago the meta modifier: > > $a meta > > $z meta shift > > meta is sensitive to the current environment and is equivalent to what you > where describing above: > - command in mac > - control in windows/unix > > What should be done is to use it in the system :). > > Guille > > El lun., 25 de may. de 2015 a la(s) 2:16 p. m., Sean P. DeNigris > <sean(a)clipperadams.com> escribiÃ³: >> >> Great OP! We should get this straight for sure... >> >> >> Nicolai Hess wrote >> > Yes, this is what I expected too. >> > ... >> > With that, I would expect "Character arrowLeft command" maps to >> > Ctrl+Left for windows/linux >> > Meta+Left for Mac (If Meta is the Command-Key on a Mac keyboard). >> >> That makes sense to me. "command" seems like it may be the best abstract >> term. Hotkey already has a meaning >> (http://en.wikipedia.org/wiki/Keyboard_shortcut) and it seems meta is >> used >> inconsistently by the platforms - i.e. Mac uses it for commands, but >> Windows >> uses ctrl instead. IIRC we already treat #option and #alt as synonyms... >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: >> http://forum.world.st/Cross-platform-key-modifiers-tp4828113p4828461.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

May 27, 2015

Re: [Pharo-dev] strange code in RBRefactoringTest

by Marcus Denker

> On 27 May 2015, at 09:46, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > > 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. > I guess someone wanted to reset the class var without adding a #reset method. There is #nuke, though: nuke Instance notNil ifTrue: [ Instance release ]. Instance := nil maybe the test does not want to call #release? The reflective API was improved in the meantime, you can just do RBRefactoringManagerclassVarNamed: âInstance' put: nil. Marcus

May 27, 2015

Re: [Pharo-dev] strange code in RBRefactoringTest

by Guillermo Polito

I'd say that it looks like a "bug ward". But I think the system should not contain right now classpools with string keys. They should all be symbols. (Smalltalk allClasses gather: [ :class | class classPool keys ]) select: [ :k | k isSymbol not ] should be an empty collection. So you probably can replace those three lines by: manager := Instance. ? Guille El miÃ©., 27 de may. de 2015 a la(s) 9:46 a. m., Christophe Demarey < christophe.demarey(a)inria.fr> escribiÃ³: > 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 >

May 27, 2015

strange code in RBRefactoringTest

by Christophe Demarey

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

May 27, 2015

Re: [Pharo-dev] Cross platform key modifiers

by Guillermo Polito

Camillo introduced a while ago the meta modifier: $a meta $z meta shift meta is sensitive to the current environment and is equivalent to what you where describing above: - command in mac - control in windows/unix What should be done is to use it in the system :). Guille El lun., 25 de may. de 2015 a la(s) 2:16 p. m., Sean P. DeNigris < sean(a)clipperadams.com> escribiÃ³: > Great OP! We should get this straight for sure... > > > Nicolai Hess wrote > > Yes, this is what I expected too. > > ... > > With that, I would expect "Character arrowLeft command" maps to > > Ctrl+Left for windows/linux > > Meta+Left for Mac (If Meta is the Command-Key on a Mac keyboard). > > That makes sense to me. "command" seems like it may be the best abstract > term. Hotkey already has a meaning > (http://en.wikipedia.org/wiki/Keyboard_shortcut) and it seems meta is > used > inconsistently by the platforms - i.e. Mac uses it for commands, but > Windows > uses ctrl instead. IIRC we already treat #option and #alt as synonyms... > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Cross-platform-key-modifiers-tp4828113p4828461.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

May 27, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] c9dbbd: 50068

by Sven Van Caekenberghe

> On 27 May 2015, at 08:06, GitHub <noreply(a)github.com> wrote: > > Branch: refs/heads/5.0 > Home: https://github.com/pharo-project/pharo-core > Commit: c9dbbdb8f54d76633304cbe15a0b0b5864a9c05f > https://github.com/pharo-project/pharo-core/commit/c9dbbdb8f54d76633304cbe1… > Author: Jenkins Build Server <board(a)pharo-project.org> > Date: 2015-05-27 (Wed, 27 May 2015) > > Changed paths: > A Balloon.package/extension/InfiniteForm/instance/fillRectangle_on_.st > R Collections-Abstract.package/Collection.class/instance/adapting/adaptToString_andSend_.st > R Collections-Arithmetic.package/extension/String/instance/%2A.st > R Collections-Arithmetic.package/extension/String/instance/%2F%2F.st > R Collections-Arithmetic.package/extension/String/instance/%2F.st > R Collections-Arithmetic.package/extension/String/instance/%5C%5C.st > R Collections-Arithmetic.package/extension/String/instance/+.st > R Collections-Arithmetic.package/extension/String/instance/-.st > R Collections-Strings.package/String.class/instance/converting/adaptToCollection_andSend_.st > R Collections-Strings.package/String.class/instance/converting/adaptToNumber_andSend_.st > R Collections-Strings.package/String.class/instance/converting/adaptToPoint_andSend_.st > R Collections-Strings.package/String.class/instance/converting/adaptToString_andSend_.st > R Kernel.package/Number.class/instance/converting/adaptToString_andSend_.st > R Kernel.package/Point.class/instance/converting/adaptToString_andSend_.st > M Morphic-Core.package/WorldState.class/class/world menu items/mostUsedToolsOn_.st > M Morphic-Core.package/WorldState.class/class/world menu items/quitItemsOn_.st > A Morphic-Widgets-Pluggable.package/TextMorphForFieldView.class/README.md > A Morphic-Widgets-Pluggable.package/TextMorphForFieldView.class/definition.st > A Morphic-Widgets-Pluggable.package/TextMorphForFieldView.class/instance/accessing/maxLength.st > A Morphic-Widgets-Pluggable.package/TextMorphForFieldView.class/instance/accessing/maxLength_.st > A Morphic-Widgets-Pluggable.package/TextMorphForFieldView.class/instance/accessing/minExtent.st > A Morphic-Widgets-Pluggable.package/TextMorphForFieldView.class/instance/changed/keyboardFocusChange_.st > A Morphic-Widgets-Pluggable.package/TextMorphForFieldView.class/instance/event handling/keyStroke_.st > A Morphic-Widgets-Pluggable.package/TextMorphForFieldView.class/instance/event handling/mouseMove_.st > A Morphic-Widgets-Pluggable.package/TextMorphForFieldView.class/instance/events/localHandleKeystroke_.st > A Morphic-Widgets-Pluggable.package/TextMorphForFieldView.class/instance/find-replace/sharesFindReplace.st > A Morphic-Widgets-Pluggable.package/TextMorphForFieldView.class/instance/geometry/minimumExtent.st > A Morphic-Widgets-Pluggable.package/TextMorphForFieldView.class/instance/layout/minHeight.st > A Morphic-Widgets-Pluggable.package/TextMorphForFieldView.class/instance/layout/minWidth.st > A Morphic-Widgets-Pluggable.package/TextMorphForFieldView.class/instance/private/editorClass.st > A Morphic-Widgets-Pluggable.package/TextMorphForFieldView.class/instance/private/paragraph.st > A Morphic-Widgets-Pluggable.package/TextMorphForFieldView.class/instance/private/useFindReplaceSelection.st > A Morphic-Widgets-Pluggable.package/TextMorphForFieldView.class/instance/private/useSecondarySelection.st > A Morphic-Widgets-Pluggable.package/TextMorphForFieldView.class/instance/private/useSelectionBar.st > A Morphic-Widgets-Pluggable.package/TextMorphForFieldView.class/instance/testing/isEditEvent_.st > R Polymorph-Widgets.package/TextMorphForFieldView.class/README.md > R Polymorph-Widgets.package/TextMorphForFieldView.class/definition.st > R Polymorph-Widgets.package/TextMorphForFieldView.class/instance/accessing/maxLength.st > R Polymorph-Widgets.package/TextMorphForFieldView.class/instance/accessing/maxLength_.st > R Polymorph-Widgets.package/TextMorphForFieldView.class/instance/accessing/minExtent.st > R Polymorph-Widgets.package/TextMorphForFieldView.class/instance/changed/keyboardFocusChange_.st > R Polymorph-Widgets.package/TextMorphForFieldView.class/instance/event handling/keyStroke_.st > R Polymorph-Widgets.package/TextMorphForFieldView.class/instance/event handling/mouseMove_.st > R Polymorph-Widgets.package/TextMorphForFieldView.class/instance/events/localHandleKeystroke_.st > R Polymorph-Widgets.package/TextMorphForFieldView.class/instance/find-replace/sharesFindReplace.st > R Polymorph-Widgets.package/TextMorphForFieldView.class/instance/geometry/minimumExtent.st > R Polymorph-Widgets.package/TextMorphForFieldView.class/instance/layout/minHeight.st > R Polymorph-Widgets.package/TextMorphForFieldView.class/instance/layout/minWidth.st > R Polymorph-Widgets.package/TextMorphForFieldView.class/instance/private/editorClass.st > R Polymorph-Widgets.package/TextMorphForFieldView.class/instance/private/paragraph.st > R Polymorph-Widgets.package/TextMorphForFieldView.class/instance/private/useFindReplaceSelection.st > R Polymorph-Widgets.package/TextMorphForFieldView.class/instance/private/useSecondarySelection.st > R Polymorph-Widgets.package/TextMorphForFieldView.class/instance/private/useSelectionBar.st > R Polymorph-Widgets.package/TextMorphForFieldView.class/instance/testing/isEditEvent_.st > R Polymorph-Widgets.package/extension/FillStyle/instance/fillRectangle_on_.st > R Polymorph-Widgets.package/extension/InfiniteForm/instance/fillRectangle_on_.st > R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50067.st > A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50068.st > R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50067.st > A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50068.st > M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st > R Spec-Inspector.package/extension/Object/instance/basicInspect.st > R Spec-Inspector.package/extension/Object/instance/explore.st > R Spec-Inspector.package/extension/Object/instance/inspect.st > R Spec-Inspector.package/extension/Object/instance/inspectOnce.st > R Spec-Inspector.package/extension/Object/instance/inspectWithLabel_.st > R Spec-Inspector.package/extension/Object/instance/inspector.st > R Spec-Inspector.package/extension/Object/instance/inspectorClass.st > R Spec-Tools.package/extension/Object/instance/displaySubObjectAt_.st > R Spec-Tools.package/extension/Object/instance/subObjectsToInspect.st > R Spec-Tools.package/extension/SequenceableCollection/instance/displaySubObjectAt_.st > R Spec-Tools.package/extension/SequenceableCollection/instance/subObjectsToInspect.st > M System-Settings.package/SettingBrowser.class/class/world menu/menuCommandOn_.st > A Tool-Base.package/extension/Object/instance/basicInspect.st > A Tool-Base.package/extension/Object/instance/explore.st > A Tool-Base.package/extension/Object/instance/inspect.st > A Tool-Base.package/extension/Object/instance/inspectOnce.st > A Tool-Base.package/extension/Object/instance/inspectWithLabel_.st > A Tool-Base.package/extension/Object/instance/inspector.st > A Tool-Base.package/extension/Object/instance/inspectorClass.st > M Tool-Transcript.package/extension/ThreadSafeTranscript/class/menuCommandOn_.st > > Log Message: > ----------- > 50068 > 13829 TextMorphForEditorView should be packaged in Moprhic-Widgets-Pluggable > https://pharo.fogbugz.com/f/cases/13829 > > 2906 Analyze #adaptToNumber:andSend: > https://pharo.fogbugz.com/f/cases/2906 My faith in Pharo is restored ;-) > 14040 FillStyle>>fillRectangle: aRectangle on: aCanvas should be packaged in Balloon > https://pharo.fogbugz.com/f/cases/14040 > > 15613 Display most use tools shortcuts on World menu. > https://pharo.fogbugz.com/f/cases/15613 > > 15135 Object extensions related to explore/inspect should be repackaged into their own independent package > https://pharo.fogbugz.com/f/cases/15135 > > http://files.pharo.org/image/50/50068.zip > >

May 27, 2015