Moose-dev October 2013

moose-dev@list.inf.unibe.ch

29 participants
128 discussions

Issue 728 in moose-technology: VerveineJ places methods in the wrong classes
by moose-technology＠googlecode.com 14 Nov '13

14 Nov '13

Status: New Owner: ---- CC: stephane...(a)gmail.com, anquetil...(a)gmail.com, usman.bh...(a)gmail.com Labels: Type-Defect Priority-Critical Component-VerveineJ New issue 728 by tu...(a)tudorgirba.com: VerveineJ places methods in the wrong classes http://code.google.com/p/moose-technology/issues/detail?id=728 For some reason, some methods are placed in the wrong classes. I did not manage to identify a standalone case, but it looks like if we have a case like below: public class A { ... public void m() { ... x() } } public class B { public void x() { ... } } public class C { ... } we sometimes get x as belonging to class C instead of B. The interesting part is that the invocation will go from A::m() to C::x(). This is a critical issue that stops us from using VerveineJ because the information is too unreliable.

5 18

Issue 704 in moose-technology: One click image has a squeak icon
by moose-technology＠googlecode.com 14 Nov '13

14 Nov '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 704 by alexandr...(a)gmail.com: One click image has a squeak icon http://code.google.com/p/moose-technology/issues/detail?id=704 Apparently, the icon of the one-click image available form Moose;s jenkins is the Squeak one.

1 4

Issue 837 in moose-technology: ROCircle not constrained to equal dimensions
by moose-technology＠googlecode.com 14 Nov '13

14 Nov '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 837 by google....(a)ben.coman.com.au: ROCircle not constrained to equal dimensions http://code.google.com/p/moose-technology/issues/detail?id=837 Currently ROCircle acts more like a hypothetical ROEllipse, since it is not constrained to force dimensions to be equal. The following might be a worthwhile test case... --- | rawView element1 element2 | element1 := (ROElement on: '1' ). element1 + ROCircle. element1 width: 200; height: 100. self assert: ( element1 height = 200). element2 := (ROElement on: '2' ). element2 width: 200; height: 100. element2 + ROCircle. "Swapped order with above line" self assert: ( element2 height = 200). "Should be true. Currently not." "optional - following not part of test - just visual feedback" rawView := ROView new. rawView add: element1. rawView add: element2. ROVerticalLineLayout on: rawView elements. rawView open. --- The first assert can be made to work by adding the following... ---- ROCircle>>extent: anExtentPoint | max | max := anExtentPoint x max: anExtentPoint y. extent := max @ max. next extent: anExtentPoint --- The second assert, I'm not sure yet about resolving the fail.

1 3

Issue 986 in moose-technology: Roassal Athens uses the default Morph logic for PNG export
by moose-technology＠googlecode.com 13 Nov '13

13 Nov '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Roassal Milestone-4.9 New issue 986 by tu...(a)tudorgirba.com: Roassal Athens uses the default Morph logic for PNG export http://code.google.com/p/moose-technology/issues/detail?id=986 Even though Athens can render with nice anti aliasing, when exporting to PNG, the default logic is being used: ROMorphicPlatform>>imageExporterClass ^ ROPharoImageExporter We should use the nice rendering of Athens for the export. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 6

Re: Issue 435 in moose-technology: Using RoelTyper for a better precision of method invocation
by moose-technology＠googlecode.com 11 Nov '13

11 Nov '13

Updates: Labels: Component-SmalltalkImporter Comment #4 on issue 435 by tudor.gi...(a)gmail.com: Using RoelTyper for a better precision of method invocation http://code.google.com/p/moose-technology/issues/detail?id=435 It seems that RoelTyper does not work for all classes. Try this code for getting the classes that raise an error: classes := Dictionary new. Object withAllSubclassesDo: [:each | [(TypeCollector typeInstvarsOfClass: each )] on: Error do: [:error | classes at: each put: error ]]. classes inspect

1 5

Issue 516 in moose-technology: System Complexity displays more than the classes in the group
by moose-technology＠googlecode.com 11 Nov '13

11 Nov '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 516 by tudor.gi...(a)gmail.com: System Complexity displays more than the classes in the group http://code.google.com/p/moose-technology/issues/detail?id=516 Currently, the algorithm to identify the hierarchies does not limit the result to the current class group, but it takes all the subclasses of the superclass. This means that if you have a group with Object inside, you will end up with a system complexity with all classes.

1 4

Issue 944 in moose-technology: EyeSee chart Legend issues
by moose-technology＠googlecode.com 11 Nov '13

11 Nov '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 944 by cunningh...(a)gmail.com: EyeSee chart Legend issues http://code.google.com/p/moose-technology/issues/detail?id=944 When creating a chart, I would like to include a legend, and EyeSee allows for this. However, the legend is always top left of chart (even with #legendBelow sent) and obscures the Y axis label; or it is to right (when #verticalLegend is sent) and writes over the right axis if that axis is used. Example code for first issue: i := 0. series1 := OrderedCollection new: 7. 20130601 to: 20130607 do: [ :dt| series1 add: { dt. i := i + 1. }]. series2 := OrderedCollection new: 7. i := i + 1. 20130601 to: 20130607 do: [ :dt| series2 add: {dt. i := i -1. }]. series3 := OrderedCollection new: 7. 20130601 to: 20130607 do: [ :dt| series3 add: {dt. 4. }]. colors := { Color red. Color blue. Color green. }. parts := OrderedCollection new: 3. { series1. series2. series3. } withIndexDo: [ :ls :ind | parts addLast: (ESLineDiagram new y: #second; preferredAxisMaxY: 7; lineWidth: 2; models: ls; defaultColor: (colors at: ind); yourself). ind = 1 ifTrue: [ parts last identifier: #first; rotatedLabels: true; xAxisLabel: 'Dates'; regularAxis; axisColor: Color black; yAxisLabel: 'Some Measurement that will Collide with Legend' ]. ]. chart := ESDiagramRenderer new. composite := chart compositeDiagram. parts do: [ :chartPart| composite add: chartPart ]. composite yPadding: 30; height: 600; width: 800. parts first displayLegend: true; legendBelow; colorDict: (Dictionary keys: #( 'Series1' 'Series2' 'Series3') values: colors). chart open. Example code for second (vertical) issue: i := 0. series1 := OrderedCollection new: 7. 20130601 to: 20130607 do: [ :dt| series1 add: { dt. i := i + 1. }]. series2 := OrderedCollection new: 7. i := i + 1. 20130601 to: 20130607 do: [ :dt| series2 add: {dt. i := i -1. }]. series3 := OrderedCollection new: 7. 20130601 to: 20130607 do: [ :dt| series3 add: {dt. 4. }]. seriesRight := OrderedCollection new: 7. 20130601 to: 20130607 do: [ :dt| seriesRight add: {dt. 6. }]. colors := { Color red. Color blue. Color green. Color yellow. }. parts := OrderedCollection new: 4. { series1. series2. series3. } withIndexDo: [ :ls :ind | parts addLast: (ESLineDiagram new y: #second; preferredAxisMaxY: 7; lineWidth: 2; models: ls; defaultColor: (colors at: ind); yourself). ind = 1 ifTrue: [ parts last identifier: #first; rotatedLabels: true; xAxisLabel: 'Dates'; regularAxis; axisColor: Color black; yAxisLabel: 'Some Measurement that will Collide with Legend' ]. ]. parts addLast: (ESLineDiagram new rightYAxis y: #second; preferredAxisMaxY: 7; lineWidth: 2; models: seriesRight; defaultColor: colors last; regularAxis; axisColor: Color black; yAxisLabel: 'Another Measurement that will Collide with Legend' yourself). chart := ESDiagramRenderer new. composite := chart compositeDiagram. parts do: [ :chartPart| composite add: chartPart ]. composite yPadding: 30; height: 600; width: 800. parts first displayLegend: true; verticalLegend; colorDict: (Dictionary keys: #( 'Series1' 'Series2' 'Series3' 'Series4') values: colors). chart open. This occurs in the current Moose dev (4.8 of recent origin), on Windows. Type-Defect Component-EyeSee -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 3

Issue 992 in moose-technology: FMNullMultivalueLink does not support union: (FMNullMultivalueLink cannot have variable sized instances)
by moose-technology＠googlecode.com 11 Nov '13

11 Nov '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 992 by anne.et...(a)gmail.com: FMNullMultivalueLink does not support union: (FMNullMultivalueLink cannot have variable sized instances) http://code.google.com/p/moose-technology/issues/detail?id=992 Describe the problem: what do you get? what do you expect? Here is the code that we want to execute to combine in a same collection of a given class its incomingReferences and its superInheritances: (aClass incomingReferences) union: (aClass superInheritances) If the first set of the union operator is empty, it is a FMNullMultivalueLink. If the second set is not empty, the union: message creates a FMNullMultivalueLink with the size of this second set. However, it is not possible to create a FMNullMultivalueLink with a specified size. We would like that its creates a FMMultivalueLink with the specified size. Please fill in the labels with the following information: * Type-Defect, Type-Enhancement, Type-Engineering, Type-Review, Type-Other * Component-MooseCore -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 3

Issue 984 in moose-technology: Update the zero conf scripts
by moose-technology＠googlecode.com 11 Nov '13

11 Nov '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 984 by chisvasi...(a)gmail.com: Update the zero conf scripts http://code.google.com/p/moose-technology/issues/detail?id=984 Now that moose 4.8 is released the zero conf scripts should be updated accordingly. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

2 4

Issue 526 in moose-technology: Add explicit Interface in Famix
by moose-technology＠googlecode.com 11 Nov '13

11 Nov '13

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Enhancement Priority-Medium Milestone-4.3 New issue 526 by tudor.gi...(a)gmail.com: Add explicit Interface in Famix http://code.google.com/p/moose-technology/issues/detail?id=526 We should have a FAMIXInterface.

1 6

← Newer
1
2
3
4
5
6
7
8
...
13
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev October 2013