14 Oct
2010
14 Oct
'10
4:18 p.m.
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
14 Oct
14 Oct
4:23 p.m.
On Thu, Oct 14, 2010 at 4:18 PM, Cyrille Delaunay <cy.delaunay(a)gmail.com>wrote;wrote:
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.
Excellent. I will try :)
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.
DoctorPharo? or DrPharo ? Pharmacy?
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
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
7:31 p.m.
hi Cyrille,
The topic you work one is cool. Google gives a lot of hits for "Menssana". A bit
less for "Mensana".
Please, add a description in http://www.moosetechnology.org/tools
Alexandre
On 14 Oct 2010, at 11:18, Cyrille Delaunay wrote:
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
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
22 Oct
22 Oct
5:03 p.m.
=> All has been repackaged in Arki reporsitory.
=> The last version export and and import faster a report as mse, using the
Fame exporter / importer.
You can load it by evaluating :
Gofer new
squeaksource: 'PharoBenchmarks';
package: 'System-Benchmarking';
version: 'System-Benchmarking-cyrille_delaunay.10';
load.
Gofer new
squeaksource: 'Arki';
package: 'Arki-Menssana';
version: 'Arki-Menssana-cyrille_delaunay.18';
load.
Gofer new
squeaksource: 'Arki';
package: 'Arki-MenssanaBrowser';
version: 'Arki-MenssanaBrowser-cyrille_delaunay.10';
load.
2010/10/14 Alexandre Bergel <alexandre(a)bergel.eu>
hi Cyrille,
The topic you work one is cool. Google gives a lot of hits for "Menssana".
A bit less for "Mensana".
Please, add a description in http://www.moosetechnology.org/tools
Alexandre
On 14 Oct 2010, at 11:18, Cyrille Delaunay wrote:
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
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
5179
days inactive
5187
days old
3 comments
3 participants
participants (3)
-
Alexandre Bergel -
Cyrille Delaunay -
Mariano Martinez Peck