- Pharo-dev - lists.pharo.org

Fwd: [cormas] [Cormas] Proposition de stage en informatique

by Serge Stinckwich

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

[pharo-project/pharo-core]

by GitHub

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

May 27, 2015

[pharo-project/pharo-core] edf113: 50069

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: edf11372826bd59dde682e7e6f05ca21ebb1f8a9 https://github.com/pharo-project/pharo-core/commit/edf11372826bd59dde682e7e… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-05-27 (Wed, 27 May 2015) Changed paths: R Komitter.package/Komitter.class/class/world menu/initialize.st M Komitter.package/Komitter.class/class/world menu/komitterMenuOn_.st M Reflectivity-Tests.package/HookGeneratorTest.class/instance/tests - hooks/testConditionWithArguments.st M Reflectivity-Tests.package/HookGeneratorTest.class/instance/tests - hooks/testHookWithArguments.st M Reflectivity-Tests.package/HookGeneratorTest.class/instance/tests - hooks/testHookWithVirtualMeta.st R Reflectivity.package/Breakpoint.class/instance/as yet unclassified/initialize.st A Reflectivity.package/Breakpoint.class/instance/initialization/initialize.st A Reflectivity.package/HookGenerator.class/class/instance creation/node_link_.st R Reflectivity.package/HookGenerator.class/instance/initialize/initForNode_.st A Reflectivity.package/HookGenerator.class/instance/initialize/node_link_.st R Reflectivity.package/ManifestReflectivity.class/instance/code-critics/ruleRBBadMessageRuleV1FalsePositive.st R Reflectivity.package/MetaLink.class/class/as yet unclassified/uninstallAll.st A Reflectivity.package/MetaLink.class/class/cleanup/uninstallAll.st M Reflectivity.package/MetaLink.class/instance/ast/hookOn_.st A Reflectivity.package/RFArgumentsReification.class/README.md A Reflectivity.package/RFArgumentsReification.class/class/plugin interface/key.st A Reflectivity.package/RFArgumentsReification.class/class/plugin interface/nodes.st A Reflectivity.package/RFArgumentsReification.class/definition.st A Reflectivity.package/RFArgumentsReification.class/instance/generate/genForRBProgramNode.st R Reflectivity.package/RFLinkReification.class/instance/as yet unclassified/genForRBProgramNode.st A Reflectivity.package/RFLinkReification.class/instance/generate/genForRBProgramNode.st M Reflectivity.package/RFNewValueReification.class/instance/generate/genForRBAssignmentNode.st R Reflectivity.package/RFNodeReification.class/instance/as yet unclassified/genForRBProgramNode.st A Reflectivity.package/RFNodeReification.class/instance/generate/genForRBProgramNode.st R Reflectivity.package/RFObjectReification.class/instance/code generation/genForRBProgramNode.st A Reflectivity.package/RFObjectReification.class/instance/generate/genForRBProgramNode.st R Reflectivity.package/RFReification.class/class/accessing/allKeys.st R Reflectivity.package/RFReification.class/class/accessing/for_.st R Reflectivity.package/RFReification.class/class/as yet unclassified/node_link_.st A Reflectivity.package/RFReification.class/class/instance creation/node_link_.st A Reflectivity.package/RFReification.class/class/plugin interface/allKeys.st A Reflectivity.package/RFReification.class/class/plugin interface/for_.st M Reflectivity.package/RFSemanticAnalyzer.class/instance/visiting/visitNode_.st A Reflectivity.package/RFSenderReification.class/README.md A Reflectivity.package/RFSenderReification.class/class/plugin interface/key.st A Reflectivity.package/RFSenderReification.class/class/plugin interface/nodes.st A Reflectivity.package/RFSenderReification.class/definition.st A Reflectivity.package/RFSenderReification.class/instance/generate/genForRBMessageNode.st A Reflectivity.package/RFSenderReification.class/instance/generate/genForRBMethodNode.st R Reflectivity.package/RFTArgumentsReification.class/README.md R Reflectivity.package/RFTArgumentsReification.class/class/plugin interface/key.st R Reflectivity.package/RFTArgumentsReification.class/class/plugin interface/nodes.st R Reflectivity.package/RFTArgumentsReification.class/definition.st R Reflectivity.package/RFTArgumentsReification.class/instance/generate/genForRBProgramNode.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50068.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50069.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50068.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50069.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Caching.package/DoubleLinkedList.class/README.md M System-Caching.package/DoubleLinkedList.class/instance/accessing/first.st A System-Caching.package/DoubleLinkedList.class/instance/accessing/firstLink.st M System-Caching.package/DoubleLinkedList.class/instance/accessing/last.st A System-Caching.package/DoubleLinkedList.class/instance/accessing/lastLink.st M System-Caching.package/DoubleLinkedList.class/instance/adding/addAll_.st M System-Caching.package/DoubleLinkedList.class/instance/adding/addFirst_.st M System-Caching.package/DoubleLinkedList.class/instance/adding/addLast_.st M System-Caching.package/DoubleLinkedList.class/instance/adding/add_.st M System-Caching.package/DoubleLinkedList.class/instance/adding/add_afterLink_.st M System-Caching.package/DoubleLinkedList.class/instance/adding/add_beforeLink_.st M System-Caching.package/DoubleLinkedList.class/instance/converting/asArray.st M System-Caching.package/DoubleLinkedList.class/instance/enumerating/collect_.st M System-Caching.package/DoubleLinkedList.class/instance/enumerating/do_.st A System-Caching.package/DoubleLinkedList.class/instance/enumerating/linksDo_.st M System-Caching.package/DoubleLinkedList.class/instance/enumerating/reject_.st M System-Caching.package/DoubleLinkedList.class/instance/enumerating/reverseDo_.st A System-Caching.package/DoubleLinkedList.class/instance/enumerating/reverseLinksDo_.st M System-Caching.package/DoubleLinkedList.class/instance/enumerating/select_.st A System-Caching.package/DoubleLinkedList.class/instance/private/emptyCheck.st M System-Caching.package/DoubleLinkedList.class/instance/removing/removeAll.st M System-Caching.package/DoubleLinkedList.class/instance/removing/removeFirst.st M System-Caching.package/DoubleLinkedList.class/instance/removing/removeLast.st M System-Caching.package/DoubleLinkedList.class/instance/removing/removeLink_.st M System-Caching.package/DoubleLinkedList.class/instance/testing/includes_.st M System-Caching.package/DoubleLinkedList.class/instance/testing/isEmpty.st A System-CachingTests.package/DoubleLinkedListTests.class/instance/testing/testFirstAndLastLink.st A System-CachingTests.package/DoubleLinkedListTests.class/instance/testing/testLinksDo.st A System-CachingTests.package/DoubleLinkedListTests.class/instance/testing/testReverseLinksDo.st A Tool-Base.package/PharoShortcuts.class/instance/kaymaps - Tools/openKomitterShortcut.st A Tool-Base.package/ToolShortcutsCategory.class/instance/keymaps/openKomitter.st Log Message: ----------- 50069 15340 Extending DoubleLinkedList API https://pharo.fogbugz.com/f/cases/15340 15617 Shortcut($k command) doesnt open the Komitter https://pharo.fogbugz.com/f/cases/15617 15616 Improve Reifications https://pharo.fogbugz.com/f/cases/15616 http://files.pharo.org/image/50/50069.zip

May 27, 2015

[pharo-project/pharo-core]

by GitHub

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

May 27, 2015

[pharo-project/pharo-core] c9dbbd: 50068

by GitHub

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 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

Re: [Pharo-dev] Gofer upgrade error

by Marcus Denker

> On 26 May 2015, at 17:30, Ben Coman <btc(a)openInWorld.com> wrote: > > Thanks Leo. Indeed I see the commands you tried are suggested in those > references. > > On Tue, May 26, 2015 at 3:26 AM, Leo <lpaniceres(a)gmail.com> wrote: >> Ben, >> the documentation for "Gofer upgrade" is >> http://file-pharo.inria.fr/doc/4.0/class/Gofer.html > > Doing this is 50064 I gives... 'MNU receiver of "default" is nil' in... > GoferUnload>>unregisterPackageInfo: aWorkingCopy > PackageOrganizer default > unregisterPackage: aWorkingCopy packageInfo The problem is that it loads a very old version of Goferâ¦ one that e.g. uses the old filesystem, Packageinfo instead of RPackage and things like that. We should just remove the update method and solve update systemwide better. Marcus

May 27, 2015

Re: [Pharo-dev] Is there an official JSON parser/writer?

by Levente Uzonyi

On Tue, 26 May 2015, Esteban A. Maringolo wrote: > 2015-05-26 16:15 GMT-03:00 Stephan Eggermont <stephan(a)stack.nl>: >> On 26/05/15 18:40, Esteban A. Maringolo wrote: >>> >>> I'm modifying the PostgresV2 package to support JSON datatype but >>> instead of using the JSON package from PharoExtras I'm trying to use >>> NeoJSON. > >> Is there a specific reason not to move to PostgresV3? > > I'd love to do so. But where is it? It is not in SmalltalkHub certainly. Google is your friend in this case. It's on squeaksource.com, but I also saw a Pharo port on Github. > It would also require to adapt/implement GLORP's adaptor for PostgresV3. > Or is it a plug-in replacement? It has slightly different API than the V2 version. I've never used Glorp, so I can't tell if it works or not, but I assume that it does not. Levente > > Please provide me with pointers, now is when :) > > > Esteban A. Maringolo > >

May 27, 2015

Inconsistent number comparison?

by Sean P. DeNigris

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.

May 27, 2015

Re: [Pharo-dev] translateBy: vs translatedBy:

by Ben Coman

> > On Tue, May 26, 2015 at 6:14 PM, Ben Coman <btc(a)openinworld.com> wrote: >> >> On Tue, May 26, 2015 at 9:38 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> >> I vote for renaming to Rectangle>>translatedBy:, because it returns a >> >> new >> >> translated rectangle instance. >> > >> > >> > -1 >> > There is no benefit in renaming a single method, apart from creating >> > more >> > confusion. >> >> I wouldn't say "no benefit". Consistent conventions are beneficial. >> It could be useful to bring these into line with the general "-ed" >> convention of returning a new object. I don't see how this would >> create confusion, though it might create work. Whether its worth the >> work is a slightly different question. >> >> > If anything, the whole Rectangle API would have to be changed, as there >> > is >> > plethora of similar methods (expandBy:, extendBy:, merge:, etc.) >> >> For a better feel of the work involved... >> >> Rectangle methods select: [ :m | m sourceCode includesSubstring: '^ >> Rectangle ' ]. >> Rectangle>>#intersect: >> Rectangle>>#quickMerge: >> Rectangle>>#encompass: >> Rectangle>>#intersect:ifNone: >> >> Rectangle methods select: [ :m | m sourceCode includesSubstring: >> '^Rectangle ' ]. >> Rectangle>>#intersect: >> Rectangle>>#translateBy: >> Rectangle>>#scaleBy: >> Rectangle>>#merge: >> Rectangle>>#compressTo: >> Rectangle>>#expandTo: >> Rectangle>>#roundTo: >> Rectangle>>#truncateTo: >> >> The following already follow the convention... >> Rectangle>>#compressed >> Rectangle>>#expanded >> Rectangle>>#rounded >> Rectangle>>#truncated >> >> > Pretty much all Rectangle messages are immutable and create new >> > Rectangle, >> > thus I feel it is unnecessary to state it explicitly. >> > >> > In VW there is plenty of methods (e.g. left:) that mutates it, thus >> > unlike >> > Pharo a clear distinction is required. >> >> Still, it is reasonable to consider the impact of inconsistent >> conventions on the rest of the system outside of Rectangle. >> >> cheers -ben >> > On Wed, May 27, 2015 at 1:16 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > That's not all, many methods return new rectangles via Point's API, namely > Point>>{#corner: #extent: #rectangle:} > > I don't know if I can perform static analysis of the code (are there tools > for that in Pharo?) to see which methods exactly return Rectangle > > rectMethods := #(#corner: #extent: #rectangle:). > (Point methods select: [ :m | rectMethods includes: m selector ] > thenCollect: [ :m | m senders ]) flattened select: [ :s | s className = > #Rectangle ]. "an Array( > Rectangle>>#areasOutside: > Rectangle>>#withSideOrCorner:setToPoint:minExtent:limit: > Rectangle>>#withBottom: > Rectangle>>#bottom: > Rectangle>>#areasOverlapingOutside: > Rectangle>>#floor > Rectangle>>#allAreasOutsideList:startingAt:do: > Rectangle>>#scaledAndCenteredIn: > Rectangle>>#squishedWithin: > Rectangle>>#ceiling > Rectangle>>#withHeight: > Rectangle>>#rectanglesAt:height: > Rectangle>>#scaleFrom:to: > Rectangle>>#withLeft: > Rectangle>>#left: > Rectangle>>#withTop: > Rectangle>>#right: > Rectangle>>#top: > Rectangle>>#innerCorners > Rectangle>>#interpolateTo:at: > Rectangle>>#withWidth: > Rectangle>>#quickMergePoint: > Rectangle>>#withRight: > Rectangle>>#rotateBy:centerAt: > Rectangle>>#withSideOrCorner:setToPoint:minExtent:limit: > Rectangle>>#flipBy:centerAt:) > " > > This list is maybe a bit excessive (sometimes it returns self, sometimes new > rectangle -- e.g. floor). > Good Point ;) However the "-ed" convention doesn't make sense for many of those... #areasdOutside: , #areasedOutside , #areaOutsided: ? ... and #areasOutside is obviously a different rectangle than the original. The scope might be restricted to only those where the usual convention makes the names misleading, for example: #merge cheers -ben

May 27, 2015

Re: [Pharo-dev] Is there an official JSON parser/writer?

by Esteban A. Maringolo

2015-05-26 16:42 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >> On 26 May 2015, at 19:24, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >> It could be dead simple as specifying the class if the different JSON >> libraries shared a common to/from API selectors, but they don't. > Yes, it would be very good if there was such a thing as a common API for any reader/writer of any format (JSON, CSV, XML, STON, FUEL, ...). > > For a reader that is pretty easy, I think. Any reader object should understand > > #readFrom: <stream> (binary or character ReadStream as appropriate) +1 > And maybe also > > #readFromString: <string> It could be implemented using #readFrom: > #readFromBytes: <bytearray> This should also specify encoding, I think. > For the writer, I am not so sure. Maybe > #nextPut: <object> toStream: <stream> (binary or character ReadStream as appropriate) > And maybe also > #toString: <object> In this particular case it is all what I'd need, #fromString:/toString: > #toBytes: <object> > Note that the reader and writer objects could be different. This is also a requirement, particularly if you want to use NeoJSON/CSV > But like I said, I am not so sure about the API. We could try to define a Trait for this. I think it's more an Interface/protocol (contract) rather than a trait. But maybe because I don't know how a trait could be implemented to solve this. Regards! Esteban A. Maringolo

May 26, 2015