Currently, there is no object in my knowledge to represent a metric in Moose. I would like to have this kind of object to ask it for example the name of the metric, a description, the associated selector...
Ideally this object should have the same behaviour than Unit framework; it should resolve units for example if you divide number of bugs by lines of code, you should get numberOfBugs.linesOfCode^(-1); then if you multiply this by line of code to get the estimated average value you get numberOfBugs...
If I missed an existing implementation close to this, thank you very much in advance to indicate me otherwise I will create a project for this and you are welcome to contribute.
Really interesting idea ;-) You want to build this on top on anacongua ?
Regards,
On Mon, Mar 31, 2014 at 11:32 AM, Guillaume Larcheveque guillaume.larcheveque@gmail.com wrote:
Currently, there is no object in my knowledge to represent a metric in Moose. I would like to have this kind of object to ask it for example the name of the metric, a description, the associated selector...
Ideally this object should have the same behaviour than Unit framework; it should resolve units for example if you divide number of bugs by lines of code, you should get numberOfBugs.linesOfCode^(-1); then if you multiply this by line of code to get the estimated average value you get numberOfBugs...
If I missed an existing implementation close to this, thank you very much in advance to indicate me otherwise I will create a project for this and you are welcome to contribute.
-- Guillaume Larcheveque
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Mon, Mar 31, 2014 at 11:05 AM, Serge Stinckwich < serge.stinckwich@gmail.com> wrote:
Really interesting idea ;-) You want to build this on top on anacongua ?
What is anacongua? Something in Moose, Pharo?
Regards,
On Mon, Mar 31, 2014 at 11:32 AM, Guillaume Larcheveque guillaume.larcheveque@gmail.com wrote:
Currently, there is no object in my knowledge to represent a metric in Moose. I would like to have this kind of object to ask it for example the name of the metric, a description, the associated selector...
Ideally this object should have the same behaviour than Unit framework;
it
should resolve units for example if you divide number of bugs by lines of code, you should get numberOfBugs.linesOfCode^(-1); then if you multiply this by line of code to get the estimated average value you get numberOfBugs...
If I missed an existing implementation close to this, thank you very
much in
advance to indicate me otherwise I will create a project for this and you are welcome to contribute.
-- Guillaume Larcheveque
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/ _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Where can I find anacongua and what is it? I didn't ever heard about it.
I was planning to build it on top of Units because in my opinion a metric is a unit.
2014-03-31 12:10 GMT+02:00 Usman Bhatti usman.bhatti@gmail.com:
On Mon, Mar 31, 2014 at 11:05 AM, Serge Stinckwich < serge.stinckwich@gmail.com> wrote:
Really interesting idea ;-) You want to build this on top on anacongua ?
What is anacongua? Something in Moose, Pharo?
Regards,
On Mon, Mar 31, 2014 at 11:32 AM, Guillaume Larcheveque guillaume.larcheveque@gmail.com wrote:
Currently, there is no object in my knowledge to represent a metric in Moose. I would like to have this kind of object to ask it for example
the
name of the metric, a description, the associated selector...
Ideally this object should have the same behaviour than Unit framework;
it
should resolve units for example if you divide number of bugs by lines
of
code, you should get numberOfBugs.linesOfCode^(-1); then if you multiply this by line of code to get the estimated average value you get numberOfBugs...
If I missed an existing implementation close to this, thank you very
much in
advance to indicate me otherwise I will create a project for this and
you
are welcome to contribute.
-- Guillaume Larcheveque
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/ _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Ok I found the paper about it and it seems that we are talking of the same thing: http://smalltalkhub.com/#!/~MarcusDenker/Units
2014-03-31 12:50 GMT+02:00 Guillaume Larcheveque < guillaume.larcheveque@gmail.com>:
Where can I find anacongua and what is it? I didn't ever heard about it.
I was planning to build it on top of Units because in my opinion a metric is a unit.
2014-03-31 12:10 GMT+02:00 Usman Bhatti usman.bhatti@gmail.com:
On Mon, Mar 31, 2014 at 11:05 AM, Serge Stinckwich < serge.stinckwich@gmail.com> wrote:
Really interesting idea ;-) You want to build this on top on anacongua ?
What is anacongua? Something in Moose, Pharo?
Regards,
On Mon, Mar 31, 2014 at 11:32 AM, Guillaume Larcheveque guillaume.larcheveque@gmail.com wrote:
Currently, there is no object in my knowledge to represent a metric in Moose. I would like to have this kind of object to ask it for example
the
name of the metric, a description, the associated selector...
Ideally this object should have the same behaviour than Unit
framework; it
should resolve units for example if you divide number of bugs by lines
of
code, you should get numberOfBugs.linesOfCode^(-1); then if you
multiply
this by line of code to get the estimated average value you get numberOfBugs...
If I missed an existing implementation close to this, thank you very
much in
advance to indicate me otherwise I will create a project for this and
you
are welcome to contribute.
-- Guillaume Larcheveque
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/ _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- *Guillaume Larcheveque*
Aconcagua is a unit frameworks.
On 31 Mar 2014, at 12:50, Guillaume Larcheveque guillaume.larcheveque@gmail.com wrote:
Where can I find anacongua and what is it? I didn't ever heard about it.
I was planning to build it on top of Units because in my opinion a metric is a unit.
2014-03-31 12:10 GMT+02:00 Usman Bhatti usman.bhatti@gmail.com:
On Mon, Mar 31, 2014 at 11:05 AM, Serge Stinckwich serge.stinckwich@gmail.com wrote: Really interesting idea ;-) You want to build this on top on anacongua ?
What is anacongua? Something in Moose, Pharo?
Regards,
On Mon, Mar 31, 2014 at 11:32 AM, Guillaume Larcheveque guillaume.larcheveque@gmail.com wrote:
Currently, there is no object in my knowledge to represent a metric in Moose. I would like to have this kind of object to ask it for example the name of the metric, a description, the associated selector...
Ideally this object should have the same behaviour than Unit framework; it should resolve units for example if you divide number of bugs by lines of code, you should get numberOfBugs.linesOfCode^(-1); then if you multiply this by line of code to get the estimated average value you get numberOfBugs...
If I missed an existing implementation close to this, thank you very much in advance to indicate me otherwise I will create a project for this and you are welcome to contribute.
-- Guillaume Larcheveque
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/ _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Guillaume Larcheveque
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi,
Nice project.
You should probably take into consideration that FM3PropertyDescription is an object representing a property. For example: class := FAMIXClass new numberOfLinesOfCode: 42. loc := class mooseDescription allAttributes detect: [ :each | each name = #numberOfLinesOfCode ]. class mmGetProperty: loc ==> 42
A possible route would be to add extra constraints (for example related to the type) to this object.
Another option would be to have the numberOfLinesOfCode method return a linesOfText unit. This implies that code like: group inject: 0 into: [:sum :each | sum + each numberOfLinesOfCode] would break. We can live with this and fix the breaking places, but it should be a thing to consider.
Cheers, Doru
On Mon, Mar 31, 2014 at 11:32 AM, Guillaume Larcheveque < guillaume.larcheveque@gmail.com> wrote:
Currently, there is no object in my knowledge to represent a metric in Moose. I would like to have this kind of object to ask it for example the name of the metric, a description, the associated selector...
Ideally this object should have the same behaviour than Unit framework; it should resolve units for example if you divide number of bugs by lines of code, you should get numberOfBugs.linesOfCode^(-1); then if you multiply this by line of code to get the estimated average value you get numberOfBugs...
If I missed an existing implementation close to this, thank you very much in advance to indicate me otherwise I will create a project for this and you are welcome to contribute.
-- *Guillaume Larcheveque*
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
In certain situations, we need to display metrics with meaningful labels in the browsers and in that case, showing selector names does not look good. With proposed framework, we'll have the objects knowing their labels and know how to compute their units.
On Mon, Mar 31, 2014 at 1:51 PM, Tudor Girba tudor@tudorgirba.com wrote:
Hi,
Nice project.
You should probably take into consideration that FM3PropertyDescription is an object representing a property. For example: class := FAMIXClass new numberOfLinesOfCode: 42. loc := class mooseDescription allAttributes detect: [ :each | each name = #numberOfLinesOfCode ]. class mmGetProperty: loc ==> 42
A possible route would be to add extra constraints (for example related to the type) to this object.
Another option would be to have the numberOfLinesOfCode method return a linesOfText unit. This implies that code like: group inject: 0 into: [:sum :each | sum + each numberOfLinesOfCode] would break. We can live with this and fix the breaking places, but it should be a thing to consider.
Cheers, Doru
On Mon, Mar 31, 2014 at 11:32 AM, Guillaume Larcheveque < guillaume.larcheveque@gmail.com> wrote:
Currently, there is no object in my knowledge to represent a metric in Moose. I would like to have this kind of object to ask it for example the name of the metric, a description, the associated selector...
Ideally this object should have the same behaviour than Unit framework; it should resolve units for example if you divide number of bugs by lines of code, you should get numberOfBugs.linesOfCode^(-1); then if you multiply this by line of code to get the estimated average value you get numberOfBugs...
If I missed an existing implementation close to this, thank you very much in advance to indicate me otherwise I will create a project for this and you are welcome to contribute.
-- *Guillaume Larcheveque*
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow"
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On 01 Apr 2014, at 09:34, Usman Bhatti usman.bhatti@gmail.com wrote:
In certain situations, we need to display metrics with meaningful labels in the browsers and in that case, showing selector names does not look good. With proposed framework, we'll have the objects knowing their labels and know how to compute their units.
I think that it is overkill. Unit is for checking km/h or other stuff Stef
On Mon, Mar 31, 2014 at 1:51 PM, Tudor Girba tudor@tudorgirba.com wrote: Hi,
Nice project.
You should probably take into consideration that FM3PropertyDescription is an object representing a property. For example: class := FAMIXClass new numberOfLinesOfCode: 42. loc := class mooseDescription allAttributes detect: [ :each | each name = #numberOfLinesOfCode ]. class mmGetProperty: loc ==> 42
A possible route would be to add extra constraints (for example related to the type) to this object.
Another option would be to have the numberOfLinesOfCode method return a linesOfText unit. This implies that code like: group inject: 0 into: [:sum :each | sum + each numberOfLinesOfCode] would break. We can live with this and fix the breaking places, but it should be a thing to consider.
Cheers, Doru
On Mon, Mar 31, 2014 at 11:32 AM, Guillaume Larcheveque guillaume.larcheveque@gmail.com wrote: Currently, there is no object in my knowledge to represent a metric in Moose. I would like to have this kind of object to ask it for example the name of the metric, a description, the associated selector...
Ideally this object should have the same behaviour than Unit framework; it should resolve units for example if you divide number of bugs by lines of code, you should get numberOfBugs.linesOfCode^(-1); then if you multiply this by line of code to get the estimated average value you get numberOfBugs...
If I missed an existing implementation close to this, thank you very much in advance to indicate me otherwise I will create a project for this and you are welcome to contribute.
-- Guillaume Larcheveque
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow"
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I am not sure what you are replying to. I understand what you need and I simply pointed out what I think the alternatives are.
If you take the second alternative, it implies significant changes to the way the clients of metrics work with those metrics. But, it can be interesting nevertheless.
Doru
On Tue, Apr 1, 2014 at 9:34 AM, Usman Bhatti usman.bhatti@gmail.com wrote:
In certain situations, we need to display metrics with meaningful labels in the browsers and in that case, showing selector names does not look good. With proposed framework, we'll have the objects knowing their labels and know how to compute their units.
On Mon, Mar 31, 2014 at 1:51 PM, Tudor Girba tudor@tudorgirba.com wrote:
Hi,
Nice project.
You should probably take into consideration that FM3PropertyDescription is an object representing a property. For example: class := FAMIXClass new numberOfLinesOfCode: 42. loc := class mooseDescription allAttributes detect: [ :each | each name = #numberOfLinesOfCode ]. class mmGetProperty: loc ==> 42
A possible route would be to add extra constraints (for example related to the type) to this object.
Another option would be to have the numberOfLinesOfCode method return a linesOfText unit. This implies that code like: group inject: 0 into: [:sum :each | sum + each numberOfLinesOfCode] would break. We can live with this and fix the breaking places, but it should be a thing to consider.
Cheers, Doru
On Mon, Mar 31, 2014 at 11:32 AM, Guillaume Larcheveque < guillaume.larcheveque@gmail.com> wrote:
Currently, there is no object in my knowledge to represent a metric in Moose. I would like to have this kind of object to ask it for example the name of the metric, a description, the associated selector...
Ideally this object should have the same behaviour than Unit framework; it should resolve units for example if you divide number of bugs by lines of code, you should get numberOfBugs.linesOfCode^(-1); then if you multiply this by line of code to get the estimated average value you get numberOfBugs...
If I missed an existing implementation close to this, thank you very much in advance to indicate me otherwise I will create a project for this and you are welcome to contribute.
-- *Guillaume Larcheveque*
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow"
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
We had a meeting with Anne and Nicolas about this and it will break too many things to be reasonably done. Moreover it will be really difficult to still have a consistent meta-model including a Metric type based on a Unit framework.
To solve our problem in Synectique, I will just create a method ( #metric: aSelector ) that will return a MooseMetric object filled with the corresponding MSEProperty and all our Metrics description (displayName, description, unit...) will be defined in a dictionary.
2014-04-02 7:25 GMT+02:00 Tudor Girba tudor@tudorgirba.com:
I am not sure what you are replying to. I understand what you need and I simply pointed out what I think the alternatives are.
If you take the second alternative, it implies significant changes to the way the clients of metrics work with those metrics. But, it can be interesting nevertheless.
Doru
On Tue, Apr 1, 2014 at 9:34 AM, Usman Bhatti usman.bhatti@gmail.comwrote:
In certain situations, we need to display metrics with meaningful labels in the browsers and in that case, showing selector names does not look good. With proposed framework, we'll have the objects knowing their labels and know how to compute their units.
On Mon, Mar 31, 2014 at 1:51 PM, Tudor Girba tudor@tudorgirba.comwrote:
Hi,
Nice project.
You should probably take into consideration that FM3PropertyDescription is an object representing a property. For example: class := FAMIXClass new numberOfLinesOfCode: 42. loc := class mooseDescription allAttributes detect: [ :each | each name = #numberOfLinesOfCode ]. class mmGetProperty: loc ==> 42
A possible route would be to add extra constraints (for example related to the type) to this object.
Another option would be to have the numberOfLinesOfCode method return a linesOfText unit. This implies that code like: group inject: 0 into: [:sum :each | sum + each numberOfLinesOfCode] would break. We can live with this and fix the breaking places, but it should be a thing to consider.
Cheers, Doru
On Mon, Mar 31, 2014 at 11:32 AM, Guillaume Larcheveque < guillaume.larcheveque@gmail.com> wrote:
Currently, there is no object in my knowledge to represent a metric in Moose. I would like to have this kind of object to ask it for example the name of the metric, a description, the associated selector...
Ideally this object should have the same behaviour than Unit framework; it should resolve units for example if you divide number of bugs by lines of code, you should get numberOfBugs.linesOfCode^(-1); then if you multiply this by line of code to get the estimated average value you get numberOfBugs...
If I missed an existing implementation close to this, thank you very much in advance to indicate me otherwise I will create a project for this and you are welcome to contribute.
-- *Guillaume Larcheveque*
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow"
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow"
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Ben Coman -
Guillaume Larcheveque -
Pharo4Stef -
Serge Stinckwich -
Tudor Girba -
Usman Bhatti