Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

by Guillaume Larcheveque

Stef and I think that Kontractor should be include in Moose by default to offer a tool for reducing title length. Do you think it's a good idea and do you know a better tool to do this? -- *Guillaume Larcheveque*

13 years

[glamour] react while choosing tab

by Esteban Lorenzano

Hi, when building some browsers, I often find that it would be useful to react in some way while choosing one tab. For instance, in glamoroust codebrowser (the "standard" one), when you choose between "Instance" and "Meta", you should react in some way, to display class definition or class instance definition (just like regular browsers). AFAIK, currently there is no way to achieve that. I think adding some protocol (#onSelect:, for instance) to composition presentations, has some sense... what do you think? cheers, Esteban

13 years, 1 month

Some metrics don't work after refining a MSE model

by Santiago Vidal

Hi, I'm trying to customize the import context when loading an mse model by using the method MooseModel>>importFromMSEStream: aStream filteredBy: anImportingContext. The main problem is that after creating the MSE model some metrics are missing. For example, numberOfLinesOfCode is always 0 for a class. When I create the model without the importing context the metrics are fine. The importing context that I'm using has the following fullNamesOfEntitiesToBeExtracted: 'FAMIX.Comment' 'FAMIX.Access' 'FAMIX.Inheritance' 'FAMIX.Invocation' 'FAMIX.Reference' 'FAMIX.Function' 'FAMIX.Method' 'FAMIX.Module' 'FAMIX.Namespace' 'FAMIX.Package' 'FAMIX.AnnotationType' 'FAMIX.Class' 'FAMIX.Enum' 'FAMIX.ParameterType' 'FAMIX.ParameterizedType' 'FAMIX.PrimitiveType' 'FAMIX.TypeAlias' 'FAMIX.EnumValue' 'FAMIX.GlobalVariable' 'FAMIX.ImplicitVariable' 'FAMIX.LocalVariable' 'FAMIX.Parameter' 'FAMIX.UnknownVariable' 'FAMIX.ParameterizableClass' 'FAMIX.AnnotationTypeAttribute' Any help? Thanks Cheers, Santiago -- Santiago Vidal

13 years, 1 month

Issue 787 in moose-technology: Vertical legend is not working

by moose-technology＠googlecode.com

Status: New Owner: andreho...(a)gmail.com Labels: Type-Defect Priority-Medium Component-EyeSee New issue 787 by andreho...(a)gmail.com: Vertical legend is not working http://code.google.com/p/moose-technology/issues/detail?id=787 Command verticalLegend (ESVerticalLegend) is not working.

13 years, 1 month

Issue 786 in moose-technology: MooseQueryResult>>intersection: is broken

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-MooseTools New issue 786 by anquetil...(a)gmail.com: MooseQueryResult>>intersection: is broken http://code.google.com/p/moose-technology/issues/detail?id=786 calling intersection between two MooseQueryResult produces an error because "MooseQueryResult is not a variable type" This is raised in basicNew: A possible workaround is to redefine MooseQueryResult>>intersection: aCollection | result | result := self class new. aCollection do: [ :each| ((self includes: each) and: [(result includes: each) not]) ifTrue: [ result add: each]]. ^ result But it might not be the best solution since I assume basicNew: might be called from other methods ...

13 years, 1 month

Emergency evaluator pops up on red tests

by Fabrizio Perin

Hi, I loaded all my stuff in the latest moose based on 1.4. All the tests of my PetitPHPParser are red. When I click on one red method the emergency evaluator pops up. To reproduce it: 1- grab the latest MooseJee from the ci: http://ci.moosetechnology.org/job/moose-latest-dev/ 2- load the petit php parser: Gofer new squeaksource: 'PetitPHPParser'; package: 'ConfigurationOfPetitPHPParser'; load. (Smalltalk at: #ConfigurationOfPetitPHPParser) perform: #loadDefault. 3- Run the tests of the php parser and click on any red method. How can I debug the problem? Any suggestions on how to proceed? Thanks, Fabrizio

13 years, 1 month

Mondrian forNode:do: on top level self

by Ben Coman

Background: I am trying to use Mondrian to visualize SomeContainerClass holding SomeOtherContainerClass that holds Equipment classes. So I was thinking each container class might have a method (#subviewOf: aView) which at some point does (aView forNode: self do:). Now I have come to the understanding that I am probably misusing #forNode:do: like that, and am continuing exploring that, but thought I would report the MNU that I encountered before moving on - just in case it was desirable to guard against such abuse. Steps to Reproduce: The essence of this distills down to the following in Mondrian Easel, where this first case works.... view nodes: (1 to: 20). view forNode: 2 do: [ view nodes: (50 to: 52) ] but this second case... view nodes: (1 to: 20). view forNode: view do: [ view nodes: (50 to: 52) ] gets MNU "removeAllEdges" Inserting 'self halt' between the two lines and tracing through to MONode>>nodeWith:ifAbsent shows the line... nodeLookedUp := self nodes detect: [:each | each model = anObject ] ifNone: aBlock. has in the first case (self nodes) as anOrderedCollection of 20 items and in the second (self nodes) is an empty Array. Just reporting for discussion. I am not sure if this would be considered a bug worth tracking, or just an abuse of the framework. Cheers, Ben

13 years, 1 month

jenkins do not read the xml reports from Arki

by Fabrizio Perin

Hi, I have a problem with automoose and jenkins. I basically use automoose to load some code than at the end of the st file I do: Gofer new renggli: 'hudson'; package: 'HudsonBuildTools'; load. "Run reports" report := MyReport on: MooseModel root first. report open. REPHudson runOn: report spec. SmalltalkImage current snapshot: true andQuit: true. What happen is that jenkins ends with a failure claiming that there are no test runned but the xml file generated by REPHudson is in the folder together with the Moose image. Do I miss something? Shouldn't jenkins report about the Arki report? Thanks for any help. Cheers, Fabrizio

13 years, 1 month

Load PetitGui with minimal dependency

by Norbert Hartl

Is there a way to load PetitGui with a smaller set of dependecies? Or is Magritte and Grease and etc. needed for the GUI? Loading PetitParser default loads default of Glamour, too. And that's quite a lot. thanks, Norbert

13 years, 1 month

TreeMapLayout in Mondrian

by Dennis Schenk

Hi, I'm working on a treemap layout in Mondrian. I created the basic functionality but am far from finished. For the current progress see the following screenshots: http://cl.ly/342z261g021c3X1j3X2b - A visualization of a very simple java system (https://github.com/mircealungu/SimpleSample) http://cl.ly/3H3x1K1y3O3j430S0a2z - A visualization of FAMIX itself. The following is an example of how one sets up the layout: viewTreemapOn: view > view nodes: self nodes. > > view edges: self nodes > from: [ :each | each ] > toAll: [ :each | each children ]. > > view layout: (MOTreeMapLayoutIncubation withWeightBlock: [ :e | > | model | > model := e model. > model isNil ifTrue: [ > 0. > ] > ifFalse: [ > e model entity numberOfLinesOfCode. > ]. > ]). The tree structure is given by the edges definition. The layout is created with a weight block (lines of code here, but could be anything). At the end I'd like to have something like: http://cl.ly/3v1L3O2a2n1H1C2x3J0V - TreeMap in Softwarenaut in VisualWorks. This is the first code that I'm writing with Mondrian, so I'm sure it could be improved in many areas. If anyone sees a problem with how I set up the layout. please do tell. If anyone wants to look at the code in detail please take a look at MOTreeMapLayoutIncubation in my Softwarenaut repository (I'm creating the tree map layout as part of the Softwarenaut port to Pharo): MCHttpRepository > location: 'http://www.squeaksource.com/Softwarenaut' > user: '' > password: '' The layout is currently in this repo, if it is more mature, it would be cool to add it to Mondrian itself. I'd like to make it as generic as possible. Now for some specific questions: The red colors you see in the screenshots is actually a bug. What I would like to do is only color the leaf nodes, but somehow (my guess is, it has something to do with shape caching?), it also colors the containment blocks. The way I do it is, while ging through the nodes (MONode) to draw them If it is a leaf > node shape fillColor: ((Color fromString: '#ff0000') alpha: 0.1). If it is a containment block: > node shape fillColor: (Color fromString: '#eeeeee'). But somehow all shapes (except the root node) are colored with the red translucent color. Does anyone have an idea why this could be the case? In general: I'm doing the styling of the nodes (also tried to add some interactivity) directly inside the layout, but I'm not sure if this is the Mondrian way to do this, since normally shape definitions and interaction is defined when creating the view. Is this okay? Or should I do this in another way? My thought was that I'd like to have a treemap layout with default, nice looking interactions, colors etc. without having to define them outside, when defining the view, so it needs as little setup as possible. Any inputs in general are greatly appreciated. Cheers, Dennis

13 years, 1 month

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev