Moose-dev June 2011

moose-dev@list.inf.unibe.ch

32 participants
176 discussions

Issue 544 in moose-technology: inFusion should point the C++ source text to the implementation, not definition

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 544 by tudor.gi...(a)gmail.com: inFusion should point the C++ source text to the implementation, not definition http://code.google.com/p/moose-technology/issues/detail?id=544 Currently, the source anchor for a c/c++ class or methods points to the definition in the header. It should point to the implementation from the c/cpp file.

12 years, 7 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.)

12 years, 8 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 ]

12 years, 8 months

Issue 619 in moose-technology: RPackage should deal with unknown extensions

by moose-technology＠googlecode.com

Status: Accepted Owner: ---- Labels: Type-Defect Priority-Medium RPackage New issue 619 by stephane...(a)gmail.com: RPackage should deal with unknown extensions http://code.google.com/p/moose-technology/issues/detail?id=619 In MC we have - AST-Core - AST-Semantic but no - AST-Compiler- whatever so when we get *AST-Compiler-Overrides..... clearly this is a problem. We should create a new package with the extension names.

12 years, 8 months

column:span:evaluated: for GLMTablePresentation

by jannik.laval

Hi Doru, I am using GLMTablePresentation, and I would like to specify span or size for each column. Is it possible to do it easily ? Thank you, Jannik

12 years, 8 months

Issue 620 in moose-technology: RPackageOrganizer should have a better public API for unregistering package

by moose-technology＠googlecode.com

Status: Accepted Owner: ---- CC: cy.delau...(a)gmail.com Labels: Type-Defect Priority-Medium RPackage New issue 620 by stephane...(a)gmail.com: RPackageOrganizer should have a better public API for unregistering package http://code.google.com/p/moose-technology/issues/detail?id=620 in particular one that assembles all the elementary steps - unregister back pointer (class mapping) - unregister class extension mapping

12 years, 8 months

Issue 646 in moose-technology: More readable code for classes

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 646 by cy.delau...(a)gmail.com: More readable code for classes http://code.google.com/p/moose-technology/issues/detail?id=646 In the moose panel, when I browse a class and click on the source code tab , it shows me a big text with className, attributes and all the method. Maybe this one could be more readable by separating more 'clearly' thedifferent parts

12 years, 8 months

Issue 639 in moose-technology: Remove the border around each bar

by moose-technology＠googlecode.com

Status: New Owner: andreho...(a)gmail.com Labels: Type-Enhancement Priority-Medium Component-EyeSee New issue 639 by andreho...(a)gmail.com: Remove the border around each bar http://code.google.com/p/moose-technology/issues/detail?id=639 Add the possibility to remove the border around each bar in a bar diagram.

12 years, 9 months

Issue 633 in moose-technology: Closing a morphic tab of an Accumulator browser, does not populate activeEntity properly

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.5 New issue 633 by tu...(a)tudorgirba.com: Closing a morphic tab of an Accumulator browser, does not populate activeEntity properly http://code.google.com/p/moose-technology/issues/detail?id=633 How to reproduce: 1. Execute: browser := GLMBasicExamples new accumulator. browser openOn: 42. ((browser paneNamed: #one) port: #strongSelection) value: 50. ((browser paneNamed: #one) port: #strongSelection) value: 60. 2. Close the first tab (50) 3. You will get 50 selected on the list to the left (while it should be 60)

12 years, 9 months

exporting model to mse? do they keep the metrics

by Stéphane Ducasse

Hi guys I could not find metrics in the saved MSE metrics like LOC that cannot be computed by moose. Are metrics saved? I remember writing tests to make sure that this was correct. In addition it would be good to be able to select some metrics to be exported to other formats. Stef

12 years, 9 months

← Newer
1
...
4
5
6
7
8
9
10
...
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 June 2011