Moose-dev December 2012

moose-dev@list.inf.unibe.ch

15 participants
126 discussions

by Tudor Girba

Hi, The way it looks now, we will be able to release Moose somewhere at the end of the week. Are there any particular issues that you might still have open? Are there any particular Moose-based projects that you would want to include in the main distribution? @Alex: is there anything in Roassal that is pending and that we should wait for? Cheers, Doru -- www.tudorgirba.com "No matter how many recipes we know, we still value a chef."

12 years

Presentations at FOSDEM?

by Stephan Eggermont

Hi, I would be interested to see some of the (new or very impressive) developments presented at the devroom FOSDEM. Would someone be able to show Softwarenaut on Pharo? Stephan

12 years

adding comments to FAMIX

by Tudor Girba

Hi, Does anyone want to help commenting properties and entities in FAMIX meta-models? Here are the two issues: http://code.google.com/p/moose-technology/issues/detail?id=889 (add an MSEComment) http://code.google.com/p/moose-technology/issues/detail?id=890 (add a class comment) Cheers, Doru -- www.tudorgirba.com "We cannot reach the flow of things unless we let go."

12 years

Issue 890 in moose-technology: All meta-entities should have an MSEComment

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Famix Milestone-4.7 New issue 890 by tu...(a)tudorgirba.com: All meta-entities should have an MSEComment http://code.google.com/p/moose-technology/issues/detail?id=890 Here is the list of missing comments: http://ci.moosetechnology.org/job/moose-on-moose/lastCompletedBuild/testRep…

12 years

zOrder: roassal vs mondrian :)

by Tudor Girba

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

12 years

Issue 886 in moose-technology: GLMMorphicSpotterTest>>testCreation is not automatic

by moose-technology＠googlecode.com

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.

12 years

Issue 887 in moose-technology: <MSEProperty: ...> should replace <property: ... > pragmas

by moose-technology＠googlecode.com

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()'

12 years

Jenkins build became unstable: moose-latest-dev #1219

by admin＠moosetechnology.org

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

12 years

Issue 867 in moose-technology: Start rule is missing in the PPAllParsersBrowser

by moose-technology＠googlecode.com

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.

12 years

talks and other media

by Tudor Girba

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

12 years

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev December 2012