Moose-dev September 2013

moose-dev@list.inf.unibe.ch

30 participants
148 discussions

Issue 528 in moose-technology: Remove Category Importer

by moose-technology＠googlecode.com

Status: Accepted Owner: ---- Labels: Type-Defect Priority-Medium Milestone-4.3 Component-Famix Component-SmalltalkImporter New issue 528 by jannik.l...(a)gmail.com: Remove Category Importer http://code.google.com/p/moose-technology/issues/detail?id=528 With RPackage, Category importer is useless, We should remove it. They are some referecnes in examples in DSM.

10 years, 6 months

Re: Issue 228 in moose-technology: Nested browsers do not take "when", or "display" into account

by moose-technology＠googlecode.com

Updates: Labels: -Milestone-4.2 Comment #4 on issue 228 by tudor.gi...(a)gmail.com: Nested browsers do not take "when", or "display" into account http://code.google.com/p/moose-technology/issues/detail?id=228 (No comment was entered for this change.)

10 years, 10 months

Issue 757 in moose-technology: Smalltalk completion appears at absolute coordinates, instead of relative ones in Finder

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Glamour New issue 757 by tudor.gi...(a)gmail.com: Smalltalk completion appears at absolute coordinates, instead of relative ones in Finder http://code.google.com/p/moose-technology/issues/detail?id=757 Try this: GLMFinder new show: [:a | a smalltalkCode ]; openOn: ''. and then type "1 as". You will see that the completion appears in the top right of the world, instead of the top right of the text pane. This only happens in the finder, and it is likely due to some problems of transforming coordinates.

10 years, 10 months

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

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, 1 month

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, 1 month

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, 1 month

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

11 years, 3 months

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

11 years, 3 months

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.

11 years, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev September 2013