Moose-dev April 2014

moose-dev@list.inf.unibe.ch

42 participants
166 discussions

Issue 528 in moose-technology: Remove Category Importer

by moose-technology＠googlecode.com

Status: Accepted Owner: ---- Labels: Type-Defect Priority-Medium Milestone-4.3 Component-Famix Component-SmalltalkImporter New issue 528 by jannik.l...(a)gmail.com: Remove Category Importer http://code.google.com/p/moose-technology/issues/detail?id=528 With RPackage, Category importer is useless, We should remove it. They are some referecnes in examples in DSM.

10 years, 6 months

Use of inFamix with Java

by James Foster

I’m trying to use Moose to analyze some C++ and Java code and will need some advice. First, I’ve tried to parse the Java code with inFamix and continue to get the error “The location of the project must be specified.” I’ve passed in as ‘-path’ every directory down to a Main.java file. James

10 years, 6 months

Issue 1002 in moose-technology: The treemap builder should support multiple types of nodes

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: alexandr...(a)gmail.com Labels: Type-Enhancement Priority-Medium Component-Roassal Milestone-5.0 New issue 1002 by tu...(a)tudorgirba.com: The treemap builder should support multiple types of nodes http://code.google.com/p/moose-technology/issues/detail?id=1002 TreeMaps are particularly useful to show leaf nodes within a nested parent nodes tree. For example, they can show classes within packages. They are less useful for showing only one type of nodes, like a class hierarchy given that the weight is only meaningful when applied to the leaf nodes. However, right now, we can specify nodes only with one block, weight with one block only and edges with another one block. This is less convenient. We should extend this to allow multiple sets of nodes. Consider this code: packages := RPackageOrganizer default packages select: [:each | each name beginsWith: 'AST']. classes := packages flatCollect: [:each | each definedClasses ]. ... builder weightBlock: [ :el | el isBehavior ifTrue: [ el linesOfCode + 1] ifFalse: [ 1 ] ]. builder nodes: (packages), (classes). builder nestingFromAssociations: ( (builder nodes select: [ :each | each isBehavior ]) collect: [ :each | (each) -> each package ]). builder drawOn: rawView . It would be better to have it like: builder weight: [ :el | el linesOfCode + 1] ]. builder nodes: classes. builder nodes: packages builder nest: classes in: [ :each | each package ]. builder drawOn: rawView . Note how nesting is defined following the same pattern as edges:from:to:, and how the weight is only applied to the next nodes. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

10 years, 6 months

Issue 1044 in moose-technology: Can't debug block local variables in GT debugger

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1044 by v.blonde...(a)gmail.com: Can't debug block local variables in GT debugger http://code.google.com/p/moose-technology/issues/detail?id=1044 Describe the problem: what do you get? what do you expect? In the GT Debugger, when you debug a block with a local variable; you can't read its value because the variable is unknown... How to reproduce the problem: step by step if necessary Write in a Workspace : 1 = 1 ifTrue: [ |local | local := 1 ] Debug It! Use the through button to go into the block. Try to inspect the local variable. Additional information: platform, context which may impact the problem Moose 5.0 latest - Ubuntu 13.10 - x64 Please fill in the labels with the following information: * Type-Defect * Component-GT-Debugguer * Milestone-5.0 -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

10 years, 7 months

Issue 1034 in moose-technology: Glamour easel and GTDebugger

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Critical New issue 1034 by alexandr...(a)gmail.com: Glamour easel and GTDebugger http://code.google.com/p/moose-technology/issues/detail?id=1034 Hi! I have spotted an important bug. If I enter the following in the Glamour Roassal easel: view nodes: (1 to: 20). self halt. A debugger is open, but I cannot step in. Apparently the code source is not accessible. This is a major regression... -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

10 years, 7 months

Roassal on the web

by Usman Bhatti

Hi Alex, Any updates of the project about constructing visualizations with Roassal for the web (with Amber?)? Did that project get accepted for GSoc? If not, do you plan to have a version of Roassal that could allow scripting visualizations on the web (with Seaside)? Because soon we'll need it ;). regards, usman

10 years, 8 months

Issue 1015 in moose-technology: GraphET should support lineWidth and legend

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1015 by usman.bh...(a)gmail.com: GraphET should support lineWidth and legend http://code.google.com/p/moose-technology/issues/detail?id=1015 Graphet should provide support for line width for line diagrams and a legend. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

10 years, 9 months

Re: Issue 228 in moose-technology: Nested browsers do not take "when", or "display" into account

by moose-technology＠googlecode.com

Updates: Labels: -Milestone-4.2 Comment #4 on issue 228 by tudor.gi...(a)gmail.com: Nested browsers do not take "when", or "display" into account http://code.google.com/p/moose-technology/issues/detail?id=228 (No comment was entered for this change.)

10 years, 9 months

Issue 1056 in moose-technology: Can't export as PNG with Roassal export button

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1056 by v.blonde...(a)gmail.com: Can't export as PNG with Roassal export button http://code.google.com/p/moose-technology/issues/detail?id=1056 Describe the problem: what do you get? what do you expect? When you add the export button, on a Roassal view and you select PNG export, you get: MessageNotUnderstood: ROAthensImageExporter class>>subclassRespondibility How to reproduce the problem: step by step if necessary ROMondrianViewBuilder new exportButton ; open. Clic on Export and Export as PNG. Additional information: platform, context which may impact the problem Moose 5.0 - W7 Please fill in the labels with the following information: * Type-Defect * Component-Roassal -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

10 years, 9 months

Re: Issue 995 in moose-technology: Roassal does not export the full PNG / SVG

by moose-technology＠googlecode.com

Updates: Summary: Roassal does not export the full PNG / SVG Comment #6 on issue 995 by tu...(a)tudorgirba.com: Roassal does not export the full PNG / SVG http://code.google.com/p/moose-technology/issues/detail?id=995 (No comment was entered for this change.) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

10 years, 9 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 April 2014