August 2011 - Moose-dev

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!

10 years, 9 months

1
2
0 / 0

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

10 years, 9 months

1
1
0 / 0

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

10 years, 9 months

1
3
0 / 0

Issue 509 in moose-technology: Modularization Quality Metric

by moose-technology＠googlecode.com

Status: New Owner: andreho...(a)gmail.com Labels: Type-Enhancement Priority-Medium Component-Famix New issue 509 by andreho...(a)gmail.com: Modularization Quality Metric http://code.google.com/p/moose-technology/issues/detail?id=509 We implemented the Bunch metrics of coupling and cohesion as quality metrics for existing packages (FAMIXPackage) and namespaces (FAMIXNamespace). Now the idea is to implement the Modularization Quality Metric as a quality metric for existing group of packages (FAMIXPackageGroup) and namespaces (FAMIXNamespaceGroup). Pointer to the papers that propose the metrics: Using Automatic Clustering to Produce High-Level System Organizations of Source Code (http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=693283) Bunch: A Clustering Tool for the Recovery and Maintenance of Software System Structures (http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=792498)

10 years, 9 months

1
2
0 / 0

Issue 644 in moose-technology: A fly by help to show each time the source code of an entity

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 644 by cy.delau...(a)gmail.com: A fly by help to show each time the source code of an entity http://code.google.com/p/moose-technology/issues/detail?id=644 Maybe it would be interesting when navigating in moose, to always have a fly by help that show the source code of an element

10 years, 10 months

1
2
0 / 0

Issue 582 in moose-technology: Watcher support in Glamour

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Glamour New issue 582 by tudor.gi...(a)gmail.com: Watcher support in Glamour http://code.google.com/p/moose-technology/issues/detail?id=582 Like we now have a statusbar, we should also have a detailed preview shown in a floating Watcher window. The behavior would be similar to Quick Look on Mac.

10 years, 10 months

1
3
0 / 0

Re: Issue 602 in moose-technology: Hapao should provide a legend in every window

by moose-technology＠googlecode.com

Updates: Summary: Hapao should provide a legend in every window Comment #3 on issue 602 by tudor.gi...(a)gmail.com: Hapao should provide a legend in every window http://code.google.com/p/moose-technology/issues/detail?id=602 Then let's name the issue for what it should do.

11 years

1
3
0 / 0

Issue 489 in moose-technology: Glamour: action list without the dropdown

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: tudor.girba Labels: Type-Defect Priority-Medium New issue 489 by jfabry: Glamour: action list without the dropdown http://code.google.com/p/moose-technology/issues/detail?id=489 I have a Glamour pane that is an actionList where I do 5 populate:on:entitled:with: so that the pane has 5 buttons. Now what happens is that the pane also has a dropdown menu, with the same actions as the buttons. This menu should not be there according to Doru ...

11 years

1
2
0 / 0

Re: Issue 240 in moose-technology: Smalltalk importer scalability

by moose-technology＠googlecode.com

Comment #2 on issue 240 by tudor.gi...(a)gmail.com: Smalltalk importer scalability http://code.google.com/p/moose-technology/issues/detail?id=240 Anyone interested in picking this up?

11 years

1
1
0 / 0

Re: Issue 191 in moose-technology: Do not execute unnecessary transmissions

by moose-technology＠googlecode.com

Updates: Labels: -Milestone-4.2 Comment #5 on issue 191 by tudor.gi...(a)gmail.com: Do not execute unnecessary transmissions http://code.google.com/p/moose-technology/issues/detail?id=191 (No comment was entered for this change.)

11 years

1
1
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev August 2011