Moose-dev May 2012

moose-dev@list.inf.unibe.ch

21 participants
109 discussions

Re: Issue 482 in moose-technology: Use JNIPort to connect to VerveineJ
by moose-technology＠googlecode.com 30 Jun '13

30 Jun '13

Comment #2 on issue 482 by cy.delaunay: Use JNIPort to connect to VerveineJ http://code.google.com/p/moose-technology/issues/detail?id=482 you should now use that: Gofer new url: 'www.squeaksource.com/DelaunayTmpStuffs'; package: 'JNIPort-Initialization'; load. Gofer new url: 'www.squeaksource.com/DelaunayTmpStuffs'; package: 'JNIPortExample'; load. The initialization part still has to be fixed, sometimes it works, sometimes not.

2 4

Re: Issue 432 in moose-technology: Popup should appear only when a certain modifier key is pressed
by moose-technology＠googlecode.com 30 Jun '13

30 Jun '13

Comment #1 on issue 432 by tu...(a)tudorgirba.com: Popup should appear only when a certain modifier key is pressed http://code.google.com/p/moose-technology/issues/detail?id=432 Another option would be to have the rendering happening in another thread.

1 8

Re: Issue 736 in moose-technology: Moose crashes when importing Citezen (OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:)
by moose-technology＠googlecode.com 23 Jun '13

23 Jun '13

Updates: Summary: Moose crashes when importing Citezen (OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:) Comment #3 on issue 736 by tudor.gi...(a)gmail.com: Moose crashes when importing Citezen (OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:) http://code.google.com/p/moose-technology/issues/detail?id=736 (No comment was entered for this change.)

4 15

Issue 647 in moose-technology: Integrate torch package visualization
by moose-technology＠googlecode.com 23 Jun '13

23 Jun '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 647 by cy.delau...(a)gmail.com: Integrate torch package visualization http://code.google.com/p/moose-technology/issues/detail?id=647 Maybe it would be a good idea (?) to use / integrate the torch packages visualization in moose ? http://hal.archives-ouvertes.fr/docs/00/53/15/08/PDF/Uqui10a-Torch-WCRE10.p…

2 4

Re: Issue 469 in moose-technology: integrate Kontractor
by moose-technology＠googlecode.com 23 Jun '13

23 Jun '13

Updates: Labels: Milestone-4.3 Comment #4 on issue 469 by tudor.girba: integrate Kontractor http://code.google.com/p/moose-technology/issues/detail?id=469 What is the status of this?

1 3

Re: Issue 437 in moose-technology: Text is not affected by zooming in Mondrian
by moose-technology＠googlecode.com 23 Jun '13

23 Jun '13

Comment #1 on issue 437 by alexandre.bergel: Text is not affected by zooming in Mondrian http://code.google.com/p/moose-technology/issues/detail?id=437 Situation has been slightly improved, but this is clearly not satisfactory

1 4

importers page
by Tudor Girba 28 Apr '13

28 Apr '13

Hi, I created a page dedicated to importing instructions: http://www.moosetechnology.org/docs/importers A good example of how these instructions should look like can be found here: http://www.moosetechnology.org/docs/importers/importJavaWithinFusion We would need more detailed information about: - Import C# with PMCS http://www.moosetechnology.org/docs/importers/importCSharpWithPMCS - Import C with CAnalyzer http://www.moosetechnology.org/docs/importers/importCWithCAnalyzer Cheers, Doru -- www.tudorgirba.com "Obvious things are difficult to teach."

7 14

Re: Issue 382 in moose-technology: CMD + W does not close Mondrian window
by moose-technology＠googlecode.com 16 Mar '13

16 Mar '13

Comment #1 on issue 382 by tudor.gi...(a)gmail.com: CMD + W does not close Mondrian window http://code.google.com/p/moose-technology/issues/detail?id=382 This is still an issue and it hinders usability. Alex, could you take a look at it?

1 1

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

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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev May 2012