Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

zOrder: roassal vs mondrian :)
by Tudor Girba 04 Dec '12

04 Dec '12

Hi, I am coming back to the issue of zOrder. Here is a little example: view shape label text: #yourself. view nodes: (1 to: 20). view edges: (1 to: 20) from: [:x | x // 2] to: 1. view edges: (1 to: 20) from: [:x | x // 3] to: 2. view edges: (1 to: 20) from: [:x | x // 5] to: #yourself. view edges: (1 to: 20) from: [:x | x // 7] to: #yourself. view dominanceTreeLayout Open this one is Mondrian and then in the Roassal Easel (see attached screenshots). Then, try to select 1. In Roassal, you cannot select 1 because of the edges that go on top of it. What is more, you also can barely see it. This situation will always appear in graphs with edges that cross the nodes. Given that at least the MondrianViewBuilder should be about mapping domain models onto graphs, having a sensible zOrder, at least in the MondrianViewBuilder is important. Doru -- www.tudorgirba.com "Sometimes the best solution is not the best solution."

2 1

Issue 886 in moose-technology: GLMMorphicSpotterTest>>testCreation is not automatic
by moose-technology＠googlecode.com 04 Dec '12

04 Dec '12

Status: Started Owner: damien.c...(a)gmail.com CC: tudor.gi...(a)gmail.com, chisvasi...(a)gmail.com Labels: Type-Defect Priority-Medium Platform-Pharo Component-Glamour New issue 886 by damien.c...(a)gmail.com: GLMMorphicSpotterTest>>testCreation is not automatic http://code.google.com/p/moose-technology/issues/detail?id=886 This method opens a tool and requires user intervention. This blocks test runners and continuous integration.

1 4

Issue 887 in moose-technology: <MSEProperty: ...> should replace <property: ... > pragmas
by moose-technology＠googlecode.com 04 Dec '12

04 Dec '12

Status: New Owner: ---- Labels: Type-Engineering Priority-Medium Milestone-4.7 Maintainability New issue 887 by tu...(a)tudorgirba.com: <MSEProperty: ...> should replace <property: ... > pragmas http://code.google.com/p/moose-technology/issues/detail?id=887 Here is the list of violations: #'Smalltalk::FAMIXClassGroup.abstractness()' #'Smalltalk::FAMIXNamespace.bunchCohesion()' #'Smalltalk::FAMIXPackage.martinCohesion()' #'Smalltalk::FAMIXNamespace.martinCohesion()' #'Smalltalk::FAMIXPackage.bunchCohesion()' #'Smalltalk::FAMIXNamespace.efferentCoupling()' #'Smalltalk::FAMIXNamespace.afferentCoupling()' #'Smalltalk::FAMIXClassGroup.afferentCoupling()'

1 2

Jenkins build became unstable: moose-latest-dev #1219
by admin＠moosetechnology.org 04 Dec '12

04 Dec '12

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

1 3

Issue 867 in moose-technology: Start rule is missing in the PPAllParsersBrowser
by moose-technology＠googlecode.com 03 Dec '12

03 Dec '12

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 867 by kurs....(a)gmail.com: Start rule is missing in the PPAllParsersBrowser http://code.google.com/p/moose-technology/issues/detail?id=867 When you select e.g. PPArithmeticParser in PPAllParsersBrowser, you can test 'start' rule by defining 'Sample' and pressing Parse button. When you select some rule (e.g. number), you cannot test 'start' again. You have to select another parser and re-select PPArithmeticParser.

1 5

talks and other media
by Tudor Girba 03 Dec '12

03 Dec '12

Hi, If you are giving a talk about Moose or related projects, it would be great to announce it officially on the Moose blog. For example, here are the latest two: http://www.moosetechnology.org/news/moose-talk-at-jug-bern-2012 http://www.moosetechnology.org/news/moose-talk-at-xpdays-benelux-2012 Also, if you have a video, demo, blog post or other pointers about Moose, it would be great to get these on the Moose blog as well. Cheers, Doru -- www.tudorgirba.com "Every now and then stop and ask yourself if the war you're fighting is the right one."

3 3

Issue 882 in moose-technology: PetitParser Inspector tab in GTInspector does not work
by moose-technology＠googlecode.com 03 Dec '12

03 Dec '12

Status: New Owner: ---- CC: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-PetitParser New issue 882 by kurs....(a)gmail.com: PetitParser Inspector tab in GTInspector does not work http://code.google.com/p/moose-technology/issues/detail?id=882 When opening Petit Parser instance in GTInspector, Inspector tab is empty

1 2

Issue 885 in moose-technology: Moose Finder does not provide the navigation list in alphabetical order
by moose-technology＠googlecode.com 02 Dec '12

02 Dec '12

Status: New Owner: tu...(a)tudorgirba.com Labels: Type-Defect Priority-Medium Component-Finder Milestone-4.7 New issue 885 by tu...(a)tudorgirba.com: Moose Finder does not provide the navigation list in alphabetical order http://code.google.com/p/moose-technology/issues/detail?id=885 For example, for a class, attributes appear somewhere in the middle of the list. It should be on top.

1 1

roassal has open branches
by Tudor Girba 02 Dec '12

02 Dec '12

Hi Alex and Vanessa, At this point, Roassal has open branches. Is this wanted? I guess not, but if yes, which is the official branch? Cheers, Doru -- www.tudorgirba.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

2 1

Issue 811 in moose-technology: Create more virtual association in MooseChef
by moose-technology＠googlecode.com 02 Dec '12

02 Dec '12

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Milestone-4.7 New issue 811 by anquetil...(a)gmail.com: Create more virtual association in MooseChef http://code.google.com/p/moose-technology/issues/detail?id=811 Famix recognizes 4 types of associations (reference, access, inheritance, invocation) and Moosechef was built upon these dependencies (queryAllOutgoingReferences, ...) But this will miss a good deal of actual dependencies, because many of them are not expressed by associations: - exceptions caught, thrown - parameter types in parameterized classes - use of annotations - other?

1 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev