Moose-dev February 2017

moose-dev@list.inf.unibe.ch

24 participants
30 discussions

Cannot inspect Hashtable anymore
by Blondeau Vincent 23 Feb '17

23 Feb '17

Hello, I am currently working with Hashtable which is loaded by default in the Moose image. With the latest image, I tried to do: (HashTable new at: #a put:1;yourself) inspect. And I got an inspector with the red square of death... It seems that the visualization wants to get the item at the position 1 in the Hashtable but it cannot succeed because there is no item at 1 (obviously, it is an hashtable). Can someone with GtTools knowledge take a look at that? Thanks in advance, Cheers, Vincent !!!************************************************************************************* "Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

2 2

RTForceBasedLayout without overlapping arbitrary shapes
by Cris Fuhrman 23 Feb '17

23 Feb '17

Hello, Here's an example code using RTForceBasedLayout (from an example on this list a while back): ------------ view := RTView new. objects := RTObject withAllSubclasses. elements := (RTBox new size: #numberOfMethods; color: (Color blue alpha: 0.5)) elementsOn: objects. elements @ RTPopup new. view addAll: elements. RTForceBasedLayout on: elements. view @ RTDraggableView . view open ------------ It produces: [image: Inline image 1] Is it possible to have the RTForceBasedLayout such that the result has no overlapping boxes (or rectangles)? I realize setting force: to some large negative number will help, but it's not ideal because it creates a lot of empty space. In d3 (with SVG) there are a couple of examples of what I'd like to achieve (although they don't show edges): https://bl.ocks.org/mbostock/1062383 (arbitrary shapes) https://bl.ocks.org/mbostock/3231298 (arbitrary circles that stick to each other) The animation isn't important in my case. I wasn't sure where/how to apply the transform operation after a layout has been done in RTForceBasedLayout. Any hints? Here's what my graph looks like: [image: Inline image 2] The code I have to produce this is too much to post, so I used the example at the top. My code also uses RTForceBasedLayout new charge: -1000; on: b elements. Cheers!

1 0

Roassal: Locate a legend text below a line
by Hernán Morales Durand 21 Feb '17

21 Feb '17

Hi everybody, I have this complicated code to draw a line with separators at both ends, I try to put the legend text with #below but nothing is changed : | view e1 e2 l1 label | view := RTView new. label := RTLabeled new color: Color black; below; text: 'Class IIa'; yourself. e1 := RTBox new element color: Color black; height: 10; width: 1; yourself. e2 := RTBox new element color: Color black; height: 10; width: 1; yourself. l1 := RTStyledMultiLine new color: Color black; solidLine; edgeFrom: e1 to: e2. view addAll: (Array with: e1 with: e2 with: l1). l1 @ label. RTHorizontalLineLayout new on: view elements. view elements pairsDo: [ :a :b | b translateBy: 100 @ 0 ]. ^ view Any suggestion? Hernán

3 5

Re: software reingineering guidelines
by abdelghani ALIDRA 20 Feb '17

20 Feb '17

Hi, Thank you Nicolas and Anne for the hints/links @Alex Yes, genetic algorithms are “abstract” algorithms. I am actually talking about analysing the code of the frameworks for developing different genetic algorithms to solve all kinds of optimisation problems (knapsack, Traveling Salesman Problem but also “real life" problems : image processing, and many artificial intelligence problems) There are many GA frameworks. Some popular ones are : ECJ (https://cs.gmu.edu/~eclab/projects/ecj/), OpenBeagle (http://vision.gel.ulaval.ca/~parizeau/Publications/beagle-gecco.pdf), WatchMaker (http://watchmaker.uncommons.org/), HeuristicLab (http://dev.heuristiclab.com/)… Abdelghani Message: 4 Date: Thu, 16 Feb 2017 11:02:44 -0300 From: Alexandre Bergel <alexandre.bergel(a)me.com> To: Moose-related development <moose-dev(a)list.inf.unibe.ch> Subject: [Moose-dev] Re: software reingineering guidelines Message-ID: <9D54173C-8CD7-4873-A5F9-AC0EF570EAB2(a)me.com> Content-Type: text/plain; charset=utf-8 Ah ah! Sorry, I read too fast! But it is not clear what are you referring to when you mention “generic algorithm”? Can you give an example? Alexandre

1 0

How do you start Moose in Linux?
by Hernán Morales Durand 20 Feb '17

20 Feb '17

Hi guys, I downloaded Moose from http://moosetechnology.org/res/download/moose_suite_6_0-linux.zip My system info: $ uname -a Linux mvs-virtual-machine 3.19.0-69-generic #77~14.04.1-Ubuntu SMP Tue Aug 30 01:29:21 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: elementary OS Description: elementary OS Freya Release: 0.3.2 Codename: freya Tryng to run Moose 6.0 after unzipping: $ ./pharo unknown option: -plugins Usage: /home/mvs/moose_suite_6_0/bin/pharo [<option>...] [<imageName> [<argument>...]] /home/mvs/moose_suite_6_0/bin/pharo [<option>...] -- [<argument>...] ..... Available drivers: vm-sound-null vm-sound-ALSA vm-display-null vm-display-X11 How do you start Moose? Cheers, Hernán

2 2

Roassal: Why the grey outline?
by Hernán Morales Durand 18 Feb '17

18 Feb '17

The attached capture is the one implemented by the method #exampledoubleCurves. If you zoom the image you will notice the grey edge of each green and blue line. The same happens in #exampleVerticalAndHorizontalLines Is there a way to remove it the grey around each line? Cheers, Hernán

2 3

AthensCairoCanvas>>setPaint: receiving a "Color transparent"
by Hernán Morales Durand 17 Feb '17

17 Feb '17

I am using stable branch of Roassal2 in Pharo 5 and Win 8.1 to draw a figure for a paper (but the problem is the same loading the latest versions SmalltalkHub). When trying to open a grapher, I get a yellow-cross red morph window inside #setPaint: . The transparent color passed as argument came from AthensCairoSurface>>clear The same figure used to open without problems some months ago. All the Roassal examples open without problems. That's why here is the link to the fuel out stack with the halt previous to the crash : https://dl.dropboxusercontent.com/u/103833630/Debugger-Stack-AthensCairoCan… Is this a well-known bug? Any suggestion? Cheers, Hernán

3 7

Re: software reingineering guidelines
by Abdelghani Alidra 16 Feb '17

16 Feb '17

Hi Nicolas, > On 15 Feb 2017, at 12:00, moose-dev-request(a)list.inf.unibe.ch wrote: > > Message: 1 > Date: Tue, 14 Feb 2017 12:10:54 +0100 > From: Nicolas Anquetil <nicolas.anquetil(a)inria.fr <mailto:nicolas.anquetil@inria.fr>> > To: Moose-related development <moose-dev(a)list.inf.unibe.ch <mailto:moose-dev@list.inf.unibe.ch>> > Subject: [Moose-dev] Re: software reingineering guidelines > Message-ID: <f856fa35-917e-0a5a-a84c-41d89ebe83ac(a)inria.fr <mailto:f856fa35-917e-0a5a-a84c-41d89ebe83ac@inria.fr>> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi Abdou, > > not that I know of. > Moose provides the tools, the engineers must provide the "intelligence", > the processus to extract needed informatino. > > We currently have a project with Master students along these lines, but > they did not deliver it yet, so no experience result yet neither. I was thinking that people from Synectic (for instance) could have some valuable experience in this field (where to start from, a list of what to look for, how to look for it, the different reports, …) > > We recommended using Roassal (and explained how to use it) to try to get > an understanding of the “architecture” Yes, and use the queries to gets different metrics about the projects. maybe detect some (anti) patterns... > > Actually, asking them to explain HOW they got their results (As well as > WHAT results they got) could be interesting Definitely, this is part of the objectives too :) Maybe we could produce a sorte of practical guide to code analysis with Moose. > > nicolas

3 2

Re: software reingineering guidelines
by Abdelghani Alidra 16 Feb '17

16 Feb '17

Hi Alex, The idea is not to use genetic algorithms to improve software quality. Rather, to use Moose to enhance the design of existing frameworks for genetic algorithms. I have attached a brief description of the project to this email. It is in french but this is not a problem for you I think :) > On 15 Feb 2017, at 12:00, moose-dev-request(a)list.inf.unibe.ch wrote: > > Message: 2 > Date: Tue, 14 Feb 2017 08:13:22 -0300 > From: Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> > To: Moose-related development <moose-dev(a)list.inf.unibe.ch <mailto:moose-dev@list.inf.unibe.ch>> > Subject: [Moose-dev] Re: software reingineering guidelines > Message-ID: <6DD0680F-39CB-4E2D-8E42-9ECFF1D77542(a)me.com <mailto:6DD0680F-39CB-4E2D-8E42-9ECFF1D77542@me.com>> > Content-Type: text/plain; charset=utf-8 > > hi Abdelghani, > > How do you plan to use genetic algorithms ? How may it be used to improve software quality? > > Cheers, > Alexandre >

2 1

Book, Working Effectively with Legacy Code
by Ben Coman 14 Feb '17

14 Feb '17

Interesting to see this is the top mentioned book on stackoverflow. I wonder if Moose can facilitate any of its contained topics and maybe leverage its popularity. </randomThoughForTheDay> cheers -ben

3 6

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev February 2017