Moose-dev December 2015

moose-dev@list.inf.unibe.ch

33 participants
46 discussions

Roassal2: Unable to resolve project package for 'GlamourCore'

by Hernán Morales Durand

Hi guys, Installing stable Roassal2 from the Catalog Browser, in Pharo 5 (#50509), leads to a vanish dialog : Information There was an error while trying to install Roassal2. Installation was cancelled. and to the following message in Transcript: Loading 1.20 of ConfigurationOfRoassal2... ... Loaded -> ConfigurationOfGlamour-AndreiChis.217 --- http://smalltalkhub.com/mc/Moose/Glamour/main/ --- http://smalltalkhub.com/mc/Moose/Glamour/main/Error: Unable to resolve project package for 'GlamourCore'. It is likely that that the configuration referencing this project will not validate properly (see MetacelloToolBox class>>validateConfiguration:). Is Roassal2 configuration broken? Cheers, Hernán

9 years, 4 months

Stable version of GTDebugger bug on Moose 51

by Ferlicot D. Cyril

Hi, On Moose 51 if you try to save code on GTDebugger you will get a DNU because the method DebuggerModel>>#selectedMessageName call #messageName instead of #messageSeletor. This is pretty annoying. I don't really know what I need to change where. Can someone who knows better Moose can take a look please? Thank you. -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

9 years, 4 months

Default pane when we don't have a transmission in Glamour

by Ferlicot D. Cyril

Hi, For some tools in Synectique in Glamour we have some empty panes that are only rendered when they receive something on the entity port. So the user needs to click on an element of a list before the pane is rendered. I would like to know if it is possible to open a pane with some instructions/text util the transmission is not triggered instead of an empty space to fill the space and help the user? Thank you. -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

9 years, 4 months

Loading Roassal2 stable in Pharo 50510 fails

by Johan Fabry

Hi all, I was trying to load Roassal2 stable (ConfigurationOfRoassal2 load) in today’s Pharo 5 build but it fails with the following error: 'Unable to resolve project package for ''GlamourCore''. It is likely that that the configuration referencing this project will not validate properly (see MetacelloToolBox class>>validateConfiguration:).' If I try to load development (ConfigurationOfRoassal2 loadDevelopment, it complains that I will lose changes to Glamour-Morphic-Renderer, and then I get a warning: This package depends on the following classes: GLMFillWidthStrategy GLMFillWidthAndHeightStrategy GLMRigidStrategy What should I do to get a working version of Roassal2 for Pharo 5? ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

9 years, 4 months

Remainer: you can find us on Slack

by Alexandre Bergel

Hi! In case some of you are not aware, Slack is a super cool chat: http://slack4pharo.trentosur.com/ Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 4 months

View and action on GT?

by Alexandre Bergel

Hi! With GT, one can define particular view on an object using the pragma gtInspectorPresentationOrder: Can I do the same thing with actions? I mean, having a pragma to display a particular action, either as an icon, or as an entry in the menu next to it? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 4 months

spotter preview should be a real editor

by Nicolas Anquetil

I believe I already saw this request on the list. spotter preview should get the keyboard arrow events when one gave it focus by clicking in it and ctrl-S should actually save a method and not just remove the orange corner highlighting would be nice to ultimately, it could be possible to do without nautilus only by using spotter nicolas -- Nicolas Anquetil RMod team -- Inria Lille

9 years, 4 months

AgileVisualization - call for reviewers

by Alexandre Bergel

Dear All, As you may have heard, AgileVisualization is a book about the Roassal visualization engine. We hope to have the book released soon, within a couple of months. It would be fantastic to have feedback: http://agilevisualization.com The book is a fantastic result of the community. You guys made this possible, and we wish to thank you very much for this. Beers will flow at ESUG for everybody who comment on the chapters :-) We also have live discussion on Slack, channel #Roassal (see http://pharo.org/community on how to join Slack) Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 4 months

RTGradualDSM

by Alexandre Bergel

Hi All! We have introduced RTGradualDSM in Roassal. Simple example on numerical values: =-=-=-==-=-=-==-=-=-==-=-=-==-=-=-= dsm := RTGradualDSM new. values := { 1->#(2 3 1 5 6) . 2 -> #(1 2 1 1 1 1 4) . 3 -> #(1 2 5 3 2) . 4 -> #(2 5 1) . 5 -> #() . 6 -> #(4) } asDictionary. dsm objects: (1 to: 6). dsm score: [ :assoc | (values at: assoc key) occurrencesOf: assoc value ]. dsm =-=-=-==-=-=-==-=-=-==-=-=-==-=-=-= Example showing code authorship in the Glamour application: =-=-=-==-=-=-==-=-=-==-=-=-==-=-=-= classes := GLMLoggedObject withAllSubclasses. classesToAuthors := (classes collect: [ :cls | cls -> ((cls methods collect: #author) asSet sortedAs: #yourself) ]) asDictionary. authors := (classesToAuthors values flatCollect: #yourself) asSet sortedAs: #yourself. authorsToClasses := (authors collect: [ :anAuthor | anAuthor -> (classesToAuthors associations select: [ :as | as value includes: anAuthor ] thenCollect: #key) ]) asDictionary. b := RTGradualDSM new. b objectsX: classes. b objectsY: authors. b score: [ :assoc | (assoc value methods collect: #author) occurrencesOf: assoc key ]. b =-=-=-==-=-=-==-=-=-==-=-=-==-=-=-= Merry Christmas to all! Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 4 months

Design behind Moose-Algos-Graph

by Peter Uhnák

Hi, I'm curious about the design decisions behind Moose Graph Algorithms. Basically each algorithm (or at least many of them) has their own separate class for edges and/or vertices. This in theory makes the code more descriptive, however it also makes integration between various algorithms much harder, because now if I want to run two different algorithms on a single graph I have to convert them to the appropriate format. Wouldn't it make more sense to have the necessary behavior pluggable and have only a single representation of a graph? I'm sure there some other benefits to the current approach, however I do not see them. So all in all I would like to have a perhaps more functional (as in function) approach, as that more closely matches the mathematics behind the algorithm(s). Peter

9 years, 4 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev December 2015