Moose-dev April 2014

moose-dev@list.inf.unibe.ch

42 participants
166 discussions

scaling roassal visualizations to fit the screen
by Tudor Girba 19 Apr '14

19 Apr '14

Hi, It would be great to have a straightforward way to zoom the visualization to fit the current screen. This would be particularly useful within the context of the inspector. Essentially, we would need a RTZoomToFit animation. Would there be of interest to provide this? Doru -- www.tudorgirba.com "Every thing has its own flow"

2 7

Issue 1054 in moose-technology: VisualWorksParseTreeVisitor and VisualWorksParseTreeMetricCalculator
by moose-technology＠googlecode.com 19 Apr '14

19 Apr '14

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1054 by damien.c...(a)gmail.com: VisualWorksParseTreeVisitor and VisualWorksParseTreeMetricCalculator http://code.google.com/p/moose-technology/issues/detail?id=1054 Do we need this VisualWorks prefix? What does it mean? -- 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

1 2

Issue 1064 in moose-technology: FMMSEParser>>#'tNAME' should accept underscore character
by moose-technology＠googlecode.com 19 Apr '14

19 Apr '14

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1064 by james.fo...(a)gemtalksystems.com: FMMSEParser>>#'tNAME' should accept underscore character http://code.google.com/p/moose-technology/issues/detail?id=1064 I parsed some valid C++ code with inFamix and it produced a file that included an underscore as part of a name. Modifying the method as follows fixed the problem: [ self next isAlphaNumeric or: [char == $_] ] whileTrue: [ buf nextPut: char ]. Type-Defect -- 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

1 3

Issue 1053 in moose-technology: VerveineJ exception on wrong command line
by moose-technology＠googlecode.com 19 Apr '14

19 Apr '14

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1053 by v.blonde...(a)gmail.com: VerveineJ exception on wrong command line http://code.google.com/p/moose-technology/issues/detail?id=1053 Describe the problem: what do you get? what do you expect? When we execute VerveineJ with an wrong command line, we get : Exception in thread "main" java.lang.IllegalStateException: invalid environment settings at org.eclipse.jdt.core.dom.ASTParser.getClasspath(ASTParser.java:256) at org.eclipse.jdt.core.dom.ASTParser.createASTs(ASTParser.java:988) at fr.inria.verveine.extractor.java.VerveineJParser.parse(Unknown Source) at fr.inria.verveine.extractor.java.VerveineJParser.main(Unknown Source) Instead of a message such as: Error: a wrong command line parameter is set How to reproduce the problem: step by step if necessary Launch VerveineJ with a wrong parameter (-h to list the aloowed parameters) Additional information: platform, context which may impact the problem Windows 7 - x64 Please fill in the labels with the following information: * Type-Enhancement * Component-VerveineJ -- 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

1 1

Issue 1052 in moose-technology: VerveineJ exception on wrong command line
by moose-technology＠googlecode.com 19 Apr '14

19 Apr '14

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1052 by v.blonde...(a)gmail.com: VerveineJ exception on wrong command line http://code.google.com/p/moose-technology/issues/detail?id=1052 Describe the problem: what do you get? what do you expect? How to reproduce the problem: step by step if necessary Additional information: platform, context which may impact the problem Please fill in the labels with the following information: * Type-Defect, Type-Enhancement, Type-Engineering, Type-Review, Type-Other * Component-XXX -- 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

1 2

Issue 709 in moose-technology: add Moose-Eclipse-Plugin in Moose
by moose-technology＠googlecode.com 19 Apr '14

19 Apr '14

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 709 by jannik.l...(a)gmail.com: add Moose-Eclipse-Plugin in Moose http://code.google.com/p/moose-technology/issues/detail?id=709 I don't know if we integrate it in Moose. But we need to do something: a web page on the Moose site, with how to load it.

1 3

Re: Issue 421 in moose-technology: Fame PragmaProcessor should accept selective properties
by moose-technology＠googlecode.com 19 Apr '14

19 Apr '14

Updates: Status: WontFix Comment #4 on issue 421 by tu...(a)tudorgirba.com: Fame PragmaProcessor should accept selective properties http://code.google.com/p/moose-technology/issues/detail?id=421 (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

1 0

Re: Issue 156 in moose-technology: The table presentation for Glamour should provide dynamic sorting and column manipulation
by moose-technology＠googlecode.com 19 Apr '14

19 Apr '14

Updates: Summary: The table presentation for Glamour should provide dynamic sorting and column manipulation Comment #14 on issue 156 by tudor.gi...(a)gmail.com: The table presentation for Glamour should provide dynamic sorting and column manipulation http://code.google.com/p/moose-technology/issues/detail?id=156 (No comment was entered for this change.)

1 1

Re: Issue 254 in moose-technology: inFusion default initializer export to MSE
by moose-technology＠googlecode.com 19 Apr '14

19 Apr '14

Updates: Labels: -Component-Tools Component-ExternalTools Comment #1 on issue 254 by tudor.gi...(a)gmail.com: inFusion default initializer export to MSE http://code.google.com/p/moose-technology/issues/detail?id=254 (No comment was entered for this change.)

1 2

Re: Issue 225 in moose-technology: History in Finder Evaluator pane
by moose-technology＠googlecode.com 19 Apr '14

19 Apr '14

Updates: Status: Fixed Labels: Milestone-5.0 Comment #4 on issue 225 by tu...(a)tudorgirba.com: History in Finder Evaluator pane http://code.google.com/p/moose-technology/issues/detail?id=225 This is now supported via the GTSnippets mechanism provided by the GTInspector. -- 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

1 0

← Newer
1
...
7
8
9
10
11
12
13
...
17
Older →

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