Hello,
The reporting system based on arki, on which I work, start to be 'usable'.
Some goals was to:
- implement a first set of concerns to be able to make a first try with
pharo as model (
http://code.google.com/p/moose-technology/wiki/PharoHealthSystem)
- have an interface allowing to easily build, modify, save, display reports
(an extended arki browser).
- be able to export a report as MSE, then be able import a mse file.
For now all of that seem to work not so bad :) but I'm sure there is a lot
of thing to change, improve that I have not yet (or maybe no longer) in
mind. If you want to have a look you can evaluate this script in a fresh
moose image:
Gofer new
squeaksource: 'MooseDemoReport';
package: 'System-Benchmarking';
load.
Gofer new
squeaksource: 'MooseDemoReport';
package: 'MooseComputedConcerns';
load.
Then you can simply right click on a model in the moosePanel, 'open arki
reporter', and follow instructions. Any comment about: how it could better,
what you would like to be able to do, things that seems to be wrong or not
well implemented are welcome.
The name of the repository is clearly bad, and I have also to change the
name of of the package. An idea for the package name is: Menssana, (shortcut
for "Mens sana in corpore sano"). If you have any suggestion, I would be
really happy.
A think with which I have some difficulties, is to see the 'borders' between
this package and the arki package. We have an arki package providing the
basic structure to build reports and this new package mainly making
extensions to the arki package. So I don't know if some things should be
merged, and what should be merged?
Then I think I could start to set up automatic jobs with hudson that archive
(at least for now) the mse exported files of a 'PharoHealthReport'.
Then see how we manage to deal with the 'evolution' aspect