Moose-dev June 2013

moose-dev@list.inf.unibe.ch

36 participants
163 discussions

Issue 728 in moose-technology: VerveineJ places methods in the wrong classes

by moose-technology＠googlecode.com

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.

10 years, 5 months

Issue 704 in moose-technology: One click image has a squeak icon

by moose-technology＠googlecode.com

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.

10 years, 5 months

Issue 837 in moose-technology: ROCircle not constrained to equal dimensions

by moose-technology＠googlecode.com

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.

10 years, 5 months

Re: Issue 435 in moose-technology: Using RoelTyper for a better precision of method invocation

by moose-technology＠googlecode.com

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

10 years, 5 months

Issue 516 in moose-technology: System Complexity displays more than the classes in the group

by moose-technology＠googlecode.com

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.

10 years, 5 months

Issue 944 in moose-technology: EyeSee chart Legend issues

by moose-technology＠googlecode.com

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

10 years, 5 months

Issue 526 in moose-technology: Add explicit Interface in Famix

by moose-technology＠googlecode.com

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.

10 years, 5 months

Loading Hapax

by Hernán Morales Durand

Hello, I know that Hapax possibly isn't fully ported to Pharo, but running the Hapax tests causes my Moose 4.5 image to hang (I've loaded everything in the SqS Hapax repository). What image and package loading order should one use to load Hapax? I'm interested in the information retrieval part for natural language analysis, could that part be repackaged in its own package? Cheers, Hernán

10 years, 5 months

Issue 914 in moose-technology: withCenteredText not centering text correctly

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 914 by cunningh...(a)gmail.com: withCenteredText not centering text correctly http://code.google.com/p/moose-technology/issues/detail?id=914 When I ask for centeredText, I would expect it to be centered horizontally in the area that it is displaying in. Instead, it appears to be bumped up vertically above the location where it should be. If you add the following (missing?) method: ROMondrianExample>>centeredText " self new centeredText " | view | view := ROMondrianViewBuilder new. self centeredTextOn: view. view open and then run ROMondrianExample new centeredText, you will see the issue. How to reproduce the problem: step by step if necessary This is from the latest (2013-02-14) Moose Suite 4.7 from the MooseTechnology.org download page, on Windows 7 os. Labels: Type-Defect Component-Roassal -- 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

10 years, 5 months

Issue 904 in moose-technology: Roassal dragging subtrees (feature contribution)

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 904 by benjamin...(a)gmail.com: Roassal dragging subtrees (feature contribution) http://code.google.com/p/moose-technology/issues/detail?id=904 With a tree layout, when dragging an element I needed to drag all the children at the same time. I knocked up a solution sufficient to my needs in about 40 minutes - see attached changeset. I might be a nice general feature to add to Roassal but its a bit rough. It will likely need some critical love to polish it before integration. Later it might be made to work with ROSelection and multi-selected elements - but that is out of my scope for the moment. Attachments: RODraggableWithOthers.2.cs 1.3 KB

10 years, 5 months

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev June 2013