Moose-dev February 2012

moose-dev@list.inf.unibe.ch

22 participants
146 discussions

Issue 763 in moose-technology: VerveineJ generates wrong paths in source anchors when there is a . in the root folder
by moose-technology＠googlecode.com 16 Apr '12

16 Apr '12

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ Milestone-4.6 New issue 763 by tudor.gi...(a)gmail.com: VerveineJ generates wrong paths in source anchors when there is a . in the root folder http://code.google.com/p/moose-technology/issues/detail?id=763 Do this: - download: http://sourceforge.net/projects/jfreechart/files/latest/download - go to: jfreechart-1.0.14 - execute: /PATH_TO_verveine.extractor.java/verveinej.sh -Xmx2000m -- -autocp . . The fileNames all start with "0.14/./" instead of "./"

2 4

Issue 721 in moose-technology: VerveineJ should mark constructors
by moose-technology＠googlecode.com 13 Apr '12

13 Apr '12

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 721 by tu...(a)tudorgirba.com: VerveineJ should mark constructors http://code.google.com/p/moose-technology/issues/detail?id=721 Constructors should be marked with isConstructor.

2 10

Load PetitGui with minimal dependency
by Norbert Hartl 29 Mar '12

29 Mar '12

Is there a way to load PetitGui with a smaller set of dependecies? Or is Magritte and Grease and etc. needed for the GUI? Loading PetitParser default loads default of Glamour, too. And that's quite a lot. thanks, Norbert

4 10

TreeMapLayout in Mondrian
by Dennis Schenk 28 Mar '12

28 Mar '12

Hi, I'm working on a treemap layout in Mondrian. I created the basic functionality but am far from finished. For the current progress see the following screenshots: http://cl.ly/342z261g021c3X1j3X2b - A visualization of a very simple java system (https://github.com/mircealungu/SimpleSample) http://cl.ly/3H3x1K1y3O3j430S0a2z - A visualization of FAMIX itself. The following is an example of how one sets up the layout: viewTreemapOn: view > view nodes: self nodes. > > view edges: self nodes > from: [ :each | each ] > toAll: [ :each | each children ]. > > view layout: (MOTreeMapLayoutIncubation withWeightBlock: [ :e | > | model | > model := e model. > model isNil ifTrue: [ > 0. > ] > ifFalse: [ > e model entity numberOfLinesOfCode. > ]. > ]). The tree structure is given by the edges definition. The layout is created with a weight block (lines of code here, but could be anything). At the end I'd like to have something like: http://cl.ly/3v1L3O2a2n1H1C2x3J0V - TreeMap in Softwarenaut in VisualWorks. This is the first code that I'm writing with Mondrian, so I'm sure it could be improved in many areas. If anyone sees a problem with how I set up the layout. please do tell. If anyone wants to look at the code in detail please take a look at MOTreeMapLayoutIncubation in my Softwarenaut repository (I'm creating the tree map layout as part of the Softwarenaut port to Pharo): MCHttpRepository > location: 'http://www.squeaksource.com/Softwarenaut' > user: '' > password: '' The layout is currently in this repo, if it is more mature, it would be cool to add it to Mondrian itself. I'd like to make it as generic as possible. Now for some specific questions: The red colors you see in the screenshots is actually a bug. What I would like to do is only color the leaf nodes, but somehow (my guess is, it has something to do with shape caching?), it also colors the containment blocks. The way I do it is, while ging through the nodes (MONode) to draw them If it is a leaf > node shape fillColor: ((Color fromString: '#ff0000') alpha: 0.1). If it is a containment block: > node shape fillColor: (Color fromString: '#eeeeee'). But somehow all shapes (except the root node) are colored with the red translucent color. Does anyone have an idea why this could be the case? In general: I'm doing the styling of the nodes (also tried to add some interactivity) directly inside the layout, but I'm not sure if this is the Mondrian way to do this, since normally shape definitions and interaction is defined when creating the view. Is this okay? Or should I do this in another way? My thought was that I'd like to have a treemap layout with default, nice looking interactions, colors etc. without having to define them outside, when defining the view, so it needs as little setup as possible. Any inputs in general are greatly appreciated. Cheers, Dennis

3 14

Re: Issue 602 in moose-technology: Hapao should provide a legend in every window
by moose-technology＠googlecode.com 20 Mar '12

20 Mar '12

Updates: Summary: Hapao should provide a legend in every window Comment #3 on issue 602 by tudor.gi...(a)gmail.com: Hapao should provide a legend in every window http://code.google.com/p/moose-technology/issues/detail?id=602 Then let's name the issue for what it should do.

1 3

Issue 489 in moose-technology: Glamour: action list without the dropdown
by moose-technology＠googlecode.com 20 Mar '12

20 Mar '12

Status: New Owner: ---- CC: tudor.girba Labels: Type-Defect Priority-Medium New issue 489 by jfabry: Glamour: action list without the dropdown http://code.google.com/p/moose-technology/issues/detail?id=489 I have a Glamour pane that is an actionList where I do 5 populate:on:entitled:with: so that the pane has 5 buttons. Now what happens is that the pane also has a dropdown menu, with the same actions as the buttons. This menu should not be there according to Doru ...

1 2

Re: Issue 240 in moose-technology: Smalltalk importer scalability
by moose-technology＠googlecode.com 20 Mar '12

20 Mar '12

Comment #2 on issue 240 by tudor.gi...(a)gmail.com: Smalltalk importer scalability http://code.google.com/p/moose-technology/issues/detail?id=240 Anyone interested in picking this up?

1 1

Re: Issue 191 in moose-technology: Do not execute unnecessary transmissions
by moose-technology＠googlecode.com 20 Mar '12

20 Mar '12

Updates: Labels: -Milestone-4.2 Comment #5 on issue 191 by tudor.gi...(a)gmail.com: Do not execute unnecessary transmissions http://code.google.com/p/moose-technology/issues/detail?id=191 (No comment was entered for this change.)

1 1

Issue 774 in moose-technology: MNU error after selecting data using GLMStacker
by moose-technology＠googlecode.com 20 Mar '12

20 Mar '12

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 774 by santiago...(a)gmail.com: MNU error after selecting data using GLMStacker http://code.google.com/p/moose-technology/issues/detail?id=774 Running the script: | browser browserB| browser := GLMTabulator new. browser row: [ :r | r column: #columnA; column: #columnB ]. browser transmit to: #columnA; andShow: [ :a | a list display: #('Value 1' 'Value 2' 'Value 3' 'Value 1'). ]. browserB:=GLMStacker new. browserB aPane: #data; aPane: #AdditionalInformation1; aPane: #AdditionalInformation2. browserB transmit to:#data; andShow: [ :a | a titleIcon: GLMUIThemeExtraIcons glamorousBrowse ;title:'Data'. a list display:#('data A' 'data B' 'data C'). ]. browserB transmit from:#data; to:#AdditionalInformation1; andShow: [ :a | a titleIcon: GLMUIThemeExtraIcons glamorousAccept ;title:'Additional Information 1'. a text display:'something'. ]. browser transmit from: #columnA; to: #columnB; andShow: [ :a | a custom: browserB. ]. browser openOn: MooseModel root allModels anyOne. I received the following error after selecting "data A" "data B" or "data C": MessageNotUnderstood; receiver of "fullBounds" is nil.

1 1

Re: Issue 760 in moose-technology: Menssana does not understand set reference value...
by moose-technology＠googlecode.com 20 Mar '12

20 Mar '12

Updates: Summary: Menssana does not understand set reference value... Comment #2 on issue 760 by usman.bh...(a)gmail.com: Menssana does not understand set reference value... http://code.google.com/p/moose-technology/issues/detail?id=760 UndefinedObject(Object)>>doesNotUnderstand: #attributeKeyFrom:

1 7

← Newer
1
...
4
5
6
7
8
9
10
...
15
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 February 2012