Hi!
I just tried it in a Pharo 1.2 and got 11 errors and 1 failure among the 13 tests. Apparently #displayString is used a bit everywhere. This method does not exist in Pharo.
After having added #displayString on Object, I got other problem with the examples: #any is not understood by a collection, it is invoked in Collection>>minValue.
After changing #any by #anyOne, I was able to get some nice graphics. There are other bugs from here, but I will report them after....
http://code.google.com/p/moose-technology/issues/detail?id=580
Cheers, Alexandre
Hello,
I just removed the dependence to Grease and changed others small things described by Alex. Now we have 12 tests green in Pharo 1.2 and 1.2.1. The test not green is ESExamplesTest>>testSmoke that run all the examples. We still have a dependence to Moose. More specifically: Color>>lightColors Color>>strongColors MalArrayMatrix
To become independent of Moose and all the things work in Pharo we need just provide this classe and methods in EyeSee. Should I do that?
On Mon, Apr 11, 2011 at 6:41 PM, Alexandre Bergel alexandre.bergel@me.comwrote:
Hi!
I just tried it in a Pharo 1.2 and got 11 errors and 1 failure among the 13 tests. Apparently #displayString is used a bit everywhere. This method does not exist in Pharo.
After having added #displayString on Object, I got other problem with the examples: #any is not understood by a collection, it is invoked in Collection>>minValue.
After changing #any by #anyOne, I was able to get some nice graphics. There are other bugs from here, but I will report them after....
http://code.google.com/p/moose-technology/issues/detail?id=580
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi Andre,
On 11 Apr 2011, at 23:21, Andre Hora wrote:
Hello,
I just removed the dependence to Grease and changed others small things described by Alex. Now we have 12 tests green in Pharo 1.2 and 1.2.1.
Great!
The test not green is ESExamplesTest>>testSmoke that run all the examples. We still have a dependence to Moose. More specifically: Color>>lightColors Color>>strongColors MalArrayMatrix
To become independent of Moose and all the things work in Pharo we need just provide this classe and methods in EyeSee. Should I do that?
Yes, please :). Especially the colors should be preserved in some utility class. Ideally, they should make their way into Pharo.
Cheers, Doru
On Mon, Apr 11, 2011 at 6:41 PM, Alexandre Bergel alexandre.bergel@me.com wrote: Hi!
I just tried it in a Pharo 1.2 and got 11 errors and 1 failure among the 13 tests. Apparently #displayString is used a bit everywhere. This method does not exist in Pharo.
After having added #displayString on Object, I got other problem with the examples: #any is not understood by a collection, it is invoked in Collection>>minValue.
After changing #any by #anyOne, I was able to get some nice graphics. There are other bugs from here, but I will report them after....
http://code.google.com/p/moose-technology/issues/detail?id=580
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Andre Hora
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."
On Apr 11, 2011, at 11:27 PM, Tudor Girba wrote:
Hi Andre,
On 11 Apr 2011, at 23:21, Andre Hora wrote:
Hello,
I just removed the dependence to Grease and changed others small things described by Alex. Now we have 12 tests green in Pharo 1.2 and 1.2.1.
Great!
The test not green is ESExamplesTest>>testSmoke that run all the examples. We still have a dependence to Moose. More specifically: Color>>lightColors Color>>strongColors MalArrayMatrix
To become independent of Moose and all the things work in Pharo we need just provide this classe and methods in EyeSee. Should I do that?
Yes, please :). Especially the colors should be preserved in some utility class. Ideally, they should make their way into Pharo.
Yes send a cs for the Color class and it will get integrated
http://code.google.com/p/pharo/issues/detail?id=4018 The issue contains a .cs file with the few methods added by Mondrian on Color.
Alexandre
On 13 Apr 2011, at 14:35, Stéphane Ducasse wrote:
On Apr 11, 2011, at 11:27 PM, Tudor Girba wrote:
Hi Andre,
On 11 Apr 2011, at 23:21, Andre Hora wrote:
Hello,
I just removed the dependence to Grease and changed others small things described by Alex. Now we have 12 tests green in Pharo 1.2 and 1.2.1.
Great!
The test not green is ESExamplesTest>>testSmoke that run all the examples. We still have a dependence to Moose. More specifically: Color>>lightColors Color>>strongColors MalArrayMatrix
To become independent of Moose and all the things work in Pharo we need just provide this classe and methods in EyeSee. Should I do that?
Yes, please :). Especially the colors should be preserved in some utility class. Ideally, they should make their way into Pharo.
Yes send a cs for the Color class and it will get integrated
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
The XKCDColors class of Mondrian has a bunch more, (a subset) would be a good addition as well.
On 14 Apr 2011, at 09:36, Alexandre Bergel wrote:
http://code.google.com/p/pharo/issues/detail?id=4018 The issue contains a .cs file with the few methods added by Mondrian on Color.
Alexandre
On 13 Apr 2011, at 14:35, Stéphane Ducasse wrote:
On Apr 11, 2011, at 11:27 PM, Tudor Girba wrote:
Hi Andre,
On 11 Apr 2011, at 23:21, Andre Hora wrote:
Hello,
I just removed the dependence to Grease and changed others small things described by Alex. Now we have 12 tests green in Pharo 1.2 and 1.2.1.
Great!
The test not green is ESExamplesTest>>testSmoke that run all the examples. We still have a dependence to Moose. More specifically: Color>>lightColors Color>>strongColors MalArrayMatrix
To become independent of Moose and all the things work in Pharo we need just provide this classe and methods in EyeSee. Should I do that?
Yes, please :). Especially the colors should be preserved in some utility class. Ideally, they should make their way into Pharo.
Yes send a cs for the Color class and it will get integrated
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Johan Fabry jfabry@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile
I uploaded them on the google website.
Alexandre
On 14 Apr 2011, at 09:49, Johan Fabry wrote:
The XKCDColors class of Mondrian has a bunch more, (a subset) would be a good addition as well.
On 14 Apr 2011, at 09:36, Alexandre Bergel wrote:
http://code.google.com/p/pharo/issues/detail?id=4018 The issue contains a .cs file with the few methods added by Mondrian on Color.
Alexandre
On 13 Apr 2011, at 14:35, Stéphane Ducasse wrote:
On Apr 11, 2011, at 11:27 PM, Tudor Girba wrote:
Hi Andre,
On 11 Apr 2011, at 23:21, Andre Hora wrote:
Hello,
I just removed the dependence to Grease and changed others small things described by Alex. Now we have 12 tests green in Pharo 1.2 and 1.2.1.
Great!
The test not green is ESExamplesTest>>testSmoke that run all the examples. We still have a dependence to Moose. More specifically: Color>>lightColors Color>>strongColors MalArrayMatrix
To become independent of Moose and all the things work in Pharo we need just provide this classe and methods in EyeSee. Should I do that?
Yes, please :). Especially the colors should be preserved in some utility class. Ideally, they should make their way into Pharo.
Yes send a cs for the Color class and it will get integrated
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Johan Fabry jfabry@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Excellent!
Color>>lightColors Color>>strongColors
These two are part of Mondrian. Best would be to make these extensions part of the base image.
There is a refresh bug apparently. When I open an example, part of the drawing is not done. Do you see it?
Cheers, Alexandre
On 11 Apr 2011, at 17:21, Andre Hora wrote:
Hello,
I just removed the dependence to Grease and changed others small things described by Alex. Now we have 12 tests green in Pharo 1.2 and 1.2.1. The test not green is ESExamplesTest>>testSmoke that run all the examples. We still have a dependence to Moose. More specifically: Color>>lightColors Color>>strongColors MalArrayMatrix
To become independent of Moose and all the things work in Pharo we need just provide this classe and methods in EyeSee. Should I do that?
On Mon, Apr 11, 2011 at 6:41 PM, Alexandre Bergel alexandre.bergel@me.com wrote: Hi!
I just tried it in a Pharo 1.2 and got 11 errors and 1 failure among the 13 tests. Apparently #displayString is used a bit everywhere. This method does not exist in Pharo.
After having added #displayString on Object, I got other problem with the examples: #any is not understood by a collection, it is invoked in Collection>>minValue.
After changing #any by #anyOne, I was able to get some nice graphics. There are other bugs from here, but I will report them after....
http://code.google.com/p/moose-technology/issues/detail?id=580
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Andre Hora
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
While we are talking about EyeSee, let me do a bit of publicity for my own work. It would be cool to have a new version for each a nice traceability of EyeSee's versions. Especially that it has been split into many packages. MetacelloBrowser should make the thing simple.
Alexandre
On 11 Apr 2011, at 18:30, Alexandre Bergel wrote:
Excellent!
Color>>lightColors Color>>strongColors
These two are part of Mondrian. Best would be to make these extensions part of the base image.
There is a refresh bug apparently. When I open an example, part of the drawing is not done. Do you see it?
Cheers, Alexandre
On 11 Apr 2011, at 17:21, Andre Hora wrote:
Hello,
I just removed the dependence to Grease and changed others small things described by Alex. Now we have 12 tests green in Pharo 1.2 and 1.2.1. The test not green is ESExamplesTest>>testSmoke that run all the examples. We still have a dependence to Moose. More specifically: Color>>lightColors Color>>strongColors MalArrayMatrix
To become independent of Moose and all the things work in Pharo we need just provide this classe and methods in EyeSee. Should I do that?
On Mon, Apr 11, 2011 at 6:41 PM, Alexandre Bergel alexandre.bergel@me.com wrote: Hi!
I just tried it in a Pharo 1.2 and got 11 errors and 1 failure among the 13 tests. Apparently #displayString is used a bit everywhere. This method does not exist in Pharo.
After having added #displayString on Object, I got other problem with the examples: #any is not understood by a collection, it is invoked in Collection>>minValue.
After changing #any by #anyOne, I was able to get some nice graphics. There are other bugs from here, but I will report them after....
http://code.google.com/p/moose-technology/issues/detail?id=580
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Andre Hora
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi Alex,
Do you have a ConfigurationOf or Gofer script to try EyeSee in Pharo-Core 1.2.1 without having to install Moose? Cheers,
Hernán
2011/4/12 Alexandre Bergel alexandre.bergel@me.com:
While we are talking about EyeSee, let me do a bit of publicity for my own work. It would be cool to have a new version for each a nice traceability of EyeSee's versions. Especially that it has been split into many packages. MetacelloBrowser should make the thing simple.
Alexandre
On 11 Apr 2011, at 18:30, Alexandre Bergel wrote:
Excellent!
Color>>lightColors Color>>strongColors
These two are part of Mondrian. Best would be to make these extensions part of the base image.
There is a refresh bug apparently. When I open an example, part of the drawing is not done. Do you see it?
Cheers, Alexandre
On 11 Apr 2011, at 17:21, Andre Hora wrote:
Hello,
I just removed the dependence to Grease and changed others small things described by Alex. Now we have 12 tests green in Pharo 1.2 and 1.2.1. The test not green is ESExamplesTest>>testSmoke that run all the examples. We still have a dependence to Moose. More specifically: Color>>lightColors Color>>strongColors MalArrayMatrix
To become independent of Moose and all the things work in Pharo we need just provide this classe and methods in EyeSee. Should I do that?
On Mon, Apr 11, 2011 at 6:41 PM, Alexandre Bergel alexandre.bergel@me.com wrote: Hi!
I just tried it in a Pharo 1.2 and got 11 errors and 1 failure among the 13 tests. Apparently #displayString is used a bit everywhere. This method does not exist in Pharo.
After having added #displayString on Object, I got other problem with the examples: #any is not understood by a collection, it is invoked in Collection>>minValue.
After changing #any by #anyOne, I was able to get some nice graphics. There are other bugs from here, but I will report them after....
http://code.google.com/p/moose-technology/issues/detail?id=580
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Andre Hora
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Try:
Gofer it squeaksource: 'EyeSee'; package: 'ConfigurationOfEyeSee'; load. (Smalltalk at: #ConfigurationOfEyeSee) loadDefault
Cheers, Doru
On 12 Apr 2011, at 08:43, Hernán Morales Durand wrote:
Hi Alex,
Do you have a ConfigurationOf or Gofer script to try EyeSee in Pharo-Core 1.2.1 without having to install Moose? Cheers,
Hernán
2011/4/12 Alexandre Bergel alexandre.bergel@me.com:
While we are talking about EyeSee, let me do a bit of publicity for my own work. It would be cool to have a new version for each a nice traceability of EyeSee's versions. Especially that it has been split into many packages. MetacelloBrowser should make the thing simple.
Alexandre
On 11 Apr 2011, at 18:30, Alexandre Bergel wrote:
Excellent!
Color>>lightColors Color>>strongColors
These two are part of Mondrian. Best would be to make these extensions part of the base image.
There is a refresh bug apparently. When I open an example, part of the drawing is not done. Do you see it?
Cheers, Alexandre
On 11 Apr 2011, at 17:21, Andre Hora wrote:
Hello,
I just removed the dependence to Grease and changed others small things described by Alex. Now we have 12 tests green in Pharo 1.2 and 1.2.1. The test not green is ESExamplesTest>>testSmoke that run all the examples. We still have a dependence to Moose. More specifically: Color>>lightColors Color>>strongColors MalArrayMatrix
To become independent of Moose and all the things work in Pharo we need just provide this classe and methods in EyeSee. Should I do that?
On Mon, Apr 11, 2011 at 6:41 PM, Alexandre Bergel alexandre.bergel@me.com wrote: Hi!
I just tried it in a Pharo 1.2 and got 11 errors and 1 failure among the 13 tests. Apparently #displayString is used a bit everywhere. This method does not exist in Pharo.
After having added #displayString on Object, I got other problem with the examples: #any is not understood by a collection, it is invoked in Collection>>minValue.
After changing #any by #anyOne, I was able to get some nice graphics. There are other bugs from here, but I will report them after....
http://code.google.com/p/moose-technology/issues/detail?id=580
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Andre Hora
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
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
"Beauty is where we see it."
The 13 tests are green. Cool As I said, it would be cool to have a version for each increment, even minor. Since many of us are doing research on software evolution, we need material.
Cheers, Alexandre
On 12 Apr 2011, at 02:55, Tudor Girba wrote:
Try:
Gofer it squeaksource: 'EyeSee'; package: 'ConfigurationOfEyeSee'; load. (Smalltalk at: #ConfigurationOfEyeSee) loadDefault
Cheers, Doru
On 12 Apr 2011, at 08:43, Hernán Morales Durand wrote:
Hi Alex,
Do you have a ConfigurationOf or Gofer script to try EyeSee in Pharo-Core 1.2.1 without having to install Moose? Cheers,
Hernán
2011/4/12 Alexandre Bergel alexandre.bergel@me.com:
While we are talking about EyeSee, let me do a bit of publicity for my own work. It would be cool to have a new version for each a nice traceability of EyeSee's versions. Especially that it has been split into many packages. MetacelloBrowser should make the thing simple.
Alexandre
On 11 Apr 2011, at 18:30, Alexandre Bergel wrote:
Excellent!
Color>>lightColors Color>>strongColors
These two are part of Mondrian. Best would be to make these extensions part of the base image.
There is a refresh bug apparently. When I open an example, part of the drawing is not done. Do you see it?
Cheers, Alexandre
On 11 Apr 2011, at 17:21, Andre Hora wrote:
Hello,
I just removed the dependence to Grease and changed others small things described by Alex. Now we have 12 tests green in Pharo 1.2 and 1.2.1. The test not green is ESExamplesTest>>testSmoke that run all the examples. We still have a dependence to Moose. More specifically: Color>>lightColors Color>>strongColors MalArrayMatrix
To become independent of Moose and all the things work in Pharo we need just provide this classe and methods in EyeSee. Should I do that?
On Mon, Apr 11, 2011 at 6:41 PM, Alexandre Bergel alexandre.bergel@me.com wrote: Hi!
I just tried it in a Pharo 1.2 and got 11 errors and 1 failure among the 13 tests. Apparently #displayString is used a bit everywhere. This method does not exist in Pharo.
After having added #displayString on Object, I got other problem with the examples: #any is not understood by a collection, it is invoked in Collection>>minValue.
After changing #any by #anyOne, I was able to get some nice graphics. There are other bugs from here, but I will report them after....
http://code.google.com/p/moose-technology/issues/detail?id=580
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Andre Hora
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
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
"Beauty is where we see it."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I am trying to use it, but the problems are: - knowing what else was committed in the meantime, and - merging
Cheers, Doru
On 12 Apr 2011, at 15:08, Alexandre Bergel wrote:
The 13 tests are green. Cool As I said, it would be cool to have a version for each increment, even minor. Since many of us are doing research on software evolution, we need material.
Cheers, Alexandre
On 12 Apr 2011, at 02:55, Tudor Girba wrote:
Try:
Gofer it squeaksource: 'EyeSee'; package: 'ConfigurationOfEyeSee'; load. (Smalltalk at: #ConfigurationOfEyeSee) loadDefault
Cheers, Doru
On 12 Apr 2011, at 08:43, Hernán Morales Durand wrote:
Hi Alex,
Do you have a ConfigurationOf or Gofer script to try EyeSee in Pharo-Core 1.2.1 without having to install Moose? Cheers,
Hernán
2011/4/12 Alexandre Bergel alexandre.bergel@me.com:
While we are talking about EyeSee, let me do a bit of publicity for my own work. It would be cool to have a new version for each a nice traceability of EyeSee's versions. Especially that it has been split into many packages. MetacelloBrowser should make the thing simple.
Alexandre
On 11 Apr 2011, at 18:30, Alexandre Bergel wrote:
Excellent!
Color>>lightColors Color>>strongColors
These two are part of Mondrian. Best would be to make these extensions part of the base image.
There is a refresh bug apparently. When I open an example, part of the drawing is not done. Do you see it?
Cheers, Alexandre
On 11 Apr 2011, at 17:21, Andre Hora wrote:
Hello,
I just removed the dependence to Grease and changed others small things described by Alex. Now we have 12 tests green in Pharo 1.2 and 1.2.1. The test not green is ESExamplesTest>>testSmoke that run all the examples. We still have a dependence to Moose. More specifically: Color>>lightColors Color>>strongColors MalArrayMatrix
To become independent of Moose and all the things work in Pharo we need just provide this classe and methods in EyeSee. Should I do that?
On Mon, Apr 11, 2011 at 6:41 PM, Alexandre Bergel alexandre.bergel@me.com wrote: Hi!
I just tried it in a Pharo 1.2 and got 11 errors and 1 failure among the 13 tests. Apparently #displayString is used a bit everywhere. This method does not exist in Pharo.
After having added #displayString on Object, I got other problem with the examples: #any is not understood by a collection, it is invoked in Collection>>minValue.
After changing #any by #anyOne, I was able to get some nice graphics. There are other bugs from here, but I will report them after....
http://code.google.com/p/moose-technology/issues/detail?id=580
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Andre Hora
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
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
"Beauty is where we see it."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing should have the right to be different."
I am trying to use it, but the problems are:
- knowing what else was committed in the meantime, and
- merging
Yes, unfortunately there is no immediate and automatic solution for this. But really, have a trace at a fine grain is important. I agree with Dale that merging and concurrent saving are important and go a bit against doing a lot of commit. But I have more than 50 versions of Mondrian, and this is cool. I really would like to do the same for moose.
Cheers, Alexandre
On 12 Apr 2011, at 15:08, Alexandre Bergel wrote:
The 13 tests are green. Cool As I said, it would be cool to have a version for each increment, even minor. Since many of us are doing research on software evolution, we need material.
Cheers, Alexandre
On 12 Apr 2011, at 02:55, Tudor Girba wrote:
Try:
Gofer it squeaksource: 'EyeSee'; package: 'ConfigurationOfEyeSee'; load. (Smalltalk at: #ConfigurationOfEyeSee) loadDefault
Cheers, Doru
On 12 Apr 2011, at 08:43, Hernán Morales Durand wrote:
Hi Alex,
Do you have a ConfigurationOf or Gofer script to try EyeSee in Pharo-Core 1.2.1 without having to install Moose? Cheers,
Hernán
2011/4/12 Alexandre Bergel alexandre.bergel@me.com:
While we are talking about EyeSee, let me do a bit of publicity for my own work. It would be cool to have a new version for each a nice traceability of EyeSee's versions. Especially that it has been split into many packages. MetacelloBrowser should make the thing simple.
Alexandre
On 11 Apr 2011, at 18:30, Alexandre Bergel wrote:
Excellent!
> Color>>lightColors > Color>>strongColors These two are part of Mondrian. Best would be to make these extensions part of the base image.
There is a refresh bug apparently. When I open an example, part of the drawing is not done. Do you see it?
Cheers, Alexandre
On 11 Apr 2011, at 17:21, Andre Hora wrote:
> Hello, > > I just removed the dependence to Grease and changed others small things described by Alex. Now we have 12 tests green in Pharo 1.2 and 1.2.1. > The test not green is ESExamplesTest>>testSmoke that run all the examples. We still have a dependence to Moose. More specifically: > Color>>lightColors > Color>>strongColors > MalArrayMatrix > > To become independent of Moose and all the things work in Pharo we need just provide this classe and methods in EyeSee. Should I do that? > > On Mon, Apr 11, 2011 at 6:41 PM, Alexandre Bergel alexandre.bergel@me.com wrote: > Hi! > > I just tried it in a Pharo 1.2 and got 11 errors and 1 failure among the 13 tests. > Apparently #displayString is used a bit everywhere. This method does not exist in Pharo. > > After having added #displayString on Object, I got other problem with the examples: #any is not understood by a collection, it is invoked in Collection>>minValue. > > After changing #any by #anyOne, I was able to get some nice graphics. There are other bugs from here, but I will report them after.... > > http://code.google.com/p/moose-technology/issues/detail?id=580 > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev@iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > -- > Andre Hora > > _______________________________________________ > Moose-dev mailing list > Moose-dev@iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
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
"Beauty is where we see it."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch 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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Thanks!
2011/4/12 Tudor Girba tudor.girba@gmail.com:
Try:
Gofer it squeaksource: 'EyeSee'; package: 'ConfigurationOfEyeSee'; load. (Smalltalk at: #ConfigurationOfEyeSee) loadDefault
Cheers, Doru
On 12 Apr 2011, at 08:43, Hernán Morales Durand wrote:
Hi Alex,
Do you have a ConfigurationOf or Gofer script to try EyeSee in Pharo-Core 1.2.1 without having to install Moose? Cheers,
Hernán
2011/4/12 Alexandre Bergel alexandre.bergel@me.com:
While we are talking about EyeSee, let me do a bit of publicity for my own work. It would be cool to have a new version for each a nice traceability of EyeSee's versions. Especially that it has been split into many packages. MetacelloBrowser should make the thing simple.
Alexandre
On 11 Apr 2011, at 18:30, Alexandre Bergel wrote:
Excellent!
Color>>lightColors Color>>strongColors
These two are part of Mondrian. Best would be to make these extensions part of the base image.
There is a refresh bug apparently. When I open an example, part of the drawing is not done. Do you see it?
Cheers, Alexandre
On 11 Apr 2011, at 17:21, Andre Hora wrote:
Hello,
I just removed the dependence to Grease and changed others small things described by Alex. Now we have 12 tests green in Pharo 1.2 and 1.2.1. The test not green is ESExamplesTest>>testSmoke that run all the examples. We still have a dependence to Moose. More specifically: Color>>lightColors Color>>strongColors MalArrayMatrix
To become independent of Moose and all the things work in Pharo we need just provide this classe and methods in EyeSee. Should I do that?
On Mon, Apr 11, 2011 at 6:41 PM, Alexandre Bergel alexandre.bergel@me.com wrote: Hi!
I just tried it in a Pharo 1.2 and got 11 errors and 1 failure among the 13 tests. Apparently #displayString is used a bit everywhere. This method does not exist in Pharo.
After having added #displayString on Object, I got other problem with the examples: #any is not understood by a collection, it is invoked in Collection>>minValue.
After changing #any by #anyOne, I was able to get some nice graphics. There are other bugs from here, but I will report them after....
http://code.google.com/p/moose-technology/issues/detail?id=580
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Andre Hora
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
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
"Beauty is where we see it."
Moose-dev mailing list Moose-dev@iam.unibe.ch
-
Alexandre Bergel -
Andre Hora -
Hernán Morales Durand -
Johan Fabry -
Stéphane Ducasse -
Tudor Girba