Moose-dev March 2010

moose-dev@list.inf.unibe.ch

21 participants
43 discussions

by Tudor Girba

Hi, I would like to announce "The Moose Book", a small book I have been working on since a couple of months. It is freely accessible online at: http://themoosebook.org The book is very much a work in progress, with only a few chapters being close to a reasonable state. Among them, the Glamour chapter was the one in which I invested the most effort. I will continue to write more contents during the following weeks. Feedback is more than appreciated :). Cheers, Doru p.s. Btw, the website is powered by Pier. Thanks, Lukas :) -- www.tudorgirba.com "Be rather willing to give than demanding to get."

14 years, 9 months

ConfigurationOfMetacello and OB

by Alexandre Bergel

Hi all, Installing ConfigurationOfMetacello requires the installation of OB. However, OB does not properly install in Core 1.1. Is there something we can do against that? It would be great to do so. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years, 9 months

[Pharo 1.1] Object>>initialExtent

by Alexandre Bergel

Hi! I do not have a solution, but Object>>initialExtent was recently deprecated and this causes great usability problem. This deprecation is very valuable for a clean UI separation. However, I have a warning deprecation each time a window is open. The reason stems from the method: SystemWindow>>initialExtent ^ model initialExtent For now, in my image, I suppressed this deprecation. Again, I do not have a clean solution. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years, 9 months

Adding ConfigurationOfRefactoringBrowser in ConfigurationOfMoose

by Alexandre Bergel

Hi! Moose depends on the refactoring browser. I added in baseline40beta6:: spec project: 'Refactoring browser' with: [ spec className: 'ConfigurationOfRefactoringBrowser'; file: 'ConfigurationOfRefactoringBrowser'; version: '1.1'; repository: 'http://www.squeaksource.com/rb' ]. Version 68 of ConfigurationOfMoose is in the repository. I also copied it to MonticelloRepository. With this dependency, Moose loads in PharoCore 1.1! Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years, 9 months

Port & transmission in Mondrian

by Alexandre Bergel

Dear List, Yesterday evening I found the time between two ground shakes to have a chat with Doru about porting some of the Glamour ideas in Mondrian. I would like to have a better support for interaction, useful for animation. In Glamour, the essential idea for interaction rely on 4 notions: Pane, Presentation, Port and Transmission. (Please, correct me if I am wrong). The Mondrian equivalent of Pane and Presentation are MOGraphElement and MOShape, respectively. Port and Transmission are left to be implemented. You can find them in the version 384. Here is a short test I wrote (all the test methods given here may be found in MOInteractionTest). -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= testSimpleTransmission | node1 node2 transmission | node1 := MONode on: 'test1'. node2 := MONode on: 'test2'. transmission := (MOTransmission new) origin: (node1 interaction port: #output); destination: (node2 interaction port: #input); yourself. (node1 interaction port: #output) value: 42. self assert: (node1 interaction port: #output) value = 42. self assert: (node2 interaction port: #input) value = nil. transmission transmit. self assert: (node1 interaction port: #output) value = 42. self assert: (node2 interaction port: #input) value = 42 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Then, I can write: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= testEmittingOnAPort2 | view transmission nodeSet1 nodeSet2 globalVariable node1 node2 interaction1 | view := MOViewRenderer new. interaction1 := view interaction on: MOMouseEnter do: [:ann | ann transmit: 42 onPort: #output ]; yourself. nodeSet1 := view nodes: (1 to: 20). node1 := nodeSet1 first. view interaction from: interaction1 port: #output do: [:ann | globalVariable := ann value ]. nodeSet2 := view nodes: (21 to: 40). node2 := nodeSet2 first. window := view open. self assert: (globalVariable isNil). node1 announce: (MOMouseEnter new). self assert: (globalVariable = 42). -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= But there is something wrong. In the second script, interaction1 should not be necessary, shouldn't it? Else it defeats the whole purpose of having port and transmission. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years, 9 months

Next steps for Cyrille

by Stéphane Ducasse

Hi guys here is a list of the next topic I would like cyrille to work on Radu's pyramid Better UI (for me this is still difficult to interact with moose - I will discuss with doru - sunday) How to apply visualizations to a group Does distribution map work? Porting EyeSee Report builder User Interface for Squale model Saving model to database (we have openDBX expert / Glorp?) Support for C# Algorithm librarie of VW Collection iterator -> Pharo YellowSubmarine (http://moose.unibe.ch/tools/yellowsubmarine) qui permet l'analyse de SVN. Alien help Rome for Moose Interface for Support for remediation Cost estimation Do you have other needs? Stef

14 years, 9 months

mondrian emergency :)

by Tudor Girba

Hi, I do not know exactly what happened, but it looks like simple graphs are not displayed anymore in Mondrian. Try the following and nothing happens: view := MOViewRenderer new. view nodes: #(1 2 3). view open However, this works: view := MOViewRenderer new. view node: 5 forIt: [view nodes: #(1 2 3)]. view open Alex, do you know what the problem is? Cheers, Doru -- www.tudorgirba.com "There are no old things, there are only old ways of looking at them."

14 years, 9 months

wizard-based customizable DistributionMap

by Cyrille Delaunay

Hi, I'm looking to do this customizable DistributionMap and I have several questions: -> When you say 'customizable', I understand that what should be customizable are: -> kind of properties we want to display -> Color associated to each property Am i right? I guess the kind of the parts (Packages , classes ...) and elements (Classes , methods ) to display, will depend on the moose-group we first clicked-on (to launch to visualization). -> What kind of property can be display in a DistributionMap? In the distributionMap paper, I saw that , for example, properties could be 'the owner of a file', or also the result of a clustering algorithm like 'linguistic concepts'. What kind of property should be propose by the wizard? -> Is it better to have a wizard-based customizable map or a full-dynamically-customizable visualization like the one of SystemComplexity ?

14 years, 9 months

Glamour depends on OB

by Alexandre Bergel

Is this really wished? I just stumbled on #starBrowser, #morphIcons. Maybe these static references could be removed. Note that I haven't checked other methods. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years, 9 months

how can I launch a visualization on a group of packages?

by stephane ducasse

I tried to click on the group label but I could not get group-based visualizations like distribution maps. Stef

14 years, 9 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev March 2010