Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Start a nNew thread

Jenkins build is still unstable: moose-latest-dev #960

by admin＠moosetechnology.org

See <http://hudson.moosetechnology.org/job/moose-latest-dev/960/>

13 years

displaced edges in the new version of Roassal

by Usman Bhatti

Hello, I am having trouble with the new version of Roassal (downloaded with latest moose version today), the edges are abnormally displaced (c.f: attached figure). Here is the script to generate the visu. |mainNode view title childNodes ab mainTitle| view := ROView new. mainNode := (ROElement spriteOn: 'A Test Node') + ROBorder. mainTitle := (ROLabelElement on: 'A Test Node') textColor: Color gray. ab := Array with: 'Moose' with: 'Mondrian' with: 'Glamour'. childNodes := OrderedCollection new. ab do: [:each | element := ((ROElement spriteOn: each) + ROBorder). title := (ROLabelElement on: each) textColor: Color red. box := ROBox new color: Color transparent. element addInteraction: RODraggable. ('Mondrian' matches: each) ifTrue: [box color: Color lightBlue]. ('Glamour' matches: each) ifTrue: [box color: Color blue]. element add: title; addShape: box. childNodes add: element. ]. view add: (ROEdge arrowedLineFrom: childNodes first to: childNodes second) + ROLine blue. view add: (ROEdge arrowedLineFrom: childNodes first to: childNodes third) + ROLine blue. view add: (ROEdge arrowedLineFrom: childNodes second to: childNodes third) + ROLine blue. mainNode addAll: (ROGridLayout on: childNodes). view addAll: (ROVerticalLineLayout on: (Array with: mainTitle with: mainNode)). view open Should I open a bug entry? thanx Usman [image: Inline image 1]

13 years

filterOn: in glamour

by Usman Bhatti

Hello all, I am trying to understand the functionality of filterOn: method in GLMListingPresentation. I am not able trigger the block in glamour examples by typing the search criteria in the provided search box (c.f: multipleFinderWithFilter example). How do we trigger the filterOn: block so that the matching entities appear in the next pane of the example? What I am trying to achieve is to reduce the list of items in a tree with the criterion provided in the search box. Currently with the searchOn: block, I can select the matching entities in the tree, my idea is to remove the entities from the tree which do not fulfill the selection criterion. tx Usman

13 years

graph of object references

by Tudor Girba

Hi, I would need to debug memory leaks (maybe induced by announcements), and for that I am thinking to use a graph of object references. I guess this would be easily possible with Fuel. If I have an object, how would I go about doing this? Cheers, Doru -- www.tudorgirba.com "Don't give to get. Just give."

13 years

AbstractDistributionMap >> defaultTitleFormattingBlock looks wrong

by Mariano Martinez Peck

AbstractDistributionMap >> defaultTitleFormattingBlock ^ [ :each | | t | t := each. (t beginsWith: 'Citezen-') ifTrue: [ t := t copyReplaceAll: 'Citezen-' with: 'C' ]. (t beginsWith: 'Seaside-') ifTrue: [ t := t copyReplaceAll: 'Seaside-' with: 'S' ]. t := t copyReplaceAll: 'Tests-' with: 'T-'. "t := (Kontract reduce: t upTo: 10)." t ] On the one hand, it hardcodes stuff like Citizen or Seaside. But what is worse is that that Kontract does not exist... Cheers, -- Mariano http://marianopeck.wordpress.com

13 years, 1 month

New release of FuelMooseExtension

by Mariano Martinez Peck

Hi Doru. I have updated FuelMooseExtension to work with the latest stable version of Fuel 1.8. I think this is worth it because: 1) Right now you are using an old version of Fuel (1.6) which is like an year ago. The older it is the more difficult it will be in the future to update. 2) If you don't take into account the time to compute attributes we can have improvement up to 30% in export time. 3) Fuel 1.8 is integrated by default in Pharo 2.0 now, meaning that you will have problems when moving Moose to Pharo 2.0 (because you would need 1.6). Of course the bad news is that if you have already exported files you won't be able to import them with this new version. If you agree, let me know. I will create a new version 1.5 in ConfigurationOfFuelMooseExtension but I don't know how the Moose image is built (it seems it is not using ConfigurationOfFuel). Cheers -- Mariano http://marianopeck.wordpress.com

13 years, 1 month

Issue 501 in moose-technology: Cache independence

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 501 by alexandr...(a)gmail.com: Cache independence http://code.google.com/p/moose-technology/issues/detail?id=501 The core of Mondrian is not independent of the cache implementation. The logic of Mondrian rely on the cache to implement its semantics. This is obviously wrong. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= bounds "Answer the bounds of the receiver." "the bounds is has an absolute origin" "Note that the bounds computed above, may have (and it is likely to) a different origin. The reason is that the layout is in charge to position the nodes properly" | basicBounds | boundsCache ifNotNil: [ ^ boundsCache ]. "We check if the shape if present" self shapeBoundsAt: self shape ifPresent: [ :b | ^ boundsCache := b ]. basicBounds := self shape computeBoundsFor: self. self shapeBoundsAt: self shape put: basicBounds. ^ boundsCache := basicBounds -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= translateAbsoluteCacheBy: aPoint absoluteBoundsCache ifNil: [ ^ self ]. absoluteBoundsCache := absoluteBoundsCache translateBy: aPoint -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Thanks to Santiago Vidal for pointing this out!

13 years, 1 month

Issue 503 in moose-technology: Abstract classes and Hapao

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: vhane...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Spy New issue 503 by alexandr...(a)gmail.com: Abstract classes and Hapao http://code.google.com/p/moose-technology/issues/detail?id=503 Gaëtan le Brun suggested to remove abstract classes before running the test in Hapao. This makes sense

13 years, 1 month

Issue 794 in moose-technology: More robust dynamicActions in MooseFinder

by moose-technology＠googlecode.com

Status: Accepted Owner: ---- Labels: Type-Defect Priority-Medium New issue 794 by usman.bh...(a)gmail.com: More robust dynamicActions in MooseFinder http://code.google.com/p/moose-technology/issues/detail?id=794 Doru When we clicked (to bring the menu) in Moose Finder we got list entity mooseInterestingEntity = to nil. So for now we patched the method to [ :list | list entity mooseInterestingEntity ifNotNil: [:entity| entity mooseFinderActions ]]. buildBrowser browser := GLMFinder new. browser title: [:each | 'Moose Finder on ', each mooseInterestingEntity mooseDisplayString]. browser show: [ :a | a title: [ :each | (each mooseInterestingEntity mooseDisplayString contractTo: 30), ' (', each mooseInterestingEntity class name, ')' ]; dynamicActions: [ :list | list entity mooseInterestingEntity ifNotNil: [:entity| entity mooseFinderActions ]]. a dynamic display: [:each | | dynamic | dynamic := GLMCompositePresentation new. each mooseInterestingEntity mooseFinderPresentationsIn: dynamic. dynamic ]. a updateOn: MooseEntityAdded from: [:each | each isNil ifFalse: [each announcer] ifTrue: [nil] ]. a updateOn: MooseEntityRemoved from: [:each | each isNil ifFalse: [each announcer] ifTrue: [nil] ]. a updateOn: MooseEntityRenamed from: [:each | each isNil ifFalse: [each announcer] ifTrue: [nil] ]]. ^ browser

13 years, 1 month

Issue 601 in moose-technology: Covered methods and tests

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Hapao New issue 601 by alexandr...(a)gmail.com: Covered methods and tests http://code.google.com/p/moose-technology/issues/detail?id=601 It would be good to see what are the tests that _indirectly_ tests a methods. Thanks Laurent & Patrick

13 years, 1 month

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev