- Moose-dev - INF Mailman

by Alexandre Bergel

Hi! Doru, would it make sense to have RTBuilder>>build returns the view? Like that, there is no need of the last line in: -=-=-=-=-=-=-=-= | b | b := RTGraphBuilder new. … b build. b view -=-=-=-=-=-=-=-= Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

11 years, 2 months

3
6
0 0

Issue 1068 in moose-technology: MNU: GLMTablePresentation>>tags:

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1068 by anne.et...(a)gmail.com: MNU: GLMTablePresentation>>tags: http://code.google.com/p/moose-technology/issues/detail?id=1068 Describe the problem: what do you get? what do you expect? There is a MNU when using the metabrowser. How to reproduce the problem: step by step if necessary Open the metabrowser. Click on any entity, the debugger opens. The right column of the metabrowser is empty. Nothing appear. Additional information: platform, context which may impact the problem Due to the CI problems, I am on version 1207 of Moose 5.0, with the last version of Glamour. 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

11 years, 2 months

1
2
0 0

Use of inFamix with C++

by James Foster

I’m trying to use Moose to analyze some C++ and Java code and will need some advice. After some effort I’ve been able to parse a directory containing *.cp files and open it in Moose. When I click on the ‘All classes’ it claims that there are 309 but as far as I can tell none have any superclass or subclasses. Is that to be expected? James

11 years, 2 months

2
3
0 0

Roassal2 - RTLabelled and RTNest

by Leo Perard

Hi, with the new interaction RTLabelled, I have played with it to integrate in my work and I have found a little bug. | view box els | view := RTView new. box := RTBox new element. els := (RTEllipse new color: Color red) elementsOn: (1 to: 30). view add: box; addAll: els. box @ RTDraggable. box @ (RTLabelled new text: 'Container'). RTNest new layout: RTGridLayout; on: box nest: els. view open The label is not at the right place. If you move the box it will move to its place. But if you add the interaction RTLabelled after the nest everything is ok. Thanks -- Leo Perard

11 years, 2 months

2
1
0 0

Syntax hilighter in moose

by Pharo4Stef

The syntax hilighlter in moose does not take advantage of a reallllllly cool feaures of shout Type Po Pox Poin to understand the difference with the default hilighter and we the tango shout color scheme. You will see that Po is ok Pox is red Po is ok because Point is correct Stef

11 years, 2 months

3
7
0 0

Issue 648 in moose-technology: improve overview pyramid

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 648 by cy.delau...(a)gmail.com: improve overview pyramid http://code.google.com/p/moose-technology/issues/detail?id=648 Overview pyramid should use colors so that we can easily read the different results. Maybe also change the color code (green / blue / red for now.)

11 years, 2 months

1
6
0 0

Roassal Tip #3: Labelling any Roassal element

by Alexandre Bergel

A new tip online: https://www.facebook.com/ObjectProfile/photos/a.341189379300999.82969.34054… We kind of like this idea of having Roassal tips posted in this list. I hope you will enjoy them. If this is the case, use the like button :-) If you have some topics you would like to see us talk about, feel free to make suggestions. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

11 years, 2 months

4
4
0 0

Why GTPlayground is not api compatible with Workspace

by pharo4Stef＠free.fr

Hi I do not understand why GTPlayground in Moose replace Workspace and is accessed using Smalltalk tools workspace and does not offer the same interface than a Workspace. This is a bad design because now it forces me to have isKindOf: checks. Really annoying. Or and this is what I will do I will fix the fonts for Pharo and the system will break in Moose, after all I cannot fix everything. Stef

11 years, 2 months

2
4
0 0

How to integrate a roassal viz into a Spec UI

by Johan Fabry

Hi all, I am making a UI using Spec, and I want it to also contain a Roassal visualization. But it is not clear to me how to do that. If I send open to a RTView instance it opens itself in a new window, which is not what I want. What can I do? Thanks in advance! ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

11 years, 2 months

4
3
0 0

scaling roassal visualizations to fit the screen

by Tudor Girba

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"

11 years, 2 months

2
7
0 0

Issue 1054 in moose-technology: VisualWorksParseTreeVisitor and VisualWorksParseTreeMetricCalculator

by moose-technology＠googlecode.com

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

11 years, 2 months

1
2
0 0

Issue 1064 in moose-technology: FMMSEParser>>#'tNAME' should accept underscore character

by moose-technology＠googlecode.com

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

11 years, 2 months

1
3
0 0

Issue 1053 in moose-technology: VerveineJ exception on wrong command line

by moose-technology＠googlecode.com

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

11 years, 2 months

1
1
0 0

Issue 1052 in moose-technology: VerveineJ exception on wrong command line

by moose-technology＠googlecode.com

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

11 years, 2 months

1
2
0 0

Issue 709 in moose-technology: add Moose-Eclipse-Plugin in Moose

by moose-technology＠googlecode.com

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.

11 years, 2 months

1
3
0 0

Re: Issue 421 in moose-technology: Fame PragmaProcessor should accept selective properties

by moose-technology＠googlecode.com

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

11 years, 2 months

1
0
0 0

Re: Issue 156 in moose-technology: The table presentation for Glamour should provide dynamic sorting and column manipulation

by moose-technology＠googlecode.com

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.)

11 years, 2 months

1
1
0 0

Re: Issue 254 in moose-technology: inFusion default initializer export to MSE

by moose-technology＠googlecode.com

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.)

11 years, 2 months

1
2
0 0

Re: Issue 225 in moose-technology: History in Finder Evaluator pane

by moose-technology＠googlecode.com

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

11 years, 2 months

1
0
0 0

Re: Issue 171 in moose-technology: Fame generator should create packages

by moose-technology＠googlecode.com

Updates: Status: WontFix Comment #3 on issue 171 by tu...(a)tudorgirba.com: Fame generator should create packages http://code.google.com/p/moose-technology/issues/detail?id=171 I guess we won't fix this. -- 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

11 years, 2 months

1
0
0 0

roassal2 presentation - zooming actions

by Tudor Girba

Hi, When working with Roassal2 in Glamour, you now get the zoom actions by default. [image: Inline image 1] Doru -- www.tudorgirba.com "Every thing has its own flow"

11 years, 2 months

3
2
0 0

Re: Towards Roassal2

by Alexandre Bergel

> I started to script the visualization in Roassal 2. But I have the following missing: > > - RODynamicEdge (and ROMondrianInteractionBuilder>>dynamicEdgeFromAll: aBlockOrSymbol using: aShape) > - ROArrow Just yesterday I have introduced RTShowEdge, which is a nice replacement of RODynamicEdge. Try the following: -=-=-=-=-=-=-=-=-=-=-=-= | v es | v := RTView new. es := ((RTEllipse new size: 30) + RTLabel) elementsOn: (1 to: 20). v addAll: es. RTCircleLayout on: es. es @ (RTShowEdge new connectTo: [ :value | value - 5 to: value + 5]). v -=-=-=-=-=-=-=-=-=-=-=-= Or: -=-=-=-=-=-=-=-=-=-=-=-= | v es | v := RTView new. es := ((RTEllipse new size: 30) + RTLabel) elementsOn: (1 to: 20). v addAll: es. RTCircleLayout new initialRadius: 150; on: es. es @ (RTShowEdge new connectTo: [ :value | value - 5 to: value + 5]; shape: (RTLine new color: (Color blue alpha: 0.4))). v -=-=-=-=-=-=-=-=-=-=-=-= Here is a screenshot: And if you are in a curvy mood, you can do: -=-=-=-=-=-=-=-=-=-=-=-= | v es | v := RTView new. es := ((RTEllipse new size: 30) + RTLabel) elementsOn: (1 to: 20). v addAll: es. RTCircleLayout new initialRadius: 150; on: es. es @ (RTShowEdge new connectTo: [ :value | value - 5 to: value + 5]; shape: [ :el | RTBezierLine new centerOfObjects: (el model - 5 to: el model +5) inView: v; color: (Color blue alpha: 0.4) ] ). v -=-=-=-=-=-=-=-=-=-=-=-= We are currently working on RTArrow, we will be done by today or tomorrow I think… Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

11 years, 2 months

6
15
0 0

Migration of the Customizable System Complexity view

by Anne Etien

Hi, Today, we migrated the Customizable System Complexity view of the Moose Panel from Roassal to Roassal2. The render is not so beautiful due to the border and the popUp. We hope that the behavior of the view remains the same. Leo, Kevin and Anne.

11 years, 2 months

4
30
0 0

[ANN] Example Browser for Roassal

by Alexandre Bergel

Dear All, We are happy to announce a first draft of the example browser for the Roassal tool suite. Just open “Roassal examples” from the WorldMenu/Tool entry. You can then select some builder examples. We are currently working on more examples. Here are some screenshots: Feedback are appreciated! Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

11 years, 2 months

4
4
0 0

some changes in the white theme

by Tudor Girba

Hi, Based on the recent feedback, one thing that I managed to distill is that people do not see a couple of widgets: - text/input fields - drop downs As a consequence, now I added a thin border around them. I am not particularly satisfied because it looks ugly when we have also splitters, but please let me know if this helps now. Doru -- www.tudorgirba.com "Every thing has its own flow"

11 years, 2 months

3
5
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev