Moose-dev October 2012

moose-dev@list.inf.unibe.ch

25 participants
139 discussions

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

Issue 636 in moose-technology: VerveineJ should set hasClassScope
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 636 by tu...(a)tudorgirba.com: VerveineJ should set hasClassScope http://code.google.com/p/moose-technology/issues/detail?id=636 Static fields or methods should be marked with hasClassScope=true: public static int attributeWithClassScope; public static void methodWithClassScope() {} See the attached sample class. Attachments: ClassScope.java 179 bytes

1 3

Issue 838 in moose-technology: VerveineJ does not export non-javadoc comments
by moose-technology＠googlecode.com 01 Feb '13

01 Feb '13

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ New issue 838 by tudor.gi...(a)gmail.com: VerveineJ does not export non-javadoc comments http://code.google.com/p/moose-technology/issues/detail?id=838 VerveineJ exports javadoc comments for both types and methods. However, it does not export line comments like: //This is also a relevant comment

1 2

Issue 851 in moose-technology: Create a stable version for Moose and all its subparts
by moose-technology＠googlecode.com 29 Jan '13

29 Jan '13

Status: New Owner: ---- Labels: Type-Engineering Priority-Medium Maintainability Milestone-4.7 New issue 851 by tu...(a)tudorgirba.com: Create a stable version for Moose and all its subparts http://code.google.com/p/moose-technology/issues/detail?id=851 The configuration of Moose should be versionned, especially for a release. We have to investigate if Reloader is good enough for 4.7.

1 4

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