Moose-dev September 2012

moose-dev@list.inf.unibe.ch

25 participants
124 discussions

Issue 828 in moose-technology: [Roassal] ROMorph>>mouseOver: evt
by moose-technology＠googlecode.com 03 Mar '13

03 Mar '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 828 by google....(a)ben.coman.com.au: [Roassal] ROMorph>>mouseOver: evt http://code.google.com/p/moose-technology/issues/detail?id=828 Didn't bump into this as a runtime error, but browsing the code noticed that ROMorph>>mouseOver:evt calls super>>mouseOver: which does not exist.

2 4

Issue 825 in moose-technology: Roassal extents of text does not work with a tab character
by moose-technology＠googlecode.com 03 Mar '13

03 Mar '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 825 by google....(a)ben.coman.com.au: Roassal extents of text does not work with a tab character http://code.google.com/p/moose-technology/issues/detail?id=825 Referring to the following line in ROMondrianExample>>labeledRectangleOn: view node: ' With rectangle'. if I use the <space> key to insert before the 'W', then the outside border resizes fine. However if I use the <tab> key before the 'W', then the border does not size properly and cuts over the text. This is with ConfigurationOfRoassal.491.

1 6

Issue 824 in moose-technology: Roassal hover text should disappear when dragging node
by moose-technology＠googlecode.com 03 Mar '13

03 Mar '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 824 by google....(a)ben.coman.com.au: Roassal hover text should disappear when dragging node http://code.google.com/p/moose-technology/issues/detail?id=824 Taking for example ROMondrianExample >> labeledRectangle... Hovering over a node shows a popup with the node text, then moving away from the node makes the popup disappear - which is fine. Hovering over a node shows a popup with the node text, then dragging the node away doesn't close the popup - but I think it should. Additionally, if you drag the node to the popup and leave it there, then moving the mouse away does not close the popup either. Moose47 - ConfigurationOfMondrian.485

1 3

Issue 823 in moose-technology: buttons remains after ROMondiranExample >> chooseLayout
by moose-technology＠googlecode.com 03 Mar '13

03 Mar '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 823 by google....(a)ben.coman.com.au: buttons remains after ROMondiranExample >> chooseLayout http://code.google.com/p/moose-technology/issues/detail?id=823 From Roassal Easel > Example... clicking "chooseLayout" then clicking "Example" doesn't cleanup the buttons from "chooseLayout" Moose47 - ConfigurationOfRoassal.485

1 4

Issue 817 in moose-technology: Roassal overwriting window borders
by moose-technology＠googlecode.com 03 Mar '13

03 Mar '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 817 by google....(a)ben.coman.com.au: Roassal overwriting window borders http://code.google.com/p/moose-technology/issues/detail?id=817 Referring to attached image, you can see on the right hand side the window border is overwritten by graph. This occurs when the window is resized by dragging the bottom right corner. This does not occur when the window is large enough to fully encompass the graph and then inside the graph is moved past the edge of the window. This is with ConfigurationOfRoassal-AlexandreBergel.467 just going World > Tools > Roassal Easel Please fill in the labels with the following information: * Type-Defect, Type-Enhancement, Type-Engineering, Type-Review, Type-Other * Component-XXX Attachments: Roassal-overwriting-window-borders.png 67.8 KB

1 2

Issue 795 in moose-technology: Metrics lcom2 and lcom3
by moose-technology＠googlecode.com 03 Mar '13

03 Mar '13

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Famix New issue 795 by andreho...(a)gmail.com: Metrics lcom2 and lcom3 http://code.google.com/p/moose-technology/issues/detail?id=795 Moose should have metrics such as lcom2 and lcom3.

1 2

Issue 784 in moose-technology: opposite is missing in FAMIXLacalVariable>>parentBehaviouralEntity
by moose-technology＠googlecode.com 03 Mar '13

03 Mar '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 784 by fabrizio...(a)gmail.com: opposite is missing in FAMIXLacalVariable>>parentBehaviouralEntity http://code.google.com/p/moose-technology/issues/detail?id=784 Hi, I figured that parentBehaviouralEntity was implemented like that: FAMIXLacalVariable>>parentBehaviouralEntity <MSEProperty: #parentBehaviouralEntity type: #FAMIXBehaviouralEntity> <MSEComment: 'Behavioural entity declaring this local variable. belongsTo implementation'> ^parentBehaviouralEntity The opposite is missing. Is there a reason for that? Shouldn't it be like: FAMIXLacalVariable>>parentBehaviouralEntity <MSEProperty: #parentBehaviouralEntity type: #FAMIXBehaviouralEntity opposite: #localVariables> <MSEComment: 'Behavioural entity declaring this local variable. belongsTo implementation'> ^parentBehaviouralEntity Cheers, Fabrizio

1 2

Issue 720 in moose-technology: Classic Coder should highlight the extension categories
by moose-technology＠googlecode.com 03 Mar '13

03 Mar '13

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-GlamorousToolkit New issue 720 by tudor.gi...(a)gmail.com: Classic Coder should highlight the extension categories http://code.google.com/p/moose-technology/issues/detail?id=720 Currently, only classes and methods are shown as extensions using gray. Categories should be grayed out as well.

1 2

Issue 640 in moose-technology: Get the axis labels in a lineDiagram
by moose-technology＠googlecode.com 03 Mar '13

03 Mar '13

Status: New Owner: andreho...(a)gmail.com Labels: Type-Defect Priority-Medium Component-EyeSee New issue 640 by andreho...(a)gmail.com: Get the axis labels in a lineDiagram http://code.google.com/p/moose-technology/issues/detail?id=640 Get the axis labels in a lineDiagram in not working. See example below: | diag factory | factory := ESDummyFactory new. factory yValues: #(22 25 13 16 24 28 35 24 32 24 46 12). factory identifiers: #('January' 'February' 'March' 'April' 'Mai' 'June' 'July' 'August' 'September' 'October' 'November' 'December'). diag := ESDiagramRenderer new. (diag lineDiagram) y: #yValue; width: 500; height: 400; lineWidth: 5; defaultFontSize: 12; identifier: #identifier; labels: [:each | each]; defaultColor: Color blue; yAxisLabel: 'Clients'; regularAxis; deviationValue: 22; deviationDescription: 'avg 2006'; models: factory buildDummies. "startLineAtZero;" ^ diag open

1 2

Issue 637 in moose-technology: VerveineJ should show an invocation to the default constructor
by moose-technology＠googlecode.com 03 Mar '13

03 Mar '13

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ New issue 637 by tu...(a)tudorgirba.com: VerveineJ should show an invocation to the default constructor http://code.google.com/p/moose-technology/issues/detail?id=637 A call to the default constructor should be modeled like: - create a stub constructor in the target class - create an invocation to the constructor See the attached class for a sample. Attachments: DefaultConstructor.java 184 bytes

1 6

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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev September 2012