I am happy to announce the new home for humane assessment:
Humane assessment is a new software engineering method for making the assessment of software systems practical and manageable. This is made possible by the Moose analysis platform.
The core idea is quite simple: build custom analysis tools to analyze the contextual complexity of your software systems so that you can make better decisions. By decisions I mean anything that has to do with the system: it can be technical (such as, is this concept well encapsulated?, or is my component used the right way?), or it can be broad and strategic (such as, should I refactor my system?).
To make it practical we need to be able to craft tools (sometimes complex tools) fast. This is made feasible by Moose, and in turn, Moose achieves this because of Smalltalk.
The method also covers process and organization-related problems. If you wish, humane assessment is the coat that can place Moose and Smalltalk within any development team.
If you want to promote Smalltalk, perhaps you might want to use this path.
I would be happy to provide more information, support and even materials.
"Be rather willing to give than demanding to get."
I created a simple application using EyeSee, Customizable EyeSee chart,
where you can set the metrics you want to see (similar to Customizable
System Complexity) in a chart.
The x axis shows individual entities (a FAMIXClass, a FAMIXPakage, ...) or a
group (MooseGroup) according to the granularity you set. The y axis shows
the values of the metrics.
I you want to try, run the script below and then right-click in a MooseGroup
-> Visualize -> Customizable EyeSee chart.
- Allow multiple charts
Labels: Type-Defect Priority-Medium Component-EyeSee
New issue 652 by andreho...(a)gmail.com: compositeDiagram bugs
Trying to use compositeDiagram two problems were found:
- ESAbstractDiagram>>elements is working in a wrong way. It should return
the elements of the composed diagrams;
- interaction over ESAbstractDiagram contains some bugs. The selection is
not working (maybe) due the problem above.
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
"Being happy is a matter of choice."
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.
"It's not how it is, it is how we see it."
The newly added Moose-EyeSeeCharts depend on MooseBrowser. The best would be to move MooseBrowser>>eyeseeBrowser to Moose-Finder.
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:
> You must resolve these dependencies before you will be able to load these definitions:
> /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
"It's not how it is, it is how we see it."
I have multiple rules that are like
^ 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,