Moose-dev December 2013

moose-dev@list.inf.unibe.ch

36 participants
148 discussions

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

Issue 1024 in moose-technology: EyeSee Editor crashes by default
by moose-technology＠googlecode.com 27 Feb '14

27 Feb '14

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-EyeSee Milestone-5.0 New issue 1024 by tu...(a)tudorgirba.com: EyeSee Editor crashes by default http://code.google.com/p/moose-technology/issues/detail?id=1024 Just open an EyeSee Editor and press Cmd+s. The diagram is not initialized. -- 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

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

Issue 1022 in moose-technology: OSProcess should be loaded from the Pharo 3 repo
by moose-technology＠googlecode.com 14 Feb '14

14 Feb '14

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Milestone-5.0 New issue 1022 by tu...(a)tudorgirba.com: OSProcess should be loaded from the Pharo 3 repo http://code.google.com/p/moose-technology/issues/detail?id=1022 The ConfigurationOfMoose should be modified to make it load from the repository of Pharo 3. -- 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

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

Issue 1036 in moose-technology: Ctrl + S and Alt + S haven't the same behaviour
by moose-technology＠googlecode.com 05 Feb '14

05 Feb '14

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1036 by v.blonde...(a)gmail.com: Ctrl + S and Alt + S haven't the same behaviour http://code.google.com/p/moose-technology/issues/detail?id=1036 Describe the problem: what do you get? what do you expect? To save the modified source code in the debugger under Pharo3.0, we can make Ctrl + S or Alt + S. But with the latest version of Moose5.0. Alt + S save the source and move the stack to the saved method. Ctrl + S only save the source. How to reproduce the problem: step by step if necessary Open a debugger, select an other method in the stack trace, modify it. Try to save with Ctrl + S and do it again with Alt + S. Additional information: platform, context which may impact the problem Windows 7 x64 and Linux Ubuntu x64 Please fill in the labels with the following information: * Type-Defect * Component-GTDebugger * Milestone-5.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 9

Re: Issue 113 in moose-technology: Roassal should support lazy edges when used through the Mondrian API
by moose-technology＠googlecode.com 27 Jan '14

27 Jan '14

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.

1 6

Activity Diagram
by Serge Stinckwich 23 Jan '14

23 Jan '14

Dear all, with a colleague from Savoie University, we are looking for some Smalltalk code in order to model, execute and animate Activity Diagram. Any existing works ? Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

5 9

← Newer
1
2
3
4
5
6
7
...
15
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 December 2013