Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

renamings
by Tudor Girba 27 Mar '11

27 Mar '11

Hi, Please make sure to update Moose packages because I performed quite a bit of renaming by adding some Moose prefixes to classes. Cheers, Doru -- www.tudorgirba.com "Problem solving should be focused on describing the problem in a way that makes the solution obvious."

1 0

More on testing
by Alexandre Bergel 26 Mar '11

26 Mar '11

Hi Guys, I continued to test Moose-Core. Unfortunately, some of the tests I defined are wrongly located. For example, the class MooseModel is extended by the package Moose-Finder. I defined tests for those methods in the class MooseModelTest under a method category *moose-finder. This means that the package Moose-Finder defines some tests now. It was easier and quicker for me to do so. This is not good, and I am aware of it. I will fix the situation maybe this evening. I am a running an experiment and I do not want to have to explain the notion of class extension. I just need a beautiful screenshot with all covered methods. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 2

MooseModel class>>defaultModelPragma
by Alexandre Bergel 26 Mar '11

26 Mar '11

Can this method be deleted? It has no sender and only one implementer Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 2

Issue 563 in moose-technology: ImplicitVariable>>container should be changed to parentBehaviouralEntity
by moose-technology＠googlecode.com 26 Mar '11

26 Mar '11

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Famix Milestone-4.4 New issue 563 by tudor.gi...(a)gmail.com: ImplicitVariable>>container should be changed to parentBehaviouralEntity http://code.google.com/p/moose-technology/issues/detail?id=563 Currently, ImplicitVariable>>container points to a Type. It should be BehaviouralEntity instead.

1 1

[Glamour] Is there a way to set the size of the window
by Cyrille Delaunay 25 Mar '11

25 Mar '11

When opening a glamour browser , is there a way to specify the size (width - height) that the browser window should have ? Because it seems that it always open with the same default size

2 1

Issue 560 in moose-technology: parentType bug in Java model
by moose-technology＠googlecode.com 25 Mar '11

25 Mar '11

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 560 by usman.bh...(a)gmail.com: parentType bug in Java model http://code.google.com/p/moose-technology/issues/detail?id=560 Describe the problem: what do you get? what do you expect? I import Java mse (VerveineJ) and I want to run a small program to calculate all outgoing relationships of all the classes present in the mse. I get this message below: FAMIXClass(Object)>>doesNotUnderstand: #parentType Receiver: FontChooserMain in org::jhotdraw::samples::font (Type) Arguments and temporary variables: aMessage: parentType exception: MessageNotUnderstood: How to reproduce the problem: step by step if necessary import java mse with VerveineJ Add SoftEngMetrics package from Montecello. CohesionCouplingReport generateReportv7ForModel: 'JHotDraw_7.6-swing-awt-VerveineJ' fileName: 'JHotDraw_7.6-swing-awt-VerveineJ-',(Date today printString),'.csv'. Additional information: platform, context which may impact the problem Last three message from execution context: FAMIXClass(Object)>>doesNotUnderstand: #parentType Receiver: FontChooserMain in org::jhotdraw::samples::font (Type) Arguments and temporary variables: aMessage: parentType exception: MessageNotUnderstood: FAMIXClass>>parentType resumeValue: nil Receiver's instance variables: mooseID: 564997 state: a MooseDefaultState sourceAnchor: a FAMIXFileAnchor #noname sourceLanguage: nil comments: an Array(/** * FontChooserMain....:31:24Z rawcoder $ */ (comment ...etc... declaredSourceLanguage: nil name: 'FontChooserMain' isStub: false receivingInvocations: #() modifiers: a Set(#isPublic) parentPackage: nil outgoingReferences: #() types: #() incomingReferences: #() subInheritances: #() methods: an Array(FontChooserMain>>FontChooserMain() (Method) FontChooserMain>>...etc... container: org (Namespace)::jhotdraw (Namespace)::samples (Namespace)::font (Na...etc... superInheritances: an Array(FontChooserMain -> JPanel (Inheritance)) attributes: #() isInterface: nil FAMIXInvocation>>getReceivingFAMIXClass Receiver: FontChooserMain -> self#initComponents() (Invocation) Arguments and temporary variables: tmpReceiver: FontChooserMain.self (ImplicitVariable) belongsTo: nil Receiver's instance variables: mooseID: 679516 state: a MooseDefaultState sourceAnchor: nil sourceLanguage: nil comments: #() declaredSourceLanguage: nil previous: nil next: FontChooserMain -> self#add(Component) (Invocation) sender: FontChooserMain>>FontChooserMain() (Method) receiver: FontChooserMain.self (ImplicitVariable) receiverSourceCode: nil signature: 'initComponents()' candidates: an Array(FontChooserMain>>initComponents() (Method)) Please fill in the labels with the following information: * Type-Defect, Type-Enhancement, Type-Engineering, Type-Review, Type-Other * Component-XXX

5 12

Big kick in the coverage
by Alexandre Bergel 25 Mar '11

25 Mar '11

Hi! The coverage of Moose-Core has significantly increased. Several classes are now 100% covered. I added a red test that I would like some of you have a look at it. MooseModelTest>>testExportToFiltredBy I am not sure whether this is dead code or not. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 1

testFamixCoreMetaModel
by Alexandre Bergel 25 Mar '11

25 Mar '11

Hi! I added another red test. Sorry about that. The following raises en error: MooseModel famixCoreMetamodel Is this intended? I am not a metamodel generation guy. Maybe someone can have a look at this? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

MooseModel class>>importFrom: ...
by Alexandre Bergel 25 Mar '11

25 Mar '11

Hi! What these methods are about? Are they destructive? Can they be tested? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

Issue 552 in moose-technology: VerveineJ should have a build script
by moose-technology＠googlecode.com 24 Mar '11

24 Mar '11

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Engineering Priority-Medium Component-VerveineJ Milestone-4.4 New issue 552 by tudor.gi...(a)gmail.com: VerveineJ should have a build script http://code.google.com/p/moose-technology/issues/detail?id=552 The build script should be written with Ant and be responsible to: - build the jars - run the tests

1 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev