Hi, I downloaded latest Moose and I dragged and dropped into the image a st file to file it in. Debugger popped up saying:
SubscriptOutOfBounds: 1
By copy pasting the content of the st file into a workspace and by executing the workspace's content it works.
here the build i used: http://ci.moosetechnology.org/job/moose-latest-dev/923/artifact/moose/
Cheers, Fabrizio
Can you reproduce this on the latest Pharo 1.4?
Doru
On Wed, Apr 11, 2012 at 12:36 PM, Fabrizio Perin fabrizio.perin@gmail.com wrote:
Hi, I downloaded latest Moose and I dragged and dropped into the image a st file to file it in. Debugger popped up saying:
SubscriptOutOfBounds: 1
By copy pasting the content of the st file into a workspace and by executing the workspace's content it works.
here the build i used: http://ci.moosetechnology.org/job/moose-latest-dev/923/artifact/moose/
Cheers, Fabrizio
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
just tried on the latest 1.4 build: https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/375/artifac...
and it works.
Cheers, Fabrizio
2012/4/11 Tudor Girba tudor@tudorgirba.com
Can you reproduce this on the latest Pharo 1.4?
Doru
On Wed, Apr 11, 2012 at 12:36 PM, Fabrizio Perin fabrizio.perin@gmail.com wrote:
Hi, I downloaded latest Moose and I dragged and dropped into the image a st
file
to file it in. Debugger popped up saying:
SubscriptOutOfBounds: 1
By copy pasting the content of the st file into a workspace and by
executing
the workspace's content it works.
here the build i used: http://ci.moosetechnology.org/job/moose-latest-dev/923/artifact/moose/
Cheers, Fabrizio
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
Hi,
Indeed, the problem is that we are loading FS from squeaksource and this lets the system in an inconsistent state because there already is FS in Pharo. I removed it from ConfigurationOfMoose, but something still does not work. I do not know exactly what yet, but I am working on it.
I somehow understood that the idea was to rename FS completely so that there is no conflict when loading the original FS, but it seems it did not happen.
Cheers, Doru
On 11 Apr 2012, at 13:04, Fabrizio Perin wrote:
just tried on the latest 1.4 build: https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/375/artifac...
and it works.
Cheers, Fabrizio
2012/4/11 Tudor Girba tudor@tudorgirba.com Can you reproduce this on the latest Pharo 1.4?
Doru
On Wed, Apr 11, 2012 at 12:36 PM, Fabrizio Perin fabrizio.perin@gmail.com wrote:
Hi, I downloaded latest Moose and I dragged and dropped into the image a st file to file it in. Debugger popped up saying:
SubscriptOutOfBounds: 1
By copy pasting the content of the st file into a workspace and by executing the workspace's content it works.
here the build i used: http://ci.moosetechnology.org/job/moose-latest-dev/923/artifact/moose/
Cheers, Fabrizio
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
"Not knowing how to do something is not an argument for how it cannot be done."
I found the issue:
FS classes were renamed in Pharo by dropping the FS prefix. So, now we have Path in the base image. It's all fine, but we also load STShape80 in Mondrian and EyeSee (mostly for having Circle), and this package contains another class called Path.
So, when we load Moose, we basically override Path from FS, and this breaks the system.
Actually, I do not quite understand why ShapesST80 is not part of Pharo anymore, but in the meantime, I renamed Path to GraphicalPath to not have the collision anymore. The build will let us know if everything is fine now.
Cheers, Doru
On 13 Apr 2012, at 22:09, Tudor Girba wrote:
Hi,
Indeed, the problem is that we are loading FS from squeaksource and this lets the system in an inconsistent state because there already is FS in Pharo. I removed it from ConfigurationOfMoose, but something still does not work. I do not know exactly what yet, but I am working on it.
I somehow understood that the idea was to rename FS completely so that there is no conflict when loading the original FS, but it seems it did not happen.
Cheers, Doru
On 11 Apr 2012, at 13:04, Fabrizio Perin wrote:
just tried on the latest 1.4 build: https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/375/artifac...
and it works.
Cheers, Fabrizio
2012/4/11 Tudor Girba tudor@tudorgirba.com Can you reproduce this on the latest Pharo 1.4?
Doru
On Wed, Apr 11, 2012 at 12:36 PM, Fabrizio Perin fabrizio.perin@gmail.com wrote:
Hi, I downloaded latest Moose and I dragged and dropped into the image a st file to file it in. Debugger popped up saying:
SubscriptOutOfBounds: 1
By copy pasting the content of the st file into a workspace and by executing the workspace's content it works.
here the build i used: http://ci.moosetechnology.org/job/moose-latest-dev/923/artifact/moose/
Cheers, Fabrizio
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
"Not knowing how to do something is not an argument for how it cannot be done."
-- www.tudorgirba.com
"To lead is not to demand things, it is to make them happen."
Mmmhh... Most interesting question I think is why FS classes don't have the prefix FS anymore. Aren't prefixes used to avoid name clashes? So the new Pharo FS should have a prefix like PFS I think.
I think we should find an appropriate prefix for ShapesST80 classes to.
Anyway good to know we found the problem.
Cheers, Fabrizio
2012/4/13 Tudor Girba tudor@tudorgirba.com
I found the issue:
FS classes were renamed in Pharo by dropping the FS prefix. So, now we have Path in the base image. It's all fine, but we also load STShape80 in Mondrian and EyeSee (mostly for having Circle), and this package contains another class called Path.
So, when we load Moose, we basically override Path from FS, and this breaks the system.
Actually, I do not quite understand why ShapesST80 is not part of Pharo anymore, but in the meantime, I renamed Path to GraphicalPath to not have the collision anymore. The build will let us know if everything is fine now.
Cheers, Doru
On 13 Apr 2012, at 22:09, Tudor Girba wrote:
Hi,
Indeed, the problem is that we are loading FS from squeaksource and this
lets the system in an inconsistent state because there already is FS in Pharo. I removed it from ConfigurationOfMoose, but something still does not work. I do not know exactly what yet, but I am working on it.
I somehow understood that the idea was to rename FS completely so that
there is no conflict when loading the original FS, but it seems it did not happen.
Cheers, Doru
On 11 Apr 2012, at 13:04, Fabrizio Perin wrote:
just tried on the latest 1.4 build:
https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/375/artifac...
and it works.
Cheers, Fabrizio
2012/4/11 Tudor Girba tudor@tudorgirba.com Can you reproduce this on the latest Pharo 1.4?
Doru
On Wed, Apr 11, 2012 at 12:36 PM, Fabrizio Perin fabrizio.perin@gmail.com wrote:
Hi, I downloaded latest Moose and I dragged and dropped into the image a
st file
to file it in. Debugger popped up saying:
SubscriptOutOfBounds: 1
By copy pasting the content of the st file into a workspace and by
executing
the workspace's content it works.
here the build i used: http://ci.moosetechnology.org/job/moose-latest-dev/923/artifact/moose/
Cheers, Fabrizio
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
"Not knowing how to do something is not an argument for how it cannot be
done."
-- www.tudorgirba.com
"To lead is not to demand things, it is to make them happen."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi,
On 14 Apr 2012, at 10:19, Fabrizio Perin wrote:
Mmmhh... Most interesting question I think is why FS classes don't have the prefix FS anymore. Aren't prefixes used to avoid name clashes? So the new Pharo FS should have a prefix like PFS I think.
The reason is that FileSystem became a core component in Pharo, and that is a good thing.
I think we should find an appropriate prefix for ShapesST80 classes to.
Probably.
Doru
Anyway good to know we found the problem.
Cheers, Fabrizio
2012/4/13 Tudor Girba tudor@tudorgirba.com I found the issue:
FS classes were renamed in Pharo by dropping the FS prefix. So, now we have Path in the base image. It's all fine, but we also load STShape80 in Mondrian and EyeSee (mostly for having Circle), and this package contains another class called Path.
So, when we load Moose, we basically override Path from FS, and this breaks the system.
Actually, I do not quite understand why ShapesST80 is not part of Pharo anymore, but in the meantime, I renamed Path to GraphicalPath to not have the collision anymore. The build will let us know if everything is fine now.
Cheers, Doru
On 13 Apr 2012, at 22:09, Tudor Girba wrote:
Hi,
Indeed, the problem is that we are loading FS from squeaksource and this lets the system in an inconsistent state because there already is FS in Pharo. I removed it from ConfigurationOfMoose, but something still does not work. I do not know exactly what yet, but I am working on it.
I somehow understood that the idea was to rename FS completely so that there is no conflict when loading the original FS, but it seems it did not happen.
Cheers, Doru
On 11 Apr 2012, at 13:04, Fabrizio Perin wrote:
just tried on the latest 1.4 build: https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/375/artifac...
and it works.
Cheers, Fabrizio
2012/4/11 Tudor Girba tudor@tudorgirba.com Can you reproduce this on the latest Pharo 1.4?
Doru
On Wed, Apr 11, 2012 at 12:36 PM, Fabrizio Perin fabrizio.perin@gmail.com wrote:
Hi, I downloaded latest Moose and I dragged and dropped into the image a st file to file it in. Debugger popped up saying:
SubscriptOutOfBounds: 1
By copy pasting the content of the st file into a workspace and by executing the workspace's content it works.
here the build i used: http://ci.moosetechnology.org/job/moose-latest-dev/923/artifact/moose/
Cheers, Fabrizio
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
"Not knowing how to do something is not an argument for how it cannot be done."
-- www.tudorgirba.com
"To lead is not to demand things, it is to make them happen."
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 now and then stop and ask yourself if the war you're fighting is the right one."
Moose is back to green.
Doru
On 14 Apr 2012, at 11:20, Tudor Girba wrote:
Hi,
On 14 Apr 2012, at 10:19, Fabrizio Perin wrote:
Mmmhh... Most interesting question I think is why FS classes don't have the prefix FS anymore. Aren't prefixes used to avoid name clashes? So the new Pharo FS should have a prefix like PFS I think.
The reason is that FileSystem became a core component in Pharo, and that is a good thing.
I think we should find an appropriate prefix for ShapesST80 classes to.
Probably.
Doru
Anyway good to know we found the problem.
Cheers, Fabrizio
2012/4/13 Tudor Girba tudor@tudorgirba.com I found the issue:
FS classes were renamed in Pharo by dropping the FS prefix. So, now we have Path in the base image. It's all fine, but we also load STShape80 in Mondrian and EyeSee (mostly for having Circle), and this package contains another class called Path.
So, when we load Moose, we basically override Path from FS, and this breaks the system.
Actually, I do not quite understand why ShapesST80 is not part of Pharo anymore, but in the meantime, I renamed Path to GraphicalPath to not have the collision anymore. The build will let us know if everything is fine now.
Cheers, Doru
On 13 Apr 2012, at 22:09, Tudor Girba wrote:
Hi,
Indeed, the problem is that we are loading FS from squeaksource and this lets the system in an inconsistent state because there already is FS in Pharo. I removed it from ConfigurationOfMoose, but something still does not work. I do not know exactly what yet, but I am working on it.
I somehow understood that the idea was to rename FS completely so that there is no conflict when loading the original FS, but it seems it did not happen.
Cheers, Doru
On 11 Apr 2012, at 13:04, Fabrizio Perin wrote:
just tried on the latest 1.4 build: https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/375/artifac...
and it works.
Cheers, Fabrizio
2012/4/11 Tudor Girba tudor@tudorgirba.com Can you reproduce this on the latest Pharo 1.4?
Doru
On Wed, Apr 11, 2012 at 12:36 PM, Fabrizio Perin fabrizio.perin@gmail.com wrote:
Hi, I downloaded latest Moose and I dragged and dropped into the image a st file to file it in. Debugger popped up saying:
SubscriptOutOfBounds: 1
By copy pasting the content of the st file into a workspace and by executing the workspace's content it works.
here the build i used: http://ci.moosetechnology.org/job/moose-latest-dev/923/artifact/moose/
Cheers, Fabrizio
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
"Not knowing how to do something is not an argument for how it cannot be done."
-- www.tudorgirba.com
"To lead is not to demand things, it is to make them happen."
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 now and then stop and ask yourself if the war you're fighting is the right one."
-- www.tudorgirba.com
"From an abstract enough point of view, any two things are similar."
-
Fabrizio Perin -
Tudor Girba