Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

by roberto.minelli＠usi.ch

Hi, I'm using Roassal and I have the following question: Is there a way to have, in the same view, two different set of nodes with different layouts? For example 20 nodes layout'ed in a grid and other 20 nodes layout'ed using a tree but in the same view? Cheers, Roberto

12 years, 5 months

Issue 877 in moose-technology: DNU after parsing in PPBrowserInspector

by moose-technology＠googlecode.com

Status: New Owner: kurs....(a)gmail.com CC: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-PetitParser New issue 877 by kurs....(a)gmail.com: DNU after parsing in PPBrowserInspector http://code.google.com/p/moose-technology/issues/detail?id=877 - Open PPAllParserBrowser. - Select PPArithmeticParser. - Parse text, e.g. '1' - Go to the Debugger tab and select something - Parse the text again - Debugger with "MessageNotUnderstood: receiver of "first" is nil" appears

12 years, 5 months

Questions about the Famix Metamodel

by Anne Etien

Hi, I have studied the Famix metamodel and I have some questions / remarks: - There is a reference (I think even a composition) between ScopingEntities and Function. It thus means that by inheritance, a Module, a Namespace or a Package refer to function. Does it make sense for Namespace or Package? - Furthermore, there also exist a reference (I think even a composition) between Module and Function. In Module, how the distinction is done between the functions collection inherited from ScopingEntitiy and the specific one? - There is a reference between ImplicitVariable and BehaviouralEntity (parentBehaviouralEntity) whose opposite reference is named localVariables. However, in BehaviouralEntity, the reference named localVariables points to LocalVariables. And there is no inheritance between ImplicitVariable and LocalVariable. - There is a reference (globalVariables) (I think even a composition) between ScopingEntities and GlobalVariable with an opposite reference. There is also a reference between GlobalVariable and Module (parentModule) but without any opposite reference. Is this later an easy way to determine the module as a ScopingEntity to which a GlobalVariable belongs to or does it add something from the reference between GlobalVariable and ScopingEntities. It would be nice if someone can give me explanations. Anne PS: Sorry, if the questions have been already asked, I am new on the list.

12 years, 5 months

Issue 868 in moose-technology: VerveineJ does not set the container of a ParameterizedType correctly

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ Milestone-4.7 New issue 868 by tu...(a)tudorgirba.com: VerveineJ does not set the container of a ParameterizedType correctly http://code.google.com/p/moose-technology/issues/detail?id=868 Consider this case: ---ACalssUsedAsArgumentType.java package packageDefiningArgumentType; public class ACalssUsedAsArgumentType { } ---UserClass.java package userPackage; import packageDefiningArgumentType.*; public class userClass { public void m() { new ArrayList<ACalssUsedAsArgumentType>();} } VerveineJ sets the container of the ParameterizedType to be userPackage.userClass.m(). This is wrong. The issue gets even worse when we have multiple users of the same type. For example, if we also get: ---SecondUserClass.java package secondUserPackage; import packageDefiningArgumentType.*; public class SecondUserClass { public void m() { new ArrayList<ACalssUsedAsArgumentType>();} } ... with the current setup, we will get only one ParameterizedType, but we do not know which container we will end up with (the first or the second method). To fix the situation we have two options: 1. Continue to have only one instance of ParameterizedType and have the container point to the container of the ParameterizableClass. 2. Have multiple instances for ParameterizedTypes and keep the rest as it is. I think I prefer 1.

12 years, 5 months

Jenkins build became unstable: moose-latest-dev #1197

by admin＠moosetechnology.org

See <http://hudson.moosetechnology.org/job/moose-latest-dev/1197/>

12 years, 5 months

Issue 762 in moose-technology: VerveineJ keeps the history of old entities, when invoked from the Moose interface

by moose-technology＠googlecode.com

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium New issue 762 by usman.bh...(a)gmail.com: VerveineJ keeps the history of old entities, when invoked from the Moose interface http://code.google.com/p/moose-technology/issues/detail?id=762 First, I invoke VerveineJ from Moose menu to analyse a program A. It analyses the program and imports its entities in a moose model. I invoke VJ once more from moose menu to analyse another program B. When VJ is executed and the entities of program B are imported, I also find in the same model the entities related to the program A. So, VerveineJ keeps the history of old entities, when invoked from Moose interface. I think the problem can be resolved by deleting output.mse once VJ has finished its analysis and the entities are imported in a moose model.

12 years, 5 months

positive energy

by Tudor Girba

Hi, I notice a positive flood of good energy. It feels great! Let's keep it up like this. :) Cheers, Doru -- www.tudorgirba.com "Speaking louder won't make the point worthier."

12 years, 5 months

Issue 746 in moose-technology: VerveineJ should create parameters for methods with different signatures

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ Milestone-4.6 New issue 746 by tu...(a)tudorgirba.com: VerveineJ should create parameters for methods with different signatures http://code.google.com/p/moose-technology/issues/detail?id=746 In some cases, calls to external libraries get reified as methods with proper signatures, but without parameters. I am trying to reproduce this using the following example (in ad_hoc/MultipleSignatures.java): package ad_hoc; import java.io.PrintWriter; import java.io.StringWriter; public class MultipleSignatures { public void callToRegularPrintStackTrace(Throwable t) { t.printStackTrace() } public void callToPrintStackTraceWithParam(Throwable t) { t.printStackTrace(new PrintWriter(new StringWriter())) } } I encountered a similar code in a case study. However, in this case, I cannot even get the parser to recognize both printStackTrace calls.

12 years, 5 months

Issue 869 in moose-technology: Smalltalk code presentation does not populate the text port

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: chisvasi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.7 New issue 869 by tu...(a)tudorgirba.com: Smalltalk code presentation does not populate the text port http://code.google.com/p/moose-technology/issues/detail?id=869 Typing in the code editor should populate the text port. The test in GLMSmalltalkCodeMorphicTest>>testExplicitAcceptDoesNotAffectTextPort captures the problem. See: http://ci.moosetechnology.org/job/moose-latest-dev/lastCompletedBuild/testR…

12 years, 5 months

Issue 873 in moose-technology: PPAllParsersBrowser does not remember the sample from the inspector

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: kurs....(a)gmail.com Labels: Type-Defect Priority-Medium Milestone-4.7 Component-PetitParser New issue 873 by tu...(a)tudorgirba.com: PPAllParsersBrowser does not remember the sample from the inspector http://code.google.com/p/moose-technology/issues/detail?id=873 In the old PPBrowser, when switching between different parsers, the sample code remains available. This behaviour should be provided by the PPAllParsersBrowser, too. Jan, could you commit your fix for this issue? :)

12 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev