Moose-dev July 2011

moose-dev@list.inf.unibe.ch

26 participants
178 discussions

MooseChef scoping should not exclude self loops

by Nicolas Anquetil

I want to reimplement software engineering metrics using moose chef instead of moose cook. for example to compute cohesion I would do (among other things): self queryAllOutgoingDependencies atClassScope withinMyPackage i.e. : 1- from a package (self) 2- get all its "outgoingdependencies" (outgoing does not mean going outside the package, this includes dependencies within th package) 3- put that at class level (because we are interested in dependencies between classes within or outside the package) 4- and filter those that are inside self I want the result to be all dependencies from classes within package self going to classes within package self . but (from the moose chef documentation): "The scope operators exclude self loops by default (this was also the default in Moose Cook). That is, the query result will not contain the receiver scope itself: you will not get something like PackageX -> PackageX in the result (the reason for this is that in general algorithms do not like graphs with self loops)." So: - should we change that default? - should I change my query? I believe if there is a method to exclude self loops (withoutSelfLoop), it should not be done automatically in some case let those who want it do it themselves. What say you? nicolas

13 years, 4 months

Re: Issue 464 in moose-technology: Actions that open new browsers should go through Renderer

by moose-technology＠googlecode.com

Updates: Labels: -Milestone-4.2 Comment #1 on issue 464 by tudor.gi...(a)gmail.com: Actions that open new browsers should go through Renderer http://code.google.com/p/moose-technology/issues/detail?id=464 (No comment was entered for this change.)

13 years, 4 months

verveinej support for java 7

by Tudor Girba

Hi, Is anyone (Nicolas :)) interested in investigating how difficult would it be to have Java 7 support in VerveineJ? Cheers, Doru -- www.tudorgirba.com "Be rather willing to give than demanding to get."

13 years, 4 months

[Gamour-seaside] right-click menu

by Cyrille Delaunay

Hello, I'm looking to have the selection right-click menu working with glamour-seaside (which is currently not implemented ?). Does somoene already woked on this or have any suggestions about how to do that ? After looking a bit, maybe it is possible to reuse the scripts used for the actions menu of a presentation (?)

13 years, 4 months

Issue 688 in moose-technology: Trait browser #build3StackerBis dynamic presentation does not work

by moose-technology＠googlecode.com

Status: Started Owner: damien.c...(a)gmail.com CC: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Glamour Difficulty-Easy New issue 688 by damien.c...(a)gmail.com: Trait browser #build3StackerBis dynamic presentation does not work http://code.google.com/p/moose-technology/issues/detail?id=688 I can't make the dynamic presentation in #build3StackerBis to work. Doru asked for simple example with numbers to show the problem.

13 years, 4 months

Issue 574 in moose-technology: Nodes with complex shapes do not position the children nodes with complex shapes properly

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: alexandr...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Mondrian Milestone-4.4 New issue 574 by tudor.gi...(a)gmail.com: Nodes with complex shapes do not position the children nodes with complex shapes properly http://code.google.com/p/moose-technology/issues/detail?id=574 Another issue related to complex shapes. Try the following code: view shape umlClass. view node: 'hello' forIt: [ view shape umlClass. view nodes: (1 to: 5). view verticalLineLayout ] You will see that the children now move properly with the parent node, but they are not positioned correctly. However, it works well with simple shapes for the children. A more complex example can be seen below: view shape umlClass. view node: 'hello' forIt: [ view shape umlClass. view nodes: (1 to: 5) forEach: [:each | view shape umlClass. view nodes: (1 to: each ). view verticalLineLayout ]. view verticalLineLayout ]

13 years, 4 months

[Glamour]

by Nick Chen

Hi I've been using Glamour to create a browser for a project that I am working on. I have encountered a weird rendering issue when using GLMCompositePresentation>>accordionArrangement. The GLMPresentations that I want to display get cut off at the bottom of the window. The image below shows the problem. http://forum.world.st/file/n3707211/accordion.png I have two GLMTextPresentations being displayed in the "Projecting" pane. One of them is called "Context Checking" and the other is "Definition". "Context Checking" and "Definition" are displayed using GLMCompositePresentation>>accordionArrangement. When I try to expand both of them, the one at the bottom runs off the screen and it gets cut off. I would have expected the renderer to space both GLMTextPresentations evenly in the available vertical space and add scroll bars to them when both are expanded. I am not sure which part of the code is causing the problem. I am not intimately familiar with how Glamour does its layout so any pointers to the cause or solution to the problem would be appreciated. A temporary fix that might work would be to set a minimal size for the window. I noticed that if the window is big enough i.e. half the screen then the text does not get cut off. How can I specify a minimal size for a GLMBrowser window? Thanks! -- Nick -- View this message in context: http://forum.world.st/Glamour-tp3707211p3707211.html Sent from the Moose mailing list archive at Nabble.com.

13 years, 4 months

petit: longest match parser

by Norbert Hartl

I have a grammar that is quite ambiguous. Ambiguities aren't solved easily because the grammar is quite complex and the task of resolving ambiguity is probably not possible. Ambiguities are supposed to be solved later after establishing some context in which it can be resolved. The biggest source of parsing failures I have because in the alignment of the matching rules a short match often prevents a long match from being found. And I wonder if I can look for the longest match with petit parser. Combining parsers with / always finds the first matching and | does not find anything if more than one rule matches. Any advize how to do this with petit? Norbert

13 years, 4 months

Issue 689 in moose-technology: DNU in Dependency Brower on an verveineJ MSE

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 689 by patrick....(a)gmail.com: DNU in Dependency Brower on an verveineJ MSE http://code.google.com/p/moose-technology/issues/detail?id=689 In the Dependency Browser I choose a package and see a correct map of providers but when I click on the Map of clients tab I get a debug window with FAMIXParameterizedType(Object)>>doesNotUnderstand: #potentialReferencingNamespaces. Expected : Map should update with clients info. Steps : Download latest verveineJ and latest Moose. verveinej.sh on a java source. Launch moose, import generated MSE. Select «All model classes», top right menu «Browse > Code with Dependencies» Dependency Browser open, click Map of clients tab and navigate package tree. Some entries trigger reported DNU. May be dependent on generated MSE or Java source parsed ? Debug log attached. Attachments: Debug.log 33.7 KB

13 years, 4 months

Issue 687 in moose-technology: Presentation choice flag

by moose-technology＠googlecode.com

Status: Accepted Owner: damien.c...(a)gmail.com CC: tudor.gi...(a)gmail.com Labels: Type-Enhancement Priority-Low Component-Glamour New issue 687 by damien.c...(a)gmail.com: Presentation choice flag http://code.google.com/p/moose-technology/issues/detail?id=687 A presentation flag could offer presentation parametrization in the rendering. The parametrization icons would appear vertically on the right side. For example, a code browser could have two flags on the methods pane: - show inherited methods (yes/no) - show traits methods (yes/no)

13 years, 4 months

← Newer
1
...
5
6
7
8
9
10
11
...
18
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev July 2011