Moose-dev November 2013

moose-dev@list.inf.unibe.ch

31 participants
160 discussions

Issue 648 in moose-technology: improve overview pyramid
by moose-technology＠googlecode.com 22 Apr '14

22 Apr '14

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

1 6

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

Issue 1016 in moose-technology: PNG Export is not clean (example EyeSee charts)
by moose-technology＠googlecode.com 20 Mar '14

20 Mar '14

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1016 by usman.bh...(a)gmail.com: PNG Export is not clean (example EyeSee charts) http://code.google.com/p/moose-technology/issues/detail?id=1016 See the attached screenshot, it seems that the export is not clean. The diagram export is correct but the labels seem to be superimposed. The problem might be coming from Pharo but I dont know how to reproduce it in there. Attachments: EyeSee-2013-11-25-1506.png 5.9 KB -- 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 987 in moose-technology: Roassal does not display edges when the source is not visible
by moose-technology＠googlecode.com 02 Mar '14

02 Mar '14

Status: New Owner: ---- CC: alexandr...(a)gmail.com Labels: Type-Defect Priority-Critical Component-Roassal Milestone-4.9 New issue 987 by tu...(a)tudorgirba.com: Roassal does not display edges when the source is not visible http://code.google.com/p/moose-technology/issues/detail?id=987 Try this: view nodes: { 1 . 2 }. view edgeFromAssociation: 2->1. view horizontalLineLayout horizontalGap: 1000. I think it is easy to fix, but at the same time it is really annoying, so I mark it as critical :) -- 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 4

minimap in Glamour-Roassal
by Usman Bhatti 19 Feb '14

19 Feb '14

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

6 13

Issue 942 in moose-technology: Fame-ImportExport - XML Export - transformation of \n and \t not working.
by moose-technology＠googlecode.com 14 Feb '14

14 Feb '14

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

1 7

Issue 1018 in moose-technology: Message not understood Exception when asking for senders of some methods
by moose-technology＠googlecode.com 14 Feb '14

14 Feb '14

Status: New Owner: ---- Labels: Type-Defect Priority-Critical Milestone-5.0 New issue 1018 by anne.et...(a)gmail.com: Message not understood Exception when asking for senders of some methods http://code.google.com/p/moose-technology/issues/detail?id=1018 Describe the problem: what do you get? what do you expect? A message not understood exception occurs when asking for senders instead the opening of a window with the list of senders. How to reproduce the problem: step by step if necessary Finding the senders of #+ works. But finding the senders of #ifTrue: or #new or... does not work. Additional information: platform, context which may impact the problem The error comes from GRPackage that does not implement #includesSelector:OfClassName:. Only Magritte and Grease use GRPackage. Please fill in the labels with the following information: * Type-Defect * 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 6

slice for issue 989
by Anne Etien 14 Feb '14

14 Feb '14

Hello, We create slice to manage exception in the MoosePanel request form (each beginWith: 'C'). We modified Glamour to correctly manage the exception and not launch the debugger when the message sent is not supported. Doru, can you please have a look and integrate our change? Thanks in advance, Rafael, Gustavo, Guillaume and Anne.

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev November 2013