Moose-dev January 2012

moose-dev@list.inf.unibe.ch

27 participants
137 discussions

Issue 672 in moose-technology: Customizable EyeSee should not show zero metrics
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-EyeSee New issue 672 by andreho...(a)gmail.com: Customizable EyeSee should not show zero metrics http://code.google.com/p/moose-technology/issues/detail?id=672 Customizable EyeSee should not show the metric when it is zero to all the entities (in axis x).

1 4

Issue 579 in moose-technology: [Kumpel] Incremental loading/Updating of Kumpel Projects
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Status: New Owner: junker.m...(a)gmail.com Labels: Type-Enhancement Priority-High Component-Kumpel New issue 579 by junker.m...(a)gmail.com: [Kumpel] Incremental loading/Updating of Kumpel Projects http://code.google.com/p/moose-technology/issues/detail?id=579 The KMPProjectHistory should offer the possibility to update the model to the current head revision.

1 3

Issue 543 in moose-technology: inFusion does not export in UTF-8
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 543 by tudor.gi...(a)gmail.com: inFusion does not export in UTF-8 http://code.google.com/p/moose-technology/issues/detail?id=543 MSE should be in UTF-8.

1 2

Re: Issue 551 in moose-technology: VerveineJ should export parameterized types
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Comment #2 on issue 551 by tudor.gi...(a)gmail.com: VerveineJ should export parameterized types http://code.google.com/p/moose-technology/issues/detail?id=551 Currently, ParameterizableClass is exported, but the instances are duplicated.

1 3

Issue 532 in moose-technology: inFusion should also export PrimitiveTypes
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 532 by tudor.gi...(a)gmail.com: inFusion should also export PrimitiveTypes http://code.google.com/p/moose-technology/issues/detail?id=532 void, long, int, boolean, char, char[] ... should be PrimitiveTypes, not Classes

1 3

Re: Issue 440 in moose-technology: FamixInvocation>>to should return candidates instead of receiver
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Updates: Status: Fixed Comment #2 on issue 440 by simon.de...(a)gmail.com: FamixInvocation>>to should return candidates instead of receiver http://code.google.com/p/moose-technology/issues/detail?id=440 Fixed as first part of MooseChef integration

1 1

Re: Issue 420 in moose-technology: Shape should be properly initialized to be useful without further parameter
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Comment #3 on issue 420 by tudor.gi...(a)gmail.com: Shape should be properly initialized to be useful without further parameter http://code.google.com/p/moose-technology/issues/detail?id=420 Is this still an issue?

1 3

Re: broken tests :)
by Tudor Girba 01 Feb '12

01 Feb '12

Hi Nicolas, Thanks a lot. I looked quickly into this. There is at least a simple problem: you are calling queryAllOutgoingDependencies, but this method does not exist anymore. I guess we should replace this with queryAllOutgoingAssociations. Is this due to a wrongly published refactoring? Cheers, Doru On 30 Jan 2012, at 23:58, Nicolas Anquetil wrote: > > Hi, > > I already spent 4 hours on this and am not anywhere near the solution :-( > I think I got myself on a wrong track and cannot get out of it. > > So I will ask your help see if you can do better. > > From what I understood, the problem is not related to the metrics, but comes > from accesses to global variables. > When one does a atClassScope on a queryResult containing an access to a global > variable, this one returns nil to the message claassScope (this is normal), > and for some reason that I cannot understand the nil gets inserted in the > storage of the queryResult in some cases (not always) in the form of a > SetElement containing it. > > > After lot of debugging, I finally got a method (LANInterface>>originate() ) > that accesses (among other things) SmalltalkGlobalVariable. > > My problem is that from here the behaviour seems heratic to me :-( > > - 'theMethod queryOutgoingAccesses atClassScope' works,so it does filter out > the nil coming from the 'SmalltalkGlobalVariable classScope' > - 'theMethod queryOutgoingReferences atClassScope' also works (there is no > global variable involved there anyway) > - 'theMethod queryStaticOutgoingAssociations atClassScope', does not work, it > contains a SetElement that contains a nil :-( > > What baffles me is that the definition of > FAMIXMethod>>queryStaticOutgoingAssociations is: > ^ self queryOutgoingAccesses > addAll: self queryOutgoingReferences; > "addAll: self queryOutgoingInheritances; -- inheritance does not > make sense here" > yourself. > > I even simplified it a bit to be more sure: staticAssociations = all access + > all inheritance. > > So taken together they exhibit the problem, but taking access alone access > does not exhibit it. > If I manually remove all references from the queryStaticOutgoingAssociations' > result, then it works again, which is logical because this is the same as > asking 'queryOutgoingAccesses' which already works > > Note: to remove elements from the resutls, I use an inspector on the > MooseQueryResult: 'storage := storage reject: [:a|a class == FAMIXReference]' > > Even stranger to me, if I manually remove only one of the references (eg: > 'storage := storage reject: [:a|a to name = 'String']'), then the result > starts to be correct again. > > > The test used to built the particular model I am wroking on is > MooseModelOverviewPyramidExtensionsTest>>testoverviewPyramidMetrics > > So here I am. > Maybe you can provide some fresh view on it? > > > On Monday 30 January 2012 15:09:12 Tudor Girba wrote: >> Thanks a lot. I ran the tests again and only 6 still have errors: >> http://ci.moosetechnology.org/job/moose-latest-dev/804/testReport/ >> >> Let us know how it works. >> >> Cheers, >> Doru >> >> >> >> On Mon, Jan 30, 2012 at 11:01 AM, Nicolas Anquetil >> >> <nicolas.anquetil(a)inria.fr> wrote: >>> I looked at it. >>> >>> Problem is that I forgot to migrate some metrics from SoftEngMetrics to >>> famix- extension-metrics. So it was correct in my image but not in the >>> standard one. >>> >>> This is corrected. >>> >>> I am still having problems with a test in FAMIXPropertiesTest >>> >>> It creates a strange situation where a MooseObjectQuery contains a >>> SetElement containing a SetElement containing nil. >>> So the problem might come from some unrelated place. >>> >>> First the test class FAMIXPropertiesTest gave me troubles because there >>> are two of them (one in Moose-Tests-SmalltalkImporter-KGB and one in >>> Moose-Tests- SmalltalkImporter-core). >>> >>> Second, I am teaching today, so I don't have lot of time to devote to >>> this at this moment. >>> >>> So I will leave that for further study tonight or tomorrow. >>> >>> >>> nicolas >>> >>> On Sunday 29 January 2012 22:32:54 Tudor Girba wrote: >>>> I forgot the link: >>>> http://ci.moosetechnology.org/job/moose-latest-dev/803/testReport/ >>>> >>>> Cheers, >>>> Doru >>>> >>>> On 29 Jan 2012, at 22:13, Tudor Girba wrote: >>>>> Hi Nicolas, >>>>> >>>>> Your latest changes produced some errors in tests. >>>>> >>>>> The troubled seems to be triggered by you removing some methods >>>>> from >>>>> FAMIXClassGroup, like abstractness. >>>>> >>>>> Could you take a look? >>>>> >>>>> Cheers, >>>>> Doru >>>>> >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> >>>>> "What is more important: To be happy, or to make happy?" >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "What we can governs what we wish." >>> >>> -- >>> Nicolas Anquetil -- RMod team >>> INRIA Lille Nord Europe > -- > Nicolas Anquetil -- RMod team > INRIA Lille Nord Europe -- www.tudorgirba.com "To utilize feedback, you first have to acquire it."

2 3

a problem with a MorphTreeMorph with headers
by Esteban Lorenzano 31 Jan '12

31 Jan '12

Hi, I have a problem for an application I have: I'm displaying a MorphTreeMorph who has a header and some columns, problem is when morph has a horizontal scrollbar and I need to go down, last element on list is covered by horizontal scroll bar and customer can't see his data. I need to solve this, but I don't know how, any help will be really appreciated. (the attached image shows my problem) thanks, Esteban

1 0

Updating a tab "brother" in glamour
by Santiago Vidal 31 Jan '12

31 Jan '12

Hi, I'm running the following example: | browser | browser := GLMTabulator new. browser row: [ :r | r column: #columnA; column: #columnB ]. browser transmit to: #columnA; andShow: [ :a | a list display: [" :model | "#('Value 1' 'Value 2' 'Value 3' 'Value 1') ] ]. browser transmit from: #columnA; to: #columnB; andShow: [ :a | a list titleIcon: GLMUIThemeExtraIcons glamorousBrowse ;title:'Data'; display:#('data A' 'data B' 'data C'). a text titleIcon: GLMUIThemeExtraIcons glamorousAccept; title:'Additional Information 1';display:'something'. a text titleIcon: GLMUIThemeExtraIcons glamorousAdd; title:'Additional Information 2';display:'add something'. ]. browser openOn: MooseModel root allModels anyOne. I want to show data in the tabs "'Additional Information 1" and "Additional Information 2" only if 'data A', 'data B', or 'data C' is selected in the tab 'Data'. what is the best way to do it? I could not find a similar example. Thanks, Cheers, Santiago -- Santiago Vidal

2 4

← Newer
1
...
6
7
8
9
10
11
12
13
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 January 2012