Ok, it should be ok for the override. 
But I think I still do not understand how should be saved the concerns :)
When I finish to build a report, I have a collection of REPConcern's objects. Then I do not see how to save directly those objects as Methods. What should I do with those objects?

2010/8/23 Tudor Girba <tudor.girba@gmail.com>
Hi Cyrille,

I took a look. As I mentioned in a private email, it is a nice start, but I think it would be nicer to get the saving of concerns towards directly compiling as methods in the concern class.

Now, an important issue: you are still overriding REPConcernSpecification>>open. Please delete this override.


On 20 Aug 2010, at 17:23, Cyrille Delaunay wrote:

 In order to provide a reporting system for pharo, I implemented some tools over arki, build some concerns, work on way to save reports.
There still work to do, but you can already test it and give me feedback if you want :):

Download the package 'MooseComputedConcerns' at: www.squeaksource.com/MooseDemoReport.
A message will tell you to resolve depencies by first loading 'System-Benchmarks'.
As the concern about benchmarks is not finished you can choose to 'proceed' (the benchmarkConcern will just not been working).
Otherwise you can load 'System-Benchmarks' from the same repository (allow 'block argument assignement' in the settings before).

Then you will be able, in the moose panel, to right click on a model and open a arki reporter.
You can then play a bit with the browser.

pay attencion : load the last version of 'Refactoring-core' to be able to use the LintRules-Concern

Moose-dev mailing list


"Being happy is a matter of choice."

Moose-dev mailing list