August 2013 - Moose-dev

by Stephan Eggermont

Hi, Today I looked at getting Glamour and Torch working in Pharo 3.0 - ConfigurationOfMondrian refers to a stable version of ProfStef, which isn't defined for 3.0 - GLMUITheme has UThemeWatery2 as ancestor, which is removed. UIThemeWatery works fine - RectangleMorph behavior was moved to BorderedMorph, so GLMPaneScroller needs a different ancestor - old version of Grease-Pharo-Core is loaded, using BlockContext (refering to squeaksource instead of smalltalkhub) With those changes, most browsers work. GLMBasicExamples open works, most examples work. Action List -> Inspect has a problem. (ConfigurationOfTorch project version: '1.4') load misses AST-Semantic should refer to smalltalkhub refers to an older version of ConfigurationOfGlamour AST changes seem to be substantial. Changes needed in TCParser? Stephan

9 years, 6 months

4
3
0 / 0

Loading Hapax

by Hernán Morales Durand

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

9 years, 6 months

6
12
0 / 0

Issue 914 in moose-technology: withCenteredText not centering text correctly

by moose-technology＠googlecode.com

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

9 years, 7 months

1
1
0 / 0

Issue 904 in moose-technology: Roassal dragging subtrees (feature contribution)

by moose-technology＠googlecode.com

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

9 years, 7 months

3
3
0 / 0

Issue 938 in moose-technology: RadialTreeLayout should translate the graph

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Roassal New issue 938 by tu...(a)tudorgirba.com: RadialTreeLayout should translate the graph http://code.google.com/p/moose-technology/issues/detail?id=938 Try this: view nodes: (Collection withAllSubclasses). view edgesFrom: #superclass. view radialTreeLayout. The center of the graph is placed at 0@0, and this is annoying because you do not see half of the graph. The layout should translate the graph to make it start at 0@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, 7 months

1
10
0 / 0

Issue 884 in moose-technology: The Roassal presentation should react to custom ports

by moose-technology＠googlecode.com

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

9 years, 7 months

1
13
0 / 0

Hapax/CodeFu changes and example script

by Hernán Morales Durand

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

9 years, 8 months

5
8
0 / 0

Issue 950 in moose-technology: Freeze 4.8

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Maintainability Milestone-4.8 New issue 950 by tu...(a)tudorgirba.com: Freeze 4.8 http://code.google.com/p/moose-technology/issues/detail?id=950 We need to freeze 4.8 for ConfigurationOfMoose and the configurations of all other Moose projects. We should extend the mechanism used for 4.7. -- 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, 8 months

1
2
0 / 0

white theme

by Alexandre Bergel

Hi! Just to say that I like the white theme very much :-) Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 8 months

8
13
0 / 0

Re: Change in FAME

by Stephan Eggermont

Nicolas wrote: >did you run the tests before? >I believe I saw some of them fail in the past ... ? Uhm, we broke the build from 981 to 984, but I'm not aware of earlier problems. Stephan

9 years, 8 months

3
2
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev August 2013