July 2013 - Moose-dev

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

9 years, 7 months

1
6
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.

9 years, 7 months

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

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

9 years, 7 months

1
2
0 / 0

minimap in Glamour-Roassal

by Usman Bhatti

Hello, I am trying to create a roassal minimap in a glamour browser. But I do not get a minimap when pressing m key. It might be something to do with how keystrokes are interpreted in Glamour. can you have a look? Here's a simple browser with a roassal visualization (adapted from one of ben's mail on moose-dev). | browser viewHack | browser := GLMTabulator new. browser column: #list; column: #drawing. browser transmit to: #list; andShow: [ :a | a list ]. browser transmit to: #drawing; andShow: [ :a | a roassal painting: [ :moview :collection | moview raw @ (ROMiniMap new targetView: moview stack). collection do: [ :x | moview view add: (ROElement spriteOn: x) + ROLabel + ROBox white ]. ROVerticalLineLayout on: moview view elements. viewHack := moview view. ] ]. browser transmit from: #list port:#selection; to: #drawing; transformed: [ :x | | foundElements | viewHack elements do: [ :el | ROUnhighlightElement on: el ]. targetElement := viewHack elements at: x. ROFocusView on: targetElement. ROHighlightElement on: targetElement color: Color red. viewHack signalUpdate ]. browser openOn: #(1 2 3 4 5 6).

9 years, 9 months

6
13
0 / 0

Issue 942 in moose-technology: Fame-ImportExport - XML Export - transformation of \n and \t not working.

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 942 by v.blonde...(a)gmail.com: Fame-ImportExport - XML Export - transformation of \n and \t not working. http://code.google.com/p/moose-technology/issues/detail?id=942 In the class FMXMLPrinter of the Fame-ImportExport package, the method 'primitive:' doesn't remplace the Character cr by \n and Character tab by \t as expected in the source code. Indeed the affectation of the local block variable by this line of code : char = $n doesn't work. The result expected is : '<?xml version="1.0"?> <Document> <Element name="FAMIX.Comment" id="1"> <Attribute name="content"> <String value="This is a test\"\n\t"/> </Attribute> </Element> </Document>' What we have actually : '<?xml version="1.0"?> <Document> <Element name="FAMIX.Comment" id="1"> <Attribute name="content"> <String value="This is a test\"\ \ "/> </Attribute> </Element> </Document>' Platform : Win7, Pharo 2.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

9 years, 9 months

1
7
0 / 0

Re: Issue 113 in moose-technology: Roassal should support lazy edges when used through the Mondrian API

by moose-technology＠googlecode.com

Updates: Summary: Roassal should support lazy edges when used through the Mondrian API Status: Labels: -Component-Mondrian Component-Roassal Comment #10 on issue 113 by tu...(a)tudorgirba.com: Roassal should support lazy edges when used through the Mondrian API http://code.google.com/p/moose-technology/issues/detail?id=113 No, it does not. But, it should. The idea is that the following Mondrian script should work: view edge: #edge from: 1 to: 2. view node: 1. view node: 2. For this, the edge creation should be evaluated only after all nodes are created. I changed the entry title and labels.

9 years, 10 months

1
6
0 / 0

famix generator for .NET assemblies

by Thomas Haug

Hi everybody, I have implemented a Famix-Generator which analyses .NET assemblies and produces mse files for CodeCity as well as the MOOSE platform. If you want to give it a try, you can download it from my site (german, I am sorry - I will change that in near future): http://www.sharpmetrics.net/index.php/famix-generator The generator creates famix artifacts for namespaces, types (classes, interfaces, enums und structs), methods, methods calls and local variables. the tool is not complete (missing features, bugs?), I will enhance it during the next weeks or months.. ;-) (BTW you need a .NET 4.0 installed on your machine. It does not run on the Mono plattform, right now.) Cheers Thomas

9 years, 10 months

5
12
0 / 0

Issue 690 in moose-technology: Change the font size of labels in a chart

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-EyeSee New issue 690 by andreho...(a)gmail.com: Change the font size of labels in a chart http://code.google.com/p/moose-technology/issues/detail?id=690 Change the font size of labels in a chart using #defaultFontSize: is not working.

9 years, 11 months

1
2
0 / 0

Issue 900 in moose-technology: Glamour-Roassal should be able to work with raw ROView not just ROMondrianBuilder

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 900 by benjamin...(a)gmail.com: Glamour-Roassal should be able to work with raw ROView not just ROMondrianBuilder http://code.google.com/p/moose-technology/issues/detail?id=900 Hopefully, I've cracked this. In response to my own query: "Could something like a GLMMorphicRoassalRawRenderer be added to the Glamour-Roassal interface? - which would pass an unencumbered ROView to the paintingBlock. It is not really a Glamour-Roassal interface at the moment, more of a Glamour-Mondrian interface." With the attached slice you can now go... browser transmit to: #graphic andShow: [ :a | a roassal newView: [ ROView new @ RODraggable ] ; painting: [:view :input | view add: ROElement new] ]. After loading you can first try the new & old tests in 'Glamour-Tests-Roassal' then try 'GLMRawRoassalExamplesBrowser open' I surprised myself that I got this far. A few times I hit a brick wall and was going to submit a half done proof-of-concept, but then just kept digging. Apart from hopefully getting integrated, some critical feedback would appreciated. A few points for review... 1. I had considered using #viewPrototype: with an instance to copy, but then I wasn't sure how deep I should copy it to produce a new view. So using a block with newView: seemed the safer path (and it also feels like it opens up some interesting possibilities, even if I can't think what they are at the moment) 2. I noticed that GLMRoassalPresentation>>renderOn: had a flag 'This should be the responsibility of the view'. This method was one that I previously copied and modified for GLMRoassalRawPresentation in my "Interactive Roassal" experiment. There I removed the calls to #applyLayout and #populateMenuOn since these were MNU for ROView (which had replaced ROMondrianViewBuilder). This time I pushed these two calls into ROMondrianViewBuilder>>preOpen, where ROView>>preOpen is left empty. I'm note sure I'm happy with #preOpen as a name but it was the best I could come up with, since I also refactored ROMondrianViewBuilder>>open to use it. 3. GLMMorphicRoassalRenderer>>render: had hardcoded reference to #stack with "ROMorph on: view stack" so I pushed the required difference into ROMondrianBuilder>>newMorph and ROView>>newMorph. 4. GLMMorphicRoassalRenderer>>actOnPresentationUpdate had hardcoded use of #stack in "setView: aView stack" so I pushed that into ROMondrianViewBuilder>>onMorph: and ROView>>onMorph: 5. GLMMorphicRoassalRenderer>>actOnPresentationUpdate had hardcoded ROMondrianViewBuilder so I modified this to use the block passed to GLMRoassalPresentation>>newView: . 6. I copied GLMRoassalMorphicTest to GLMRawRoassalMorphicTest with required modifications. 7. I copied GLMRoassalExamplesBrowser to GLMRawRoassalExamplesBrowser with required modifications.

9 years, 11 months

5
18
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev July 2013