Moose-dev December 2011

moose-dev@list.inf.unibe.ch

32 participants
167 discussions

Issue 516 in moose-technology: System Complexity displays more than the classes in the group

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 516 by tudor.gi...(a)gmail.com: System Complexity displays more than the classes in the group http://code.google.com/p/moose-technology/issues/detail?id=516 Currently, the algorithm to identify the hierarchies does not limit the result to the current class group, but it takes all the subclasses of the superclass. This means that if you have a group with Object inside, you will end up with a system complexity with all classes.

11 years, 6 months

Issue 526 in moose-technology: Add explicit Interface in Famix

by moose-technology＠googlecode.com

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Enhancement Priority-Medium Milestone-4.3 New issue 526 by tudor.gi...(a)gmail.com: Add explicit Interface in Famix http://code.google.com/p/moose-technology/issues/detail?id=526 We should have a FAMIXInterface.

11 years, 6 months

Loading Hapax

by Hernán Morales Durand

Hello, I know that Hapax possibly isn't fully ported to Pharo, but running the Hapax tests causes my Moose 4.5 image to hang (I've loaded everything in the SqS Hapax repository). What image and package loading order should one use to load Hapax? I'm interested in the information retrieval part for natural language analysis, could that part be repackaged in its own package? Cheers, Hernán

11 years, 6 months

Issue 714 in moose-technology: VerveineJ does not produce correct values for classes in annotation instances

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-High Component-VerveineJ New issue 714 by tudor.gi...(a)gmail.com: VerveineJ does not produce correct values for classes in annotation instances http://code.google.com/p/moose-technology/issues/detail?id=714 Take a look at the example below: @XmlElement(name = "Time", required = true, type = String.class) protected Date time; The value of the third attribute of the annotation instance is the actual source code of the String class. Instead, it should be just the string 'String.class'. Ideally, we would get an actual reference, but the string would do for now.

11 years, 8 months

Issue 686 in moose-technology: Order in the Mondrian view DSL?

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 686 by step...(a)stack.nl: Order in the Mondrian view DSL? http://code.google.com/p/moose-technology/issues/detail?id=686 The order in which the view script has to be build up is not very clear. This is to be documented in http://www.themoosebook.org/book/internals/mondrian/scripting {shape, interaction} < nodes < edges * Type-Review * Component-Mondrian

11 years, 10 months

Issue 716 in moose-technology: span or size for each column in GLMTablePresentation

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium New issue 716 by jannik.l...(a)gmail.com: span or size for each column in GLMTablePresentation http://code.google.com/p/moose-technology/issues/detail?id=716 I am using GLMTablePresentation, and I would like to specify span or size for each column. To do that: Extend the GLMTablePresenation, and the associated rendering.

11 years, 10 months

Issue 748 in moose-technology: DistributionMap examples not working

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 748 by cy.delau...(a)gmail.com: DistributionMap examples not working http://code.google.com/p/moose-technology/issues/detail?id=748 When you try to execute the examples in the class side of DistributionMap, you get an error. This bug looks complicate and it does not seem to be related to distributionMap: When I debug and I go down to the method DistributionMap>>elementsWithProperty:inPart: If I insert this lign: (elementsAndPropertyValue keys detect: [:each | each == element]). it returns me one element. Then if I execute: (elementsAndPropertyValue at: element) I have a KeyNotFound error

11 years, 10 months

Issue 555 in moose-technology: DSM improve visualization

by moose-technology＠googlecode.com

Status: New Owner: jannik.l...(a)gmail.com Labels: Type-Defect Priority-Medium Component-DSM Milestone-4.4 New issue 555 by jannik.l...(a)gmail.com: DSM improve visualization http://code.google.com/p/moose-technology/issues/detail?id=555 I made the structure for DSM visualization. Now, I should create script for each and make communications between them coherent.

11 years, 10 months

Re: Issue 482 in moose-technology: Use JNIPort to connect to VerveineJ

by moose-technology＠googlecode.com

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.

11 years, 10 months

Re: Issue 432 in moose-technology: Popup should appear only when a certain modifier key is pressed

by moose-technology＠googlecode.com

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.

11 years, 10 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 December 2011