wizard based DistributionMap

Hi,

I gived a first try and start to build the wizard and the DistributionMap itSelf.
I put all my classes in the package Moose-MondrianScripts (is it a good idea?).
So, by dowloading the last version of this package, you will be able to test it by right-clicking on a 
FAMIXClassGroup in a MooseFinder 
(For the moment, I have only added a menu item to FAMIXClassGroup, but this visualization could be applied 
on any kind of element)
I fill-in the default inputs of the wizard with a working example, so that you can see how to use it.
Just tell me if it looks like to what you were expecting, what would you change?, what would you had?, any 
suggestions? 

The visualization itself is not yet well-implemented. I'm going to do that now :)

Excellent work, Cyrille!

I gave it a try and it's pretty nice. Of course, I have some comments :).

- first, I went over the visual rendering and changed it a bit have less striking borders and to use a flow layout for the parts so that they try to form a rectangle even when they have different sizes.

- still missing for the visualization are the labels of the parts. It would be great if this got added.

- the overall wizzard is pretty nice, but it is in parts slightly too specific. For example, to select the elements I can choose from only the meta-described properties. This is nice, for most of the things, but maybe you could also allow me to write a script there. A similar situation happens with the property selectors. But, on the other hand this is pretty nice for newcomers because they do not have to write anything.

- in the second screen (Property values) we always get the same values regardless of what properties we selected previously. This is ok if we just choose between number properties, but when we have other kind of properties the window should propose different defaults.

- currently, the distribution map is popped up from the group of parts, which is Ok, but I would want to have it also from the group of elements and from that to select the group of parts. Like this we could cover several kinds of logical operators (I have the elements and derive the parts, or I have the parts and I derive the elements).

That is about it for the moment. But don't get me wrong. I really really like this, especially that it means that the algorithms are back on track. Yuppeee :).

Cheers,
Doru

On 10 Mar 2010, at 18:40, Alexandre Bergel wrote:

I tried and it works fine.

This is really cool!

Alexandre


On 10 Mar 2010, at 11:51, Cyrille Delaunay wrote:

I improved the visualization. Now, elements are ordered by colors and parts are ordered using dendrogram clustering.
So make sure you have the last version of Moose-Algos when testing it (ConfigurationOfMooseAlgos loadDefault).


2010/3/10 Cyrille Delaunay <[hidden email]>
Hi,
I gived a first try and start to build the wizard and the DistributionMap itSelf.
I put all my classes in the package Moose-MondrianScripts (is it a good idea?).
So, by dowloading the last version of this package, you will be able to test it by right-clicking on a
FAMIXClassGroup in a MooseFinder
(For the moment, I have only added a menu item to FAMIXClassGroup, but this visualization could be applied
on any kind of element)
I fill-in the default inputs of the wizard with a working example, so that you can see how to use it.
Just tell me if it looks like to what you were expecting, what would you change?, what would you had?, any
suggestions?
The visualization itself is not yet well-implemented. I'm going to do that now :)

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"Every thing should have the right to be different."

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Alex, a Distribution Map displays parts and elements. For example, you can have classes as parts and methods as elements, or you can have packages as parts and classes as elements.

Yep. I read the paper some time ago. I kind of forgot the terminology.

Adding property names will be cool too

Alexandre

On 24 Mar 2010, at 23:12, Alexandre Bergel wrote:

Hi Cyrille,

This is nice to see distribution map the focus of some effort.
I just want to report my successful experience:

I tried to create a map that put long methods in red (say > 10 LOC), and the remaining in blue. But I am not sure how to beging. I selected 'launch Distribution map from those elements', but what I should fill in 'type of parts' is not apparent to me.

I therefore decided to opt for 'launch Distribution map from those parts'. I selected methods in pre-initialized list since this is what I want to visualize. In the 'pre-initialized list', elements are not ordered. Maybe it would help. I finally found numberOfLinesOfCode. I selected next and was happy to see it finally does what I hoped for.

Maybe you can give an opportunity to the user to edit the name of the properties? property2 and property1 is not so nice in the visualization.

Excellent job!

Alexandre


On 24 Mar 2010, at 13:48, Cyrille Delaunay wrote:

Hi guys,
I have made some improvements about the distribution map:
- we can now launch the wizard from a group deciding to use it as parts or as elements
- I change the code of the distributionMap itself, so that now we have two simple 'constructors'
 => onContainers:elements:propery:
 => onElements:containers:property
Using them, a default colour will be set to the first ten different values of the property.
You can still set your own maping with your own colors.
- In the second pane of the wizard, I added a checkbox, enabling to use this default color system when
selected.
- I have kept the computation of 'possible' lists of  selectors, to choose elements, property and now parts to
base on the map. Now, for some types, it can take some time to open the wizard.  I don't know if having a
'light' wizard can be a good idea?
- In any case, dendrogram clustering for a large number of entities can be very very long

2010/3/15 Simon Denier <[hidden email]>

On 15 mars 2010, at 13:14, Cyrille Delaunay wrote:

Hello,

I tried to improve some of those points and all seems to work correctly.
There is still some things I have to look for:
- allow the visualization to be pop up from the group of elements
- refactor the code
Also, in which package should I finally put all those classes 'Moose- MondrianScripts' or 'Moose-MondrianPaontongs' ?

the second one, create a subcategory Moose-MondrianPaintings-DistributionMap if necessary

2010/3/10 Tudor Girba <[hidden email]>
Excellent work, Cyrille!

I gave it a try and it's pretty nice. Of course, I have some comments :).

- first, I went over the visual rendering and changed it a bit have less striking borders and to use a flow layout for the parts so that they try to form a rectangle even when they have different sizes.

- still missing for the visualization are the labels of the parts. It would be great if this got added.

- the overall wizzard is pretty nice, but it is in parts slightly too specific. For example, to select the elements I can choose from only the meta-described properties. This is nice, for most of the things, but maybe you could also allow me to write a script there. A similar situation happens with the property selectors. But, on the other hand this is pretty nice for newcomers because they do not have to write anything.

- in the second screen (Property values) we always get the same values regardless of what properties we selected previously. This is ok if we just choose between number properties, but when we have other kind of properties the window should propose different defaults.

- currently, the distribution map is popped up from the group of parts, which is Ok, but I would want to have it also from the group of elements and from that to select the group of parts. Like this we could cover several kinds of logical operators (I have the elements and derive the parts, or I have the parts and I derive the elements).

That is about it for the moment. But don't get me wrong. I really really like this, especially that it means that the algorithms are back on track. Yuppeee :).

Cheers,
Doru




On 10 Mar 2010, at 18:40, Alexandre Bergel wrote:

I tried and it works fine.

This is really cool!

Alexandre


On 10 Mar 2010, at 11:51, Cyrille Delaunay wrote:

I improved the visualization. Now, elements are ordered by colors and parts are ordered using dendrogram clustering.
So make sure you have the last version of Moose-Algos when testing it (ConfigurationOfMooseAlgos loadDefault).


2010/3/10 Cyrille Delaunay <[hidden email]>
Hi,
I gived a first try and start to build the wizard and the DistributionMap itSelf.
I put all my classes in the package Moose-MondrianScripts (is it a good idea?).
So, by dowloading the last version of this package, you will be able to test it by right-clicking on a
FAMIXClassGroup in a MooseFinder
(For the moment, I have only added a menu item to FAMIXClassGroup, but this visualization could be applied
on any kind of element)
I fill-in the default inputs of the wizard with a working example, so that you can see how to use it.
Just tell me if it looks like to what you were expecting, what would you change?, what would you had?, any
suggestions?
The visualization itself is not yet well-implemented. I'm going to do that now :)

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"Every thing should have the right to be different."




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
Simon




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"What we can governs what we wish."



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Hi Cyrille,

In the original paper we used: red, blue, cyan, green, pink, dark-green, yellow, magenta, orange

However, in the meantime we changed a bit and now we have the preferred list of colors stored in Color>>strongColors. So, please use this one.

Cheers,
Doru

On 31 Mar 2010, at 15:28, Cyrille Delaunay wrote:

Hello,

You already have the possibility to have automatically-distributed colors: you just have to 'check' the bottom checkbox in the second pane.
Now, there is not yet any order to display the different values of the property. All colors are set in a random order.
What is the 'importance order' the map should follow?  How can I compute it?
I'm looking for the other improvments ;)

2010/3/30 Alexandre Bergel <[hidden email]>
Alex, a Distribution Map displays parts and elements. For example, you can have classes as parts and methods as elements, or you can have packages as parts and classes as elements.

Yep. I read the paper some time ago. I kind of forgot the terminology.

Adding property names will be cool too


Alexandre




On 24 Mar 2010, at 23:12, Alexandre Bergel wrote:

Hi Cyrille,

This is nice to see distribution map the focus of some effort.
I just want to report my successful experience:

I tried to create a map that put long methods in red (say > 10 LOC), and the remaining in blue. But I am not sure how to beging. I selected 'launch Distribution map from those elements', but what I should fill in 'type of parts' is not apparent to me.

I therefore decided to opt for 'launch Distribution map from those parts'. I selected methods in pre-initialized list since this is what I want to visualize. In the 'pre-initialized list', elements are not ordered. Maybe it would help. I finally found numberOfLinesOfCode. I selected next and was happy to see it finally does what I hoped for.

Maybe you can give an opportunity to the user to edit the name of the properties? property2 and property1 is not so nice in the visualization.

Excellent job!

Alexandre


On 24 Mar 2010, at 13:48, Cyrille Delaunay wrote:

Hi guys,
I have made some improvements about the distribution map:
- we can now launch the wizard from a group deciding to use it as parts or as elements
- I change the code of the distributionMap itself, so that now we have two simple 'constructors'
 => onContainers:elements:propery:
 => onElements:containers:property
Using them, a default colour will be set to the first ten different values of the property.
You can still set your own maping with your own colors.
- In the second pane of the wizard, I added a checkbox, enabling to use this default color system when
selected.
- I have kept the computation of 'possible' lists of  selectors, to choose elements, property and now parts to
base on the map. Now, for some types, it can take some time to open the wizard.  I don't know if having a
'light' wizard can be a good idea?
- In any case, dendrogram clustering for a large number of entities can be very very long

2010/3/15 Simon Denier <[hidden email]>

On 15 mars 2010, at 13:14, Cyrille Delaunay wrote:

Hello,

I tried to improve some of those points and all seems to work correctly.
There is still some things I have to look for:
- allow the visualization to be pop up from the group of elements
- refactor the code
Also, in which package should I finally put all those classes 'Moose- MondrianScripts' or 'Moose-MondrianPaontongs' ?


the second one, create a subcategory Moose-MondrianPaintings-DistributionMap if necessary


2010/3/10 Tudor Girba <[hidden email]>
Excellent work, Cyrille!

I gave it a try and it's pretty nice. Of course, I have some comments :).

- first, I went over the visual rendering and changed it a bit have less striking borders and to use a flow layout for the parts so that they try to form a rectangle even when they have different sizes.

- still missing for the visualization are the labels of the parts. It would be great if this got added.

- the overall wizzard is pretty nice, but it is in parts slightly too specific. For example, to select the elements I can choose from only the meta-described properties. This is nice, for most of the things, but maybe you could also allow me to write a script there. A similar situation happens with the property selectors. But, on the other hand this is pretty nice for newcomers because they do not have to write anything.

- in the second screen (Property values) we always get the same values regardless of what properties we selected previously. This is ok if we just choose between number properties, but when we have other kind of properties the window should propose different defaults.

- currently, the distribution map is popped up from the group of parts, which is Ok, but I would want to have it also from the group of elements and from that to select the group of parts. Like this we could cover several kinds of logical operators (I have the elements and derive the parts, or I have the parts and I derive the elements).

That is about it for the moment. But don't get me wrong. I really really like this, especially that it means that the algorithms are back on track. Yuppeee :).

Cheers,
Doru




On 10 Mar 2010, at 18:40, Alexandre Bergel wrote:

I tried and it works fine.

This is really cool!

Alexandre


On 10 Mar 2010, at 11:51, Cyrille Delaunay wrote:

I improved the visualization. Now, elements are ordered by colors and parts are ordered using dendrogram clustering.
So make sure you have the last version of Moose-Algos when testing it (ConfigurationOfMooseAlgos loadDefault).


2010/3/10 Cyrille Delaunay <[hidden email]>
Hi,
I gived a first try and start to build the wizard and the DistributionMap itSelf.
I put all my classes in the package Moose-MondrianScripts (is it a good idea?).
So, by dowloading the last version of this package, you will be able to test it by right-clicking on a
FAMIXClassGroup in a MooseFinder
(For the moment, I have only added a menu item to FAMIXClassGroup, but this visualization could be applied
on any kind of element)
I fill-in the default inputs of the wizard with a working example, so that you can see how to use it.
Just tell me if it looks like to what you were expecting, what would you change?, what would you had?, any
suggestions?
The visualization itself is not yet well-implemented. I'm going to do that now :)

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"Every thing should have the right to be different."




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
Simon




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"What we can governs what we wish."



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"Obvious things are difficult to teach."

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Hi Cyrille,

In general, you want to encode as much as possible with as few visual differences as possible.

Color is a visualization variable, and if you attach it randomly, the only thing it communicates is difference. However, if you preserve some order, you communicate two things.

Now, strongColors is an ordered collection, so you should attach these in the order of importance of the properties: the one property that is most used is red, the second is blue etc.

Cheers,
Doru

On 31 Mar 2010, at 16:14, Cyrille Delaunay wrote:

Ok, thank you.
Now, how do I set a property value to one of those colors? Can I set them in a random way ?

2010/3/31 Tudor Girba <[hidden email]>
Hi Cyrille,

In the original paper we used: red, blue, cyan, green, pink, dark-green, yellow, magenta, orange

However, in the meantime we changed a bit and now we have the preferred list of colors stored in Color>>strongColors. So, please use this one.

Cheers,
Doru


On 31 Mar 2010, at 15:28, Cyrille Delaunay wrote:

Hello,

You already have the possibility to have automatically-distributed colors: you just have to 'check' the bottom checkbox in the second pane.
Now, there is not yet any order to display the different values of the property. All colors are set in a random order.
What is the 'importance order' the map should follow?  How can I compute it?
I'm looking for the other improvments ;)

2010/3/30 Alexandre Bergel <[hidden email]>
Alex, a Distribution Map displays parts and elements. For example, you can have classes as parts and methods as elements, or you can have packages as parts and classes as elements.

Yep. I read the paper some time ago. I kind of forgot the terminology.

Adding property names will be cool too


Alexandre




On 24 Mar 2010, at 23:12, Alexandre Bergel wrote:

Hi Cyrille,

This is nice to see distribution map the focus of some effort.
I just want to report my successful experience:

I tried to create a map that put long methods in red (say > 10 LOC), and the remaining in blue. But I am not sure how to beging. I selected 'launch Distribution map from those elements', but what I should fill in 'type of parts' is not apparent to me.

I therefore decided to opt for 'launch Distribution map from those parts'. I selected methods in pre-initialized list since this is what I want to visualize. In the 'pre-initialized list', elements are not ordered. Maybe it would help. I finally found numberOfLinesOfCode. I selected next and was happy to see it finally does what I hoped for.

Maybe you can give an opportunity to the user to edit the name of the properties? property2 and property1 is not so nice in the visualization.

Excellent job!

Alexandre


On 24 Mar 2010, at 13:48, Cyrille Delaunay wrote:

Hi guys,
I have made some improvements about the distribution map:
- we can now launch the wizard from a group deciding to use it as parts or as elements
- I change the code of the distributionMap itself, so that now we have two simple 'constructors'
 => onContainers:elements:propery:
 => onElements:containers:property
Using them, a default colour will be set to the first ten different values of the property.
You can still set your own maping with your own colors.
- In the second pane of the wizard, I added a checkbox, enabling to use this default color system when
selected.
- I have kept the computation of 'possible' lists of  selectors, to choose elements, property and now parts to
base on the map. Now, for some types, it can take some time to open the wizard.  I don't know if having a
'light' wizard can be a good idea?
- In any case, dendrogram clustering for a large number of entities can be very very long

2010/3/15 Simon Denier <[hidden email]>

On 15 mars 2010, at 13:14, Cyrille Delaunay wrote:

Hello,

I tried to improve some of those points and all seems to work correctly.
There is still some things I have to look for:
- allow the visualization to be pop up from the group of elements
- refactor the code
Also, in which package should I finally put all those classes 'Moose- MondrianScripts' or 'Moose-MondrianPaontongs' ?


the second one, create a subcategory Moose-MondrianPaintings-DistributionMap if necessary


2010/3/10 Tudor Girba <[hidden email]>
Excellent work, Cyrille!

I gave it a try and it's pretty nice. Of course, I have some comments :).

- first, I went over the visual rendering and changed it a bit have less striking borders and to use a flow layout for the parts so that they try to form a rectangle even when they have different sizes.

- still missing for the visualization are the labels of the parts. It would be great if this got added.

- the overall wizzard is pretty nice, but it is in parts slightly too specific. For example, to select the elements I can choose from only the meta-described properties. This is nice, for most of the things, but maybe you could also allow me to write a script there. A similar situation happens with the property selectors. But, on the other hand this is pretty nice for newcomers because they do not have to write anything.

- in the second screen (Property values) we always get the same values regardless of what properties we selected previously. This is ok if we just choose between number properties, but when we have other kind of properties the window should propose different defaults.

- currently, the distribution map is popped up from the group of parts, which is Ok, but I would want to have it also from the group of elements and from that to select the group of parts. Like this we could cover several kinds of logical operators (I have the elements and derive the parts, or I have the parts and I derive the elements).

That is about it for the moment. But don't get me wrong. I really really like this, especially that it means that the algorithms are back on track. Yuppeee :).

Cheers,
Doru




On 10 Mar 2010, at 18:40, Alexandre Bergel wrote:

I tried and it works fine.

This is really cool!

Alexandre


On 10 Mar 2010, at 11:51, Cyrille Delaunay wrote:

I improved the visualization. Now, elements are ordered by colors and parts are ordered using dendrogram clustering.
So make sure you have the last version of Moose-Algos when testing it (ConfigurationOfMooseAlgos loadDefault).


2010/3/10 Cyrille Delaunay <[hidden email]>
Hi,
I gived a first try and start to build the wizard and the DistributionMap itSelf.
I put all my classes in the package Moose-MondrianScripts (is it a good idea?).
So, by dowloading the last version of this package, you will be able to test it by right-clicking on a
FAMIXClassGroup in a MooseFinder
(For the moment, I have only added a menu item to FAMIXClassGroup, but this visualization could be applied
on any kind of element)
I fill-in the default inputs of the wizard with a working example, so that you can see how to use it.
Just tell me if it looks like to what you were expecting, what would you change?, what would you had?, any
suggestions?
The visualization itself is not yet well-implemented. I'm going to do that now :)

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"Every thing should have the right to be different."




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
Simon




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"What we can governs what we wish."



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"Obvious things are difficult to teach."




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"The coherence of a trip is given by the clearness of the goal."

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev