Moose-dev April 2014

moose-dev@list.inf.unibe.ch

42 participants
166 discussions

Inti in Pharo
by milton mamani 24 Apr '14

24 Apr '14

Hi all, I would like to show you the Inti, Inti is a cool visualization to compare and handle instances of MessageTally. This is just a demo, nothing in this mail is final. This image shows the Inti program in GTInspector [image: Imágenes integradas 1] The color mapping is explainning in http://www.humane-assessment.com/blog/?_k=W1xeAy75PKaNEd2G [image: Imágenes integradas 2] Purple nodes ares nodes that have the same class of the selected method. [image: Imágenes integradas 3] This is inti profiler in pharo, this allows your to compare 2 (or more) instances of MessageTally, and see the difference of this tallies. [image: Imágenes integradas 4] You can get this program executing the next piece of code: Gofer new smalltalkhubUser: 'azazael' project: 'inti'; package: 'ConfigurationOfInti'; load. (Smalltalk at: #ConfigurationOfInti) load. http://objectprofile.com/Inti.html Best regards, Milton

3 2

Build failed in Jenkins: moose-5.0 #1231
by admin＠moosetechnology.org 24 Apr '14

24 Apr '14

See <https://ci.inria.fr/moose/job/moose-5.0/1231/> ------------------------------------------ [...truncated 1151 lines...] replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: shallowCopy species new: species new: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: species new: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: species new: compare:with:collated: at:put: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: class class at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: class class class class at:put: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: class class class class class class at:put: elementsForwardIdentityTo: elementsForwardIdentityTo: stack page bytes 4096 available headroom 3300 minimum unused headroom 2216 (Segmentation fault) ./pharo: line 11: 4657 Aborted (core dumped) "$DIR"/"pharo-vm/pharo" --nodisplay "$@" Build step 'Execute shell' marked build as failure Archiving artifacts Recording test results

3 5

Moose #1218
by Alexandre Bergel 24 Apr '14

24 Apr '14

Hi! I’ve just tried the build 1218, but I cannot open the world menu. #label: is missing on some classes and EyeSee has still some ghosts… Anyone is working on it? I can have a look if no Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 4

Roassal: changing edge size
by Johan Fabry 24 Apr '14

24 Apr '14

Hi all, I am playing with highlighting edges (par of an arrow shape) by expanding their width, but I have found that when un-highlighting by contracting their width nothing happens. I have the code below: lastview is the view, edge is the compound shape of the edge and the arrowhead, highedge is the highlighted edge, if any. highlightEdge: aName |edge| edge := lastview edgeFromModel: aName. edge isNil ifFalse: [ highedge isNil ifFalse: [ highedge shape shape1 width: 1. highedge update.]. highedge := edge. edge shape shape1 width: 3. edge update. lastview signalUpdate.] With this code, thickened edges (width: 3) stay thick, even when made thin (width: 1). I suppose this is a bug. If not, how can I get the behavior that I want? Thanks in advance, ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

1 0

How to use Moose importers ?
by Blondeau Vincent 24 Apr '14

24 Apr '14

Hi, To create a Moose model from another source that used currently, I wanted to reuse the generic classes dedicated to model creation especially to have event logging (provided by MooseAbstractImporter) and the progress bar (provided by MooseTask). But I do not well understand how it is working: - I would like to use both but there is no inheritance relation between them - MooseTask is in Moose-Core package and not in package Moose-GenericImporter. Which one I should use ? I found an old thread talking about this: http://forum.world.st/An-analysis-of-the-MooseTask-hierarchy-third-attempt-… Moreover, for my import I have 2 types of tasks: the filling of the model and the creation of the links in the model, and for each one I have several tasks. Is there a tool to define the sorting of the tasks ? The class MooseCompositeImporterTask sounds good but seems dedicated to Smalltalk And what is the purpose of the *ImportingContext classes ? I would like to know how I can reuse this properly ? Thanks for your answers, 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

Roassal layouts and trachelShape MNU
by Johan Fabry 23 Apr '14

23 Apr '14

Hi all, I am having an issue with setting up a Roassal layout. I guess that to make force based layouts work, I have to add the line view edges do: [ :e | e trachelShape pushBack ]. However when I do this, there is a MNU in TRCompositeShape>>pushback, because the canvas instvar is nil. I am doing what is essentially the following code: “in a loop, adding to an edges collection” edges add: (((RTEdge from: efrom to: eto) + (RTLine new color: color) + (RTArrow new color: color)) @ (RTLabelled new text: trans name; color: color; view: view)). “later" “adding the edges to the view all at once and do layout magic" view addAll: edges. view edges do: [ :e | e trachelShape pushBack ]. “<— MNU” What should I do to fix this? ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

2 3

RTEdge class MNU
by Johan Fabry 23 Apr '14

23 Apr '14

Hola, I found a bug: RTEdge class>>on:from:to: produces a MNU because it does self on: aModel and that message is not understood. ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

2 1

Roassal: having changes in shapes
by Johan Fabry 23 Apr '14

23 Apr '14

Hola, for my visualization, I want to be able to change the color of a shape after the view has been opened, depending on a given condition. So I wrote something like below, where the instvar lastview holds the view that was opened. highlightNode: aName |node| node := lastview elementFromModel: aName. node isNil ifFalse: [ node shape color: (Color red). lastview signalUpdate.] Sadly, I do not see the shape changing color to red. What can I do to have this working? Thanks in advance, ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

2 2

Jenkins build became unstable: moose-5.0 #1208
by admin＠moosetechnology.org 23 Apr '14

23 Apr '14

See <https://ci.inria.fr/moose/job/moose-5.0/1208/>

1 0

Roassal Tip #2: Labeling bar with GraphET.
by Alexandre Bergel 23 Apr '14

23 Apr '14

Roassal Tip #2: Labeling bar with GraphET. You can use @RTLabelled for each bar elements. Consider the following example: -=-=-=-=-=-=-=-=-= | diagram | diagram := GET2DiagramBuilder new. diagram horizontalBarDiagram models: #(10 12 13 200 150 -13 149 -151); regularAxis. diagram build. "Pick the horizontal bars and add a label" diagram view elements do: [ :e | (e shape class == RTBox) ifTrue: [ e @ RTLabelled new right ] ]. diagram view open -=-=-=-=-=-=-=-=-= https://www.facebook.com/ObjectProfile/photos/a.341189379300999.82969.34054… Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

6 18

← Newer
1
...
5
6
7
8
9
10
11
...
17
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev April 2014