Hi Jannik,
Would you like to give it a try to build DSM on top of EyeSee? I think it is better suited. There already is a ESMatrixDiagram for basic support.
For example, take a look at ESExamples>>matrixDiagramInteraction1
Cheers,
Doru
--
www.tudorgirba.com
"Being happy is a matter of choice."
Hi,
I would like to release a 4.5 version tomorrow. This should be a minor release but with some essential bug fixes.
The tests that are still red on the server are not essential and they mostly fail because of the mismatch between the tests and running headless on the server (Pharo related issue that we do not know how to solve).
Please, let me know what you think.
Cheers,
Doru
--
www.tudorgirba.com
"It's not how it is, it is how we see it."
Hi Andre,
The newly added Moose-EyeSeeCharts depend on MooseBrowser. The best would be to move MooseBrowser>>eyeseeBrowser to Moose-Finder.
Cheers,
Doru
Begin forwarded message:
> From: admin(a)moosetechnology.org
> Date: 18 June 2011 22:02:32 CEST
> To: tudor(a)tudorgirba.com, simon.denier(a)gmail.com, cy.delaunay(a)gmail.com, alexandre(a)bergel.eu, stephane.ducasse(a)inria.fr, jannik.laval(a)inria.fr
> Subject: Build failed in Jenkins: moose-latest-dev #428
>
> See <http://hudson.moosetechnology.org/job/moose-latest-dev/428/>
>
> ------------------------------------------
> Started by timer
> [workspace] $ /bin/sh -xe /tmp/hudson8003592281926512228.sh
> + rm -rf <http://hudson.moosetechnology.org/job/moose-latest-dev/ws/moose>
> + /srv/hudson.moosetechnology.org/builder/build.sh -i Pharo-1.3 -s moose -s glamorous-theme -s moose-clean -s cleanupforrelease -o moose
> build.sh: error loading code (/srv/pharo/coglinux2382/squeak)
>
> *** Warning: Warning: This package depends on the following classes:
> MooseBrowsers
> You must resolve these dependencies before you will be able to load these definitions:
> MooseBrowsers>>eyeseeBrowser
>
> /srv/hudson.moosetechnology.org/builder/build.sh: line 140: 16059 Killed exec "$PHARO_VM" $PHARO_PARAM "$OUTPUT_IMAGE" "$OUTPUT_SCRIPT"
> Recording test results
> Archiving artifacts
>
--
www.tudorgirba.com
"It's not how it is, it is how we see it."
I have multiple rules that are like
identifierList
^ identifier, ($, asParser trim, identifier) star
It parses a list of identifiers. The output is
#('abc' #(#($, 'def') #($, 'ghj')))
What I like to have is an output of
#( 'abc' 'def' 'ghj' )
I can produce this by changing the rule to
^ identifier , (($, asParser trim, identifier) ==> [:nodes| nodes second]) star
==> [:nodes| (Array with: nodes first) copyWithAll: nodes second ]
But now the rule is uglified. It doesn't work with flatten because I it would flatten all together and I want to have the identifiers separated. What would be useful is a "skip" keyword for the parser so that it is skipped for the output nodes (that would be something like ?: in perl regex).
Are there some better way to do this?
thanks in advance,
Norbert
in 4.4 upward,
FamixAnnotationTypeAttributes have a parentAnnotationType, but the reverse attribute does not exist in AnnotationType.
I believe it was there previously.
bug? feature?
nicolas
Hi guys,
Anybody used the C# importer recently? Do you know
if it exports in FAMIX 2.1? I'm a bit behind the trend with
Softwarenaut and would like to apply it on a case study :)
Cheers,
M.
Anybody to refactor the tools list on the website?
http://www.moosetechnology.org/tools
I started to sort things out, putting generic tools/frameworks on top, and custom tools/projects after.
Maybe it would be good to revise a bit the page, see what is/what is not in the Moose suite and update the information.
And why not adding a 'Moose platform' to group together all things generic?
--
Simon Denier
