Moose-dev April 2013

moose-dev@list.inf.unibe.ch

34 participants
198 discussions

Issue 837 in moose-technology: ROCircle not constrained to equal dimensions
by moose-technology＠googlecode.com 14 Nov '13

14 Nov '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 837 by google....(a)ben.coman.com.au: ROCircle not constrained to equal dimensions http://code.google.com/p/moose-technology/issues/detail?id=837 Currently ROCircle acts more like a hypothetical ROEllipse, since it is not constrained to force dimensions to be equal. The following might be a worthwhile test case... --- | rawView element1 element2 | element1 := (ROElement on: '1' ). element1 + ROCircle. element1 width: 200; height: 100. self assert: ( element1 height = 200). element2 := (ROElement on: '2' ). element2 width: 200; height: 100. element2 + ROCircle. "Swapped order with above line" self assert: ( element2 height = 200). "Should be true. Currently not." "optional - following not part of test - just visual feedback" rawView := ROView new. rawView add: element1. rawView add: element2. ROVerticalLineLayout on: rawView elements. rawView open. --- The first assert can be made to work by adding the following... ---- ROCircle>>extent: anExtentPoint | max | max := anExtentPoint x max: anExtentPoint y. extent := max @ max. next extent: anExtentPoint --- The second assert, I'm not sure yet about resolving the fail.

1 3

Re: Issue 435 in moose-technology: Using RoelTyper for a better precision of method invocation
by moose-technology＠googlecode.com 11 Nov '13

11 Nov '13

Updates: Labels: Component-SmalltalkImporter Comment #4 on issue 435 by tudor.gi...(a)gmail.com: Using RoelTyper for a better precision of method invocation http://code.google.com/p/moose-technology/issues/detail?id=435 It seems that RoelTyper does not work for all classes. Try this code for getting the classes that raise an error: classes := Dictionary new. Object withAllSubclassesDo: [:each | [(TypeCollector typeInstvarsOfClass: each )] on: Error do: [:error | classes at: each put: error ]]. classes inspect

1 5

Issue 516 in moose-technology: System Complexity displays more than the classes in the group
by moose-technology＠googlecode.com 11 Nov '13

11 Nov '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 516 by tudor.gi...(a)gmail.com: System Complexity displays more than the classes in the group http://code.google.com/p/moose-technology/issues/detail?id=516 Currently, the algorithm to identify the hierarchies does not limit the result to the current class group, but it takes all the subclasses of the superclass. This means that if you have a group with Object inside, you will end up with a system complexity with all classes.

1 4

Issue 526 in moose-technology: Add explicit Interface in Famix
by moose-technology＠googlecode.com 11 Nov '13

11 Nov '13

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Enhancement Priority-Medium Milestone-4.3 New issue 526 by tudor.gi...(a)gmail.com: Add explicit Interface in Famix http://code.google.com/p/moose-technology/issues/detail?id=526 We should have a FAMIXInterface.

1 6

Loading Hapax
by Hernán Morales Durand 06 Nov '13

06 Nov '13

Hello, I know that Hapax possibly isn't fully ported to Pharo, but running the Hapax tests causes my Moose 4.5 image to hang (I've loaded everything in the SqS Hapax repository). What image and package loading order should one use to load Hapax? I'm interested in the information retrieval part for natural language analysis, could that part be repackaged in its own package? Cheers, Hernán

6 12

Issue 914 in moose-technology: withCenteredText not centering text correctly
by moose-technology＠googlecode.com 28 Oct '13

28 Oct '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 914 by cunningh...(a)gmail.com: withCenteredText not centering text correctly http://code.google.com/p/moose-technology/issues/detail?id=914 When I ask for centeredText, I would expect it to be centered horizontally in the area that it is displaying in. Instead, it appears to be bumped up vertically above the location where it should be. If you add the following (missing?) method: ROMondrianExample>>centeredText " self new centeredText " | view | view := ROMondrianViewBuilder new. self centeredTextOn: view. view open and then run ROMondrianExample new centeredText, you will see the issue. How to reproduce the problem: step by step if necessary This is from the latest (2013-02-14) Moose Suite 4.7 from the MooseTechnology.org download page, on Windows 7 os. Labels: Type-Defect Component-Roassal -- 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 904 in moose-technology: Roassal dragging subtrees (feature contribution)
by moose-technology＠googlecode.com 21 Oct '13

21 Oct '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 904 by benjamin...(a)gmail.com: Roassal dragging subtrees (feature contribution) http://code.google.com/p/moose-technology/issues/detail?id=904 With a tree layout, when dragging an element I needed to drag all the children at the same time. I knocked up a solution sufficient to my needs in about 40 minutes - see attached changeset. I might be a nice general feature to add to Roassal but its a bit rough. It will likely need some critical love to polish it before integration. Later it might be made to work with ROSelection and multi-selected elements - but that is out of my scope for the moment. Attachments: RODraggableWithOthers.2.cs 1.3 KB

3 3

Issue 884 in moose-technology: The Roassal presentation should react to custom ports
by moose-technology＠googlecode.com 21 Oct '13

21 Oct '13

Status: New Owner: tu...(a)tudorgirba.com CC: chisvasi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Glamour New issue 884 by tu...(a)tudorgirba.com: The Roassal presentation should react to custom ports http://code.google.com/p/moose-technology/issues/detail?id=884 The current implementation of the Roassal presentation relies only on the original entity. However, given that Roassal can handle various animations, we would benefit from an extra ability of the presentation to react to other ports. For example, the list presentation reacts to #selection. Similarly, Roassal should be able to react to it or others as well. Only, given that Roassal is generic, the reaction should be customisable, too. Perhaps something like this: a roassal painting: [:view :entity | ... ] on: #customPort do: [ :view :customValue | ... ]

1 13

Hapax/CodeFu changes and example script
by Hernán Morales Durand 03 Oct '13

03 Oct '13

Hi guys, For those working in information retrieval, for example for doing td-idf ranking, you can find adapted packages: "Hapax" and "CodeFu" in the BioSmalltalk repository http://ss3.gemstone.com/ss/BioSmalltalk.html . I have translated some VW specific code to Pharo 1.4 (under Windows requires the ProcessWrapper package) and adapted some Hapax methods to work with corpus in different languages. This is an example script for a corpus in Spanish: | corpus tdm documents | corpus := HXSpanishCorpus new. documents := 'el río Danubio pasa por Viena, su color es azul el caudal de un río asciende en Invierno el río Rhin y el río Danubio tienen mucho caudal si un río es navegable, es porque tiene mucho caudal'. documents lines doWithIndex: [: doc : index | corpus addDocument: index asString with: (Terms new addString: doc using: CamelcaseScanner; yourself)]. corpus removeStopwords. corpus stemAll. tdm := TermDocumentMatrix on: corpus. Feel free to integrate to any repository. If you want to add a language just see methods with selectors including "spanish". Cheers, Hernán

5 8

Issue 714 in moose-technology: VerveineJ does not produce correct values for classes in annotation instances
by moose-technology＠googlecode.com 23 Aug '13

23 Aug '13

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-High Component-VerveineJ New issue 714 by tudor.gi...(a)gmail.com: VerveineJ does not produce correct values for classes in annotation instances http://code.google.com/p/moose-technology/issues/detail?id=714 Take a look at the example below: @XmlElement(name = "Time", required = true, type = String.class) protected Date time; The value of the third attribute of the annotation instance is the actual source code of the String class. Instead, it should be just the string 'String.class'. Ideally, we would get an actual reference, but the string would do for now.

2 11

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