Issue 1102 in moose-technology: Error in GlamourRenderer configuration Moose 5.0

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 1102 in moose-technology: Error in GlamourRenderer configuration Moose 5.0

moose-technology
Status: New
Owner: ----
Labels: Type-Defect Priority-Critical

New issue 1102 by [hidden email]: Error in GlamourRenderer  
configuration Moose 5.0
https://code.google.com/p/moose-technology/issues/detail?id=1102


Load a brand new Moose 5.0 image.
Execute some code from a playground.
There is an issue since the WorkspaceVariable class does not exist in Pharo  
3.0 but only in Pharo 4.0.

I think that the issue comes from the fact that the  
ConfigurationOfGlamourRenderer load version 304 and not 303. We should do a  
ConfigurationOf for Pharo 3.0 and an other one for Pharo 4.0

Moose 5.0 should not evolve anymore.

Anne

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 1102 in moose-technology: Error in GlamourRenderer configuration Moose 5.0

Tudor Girba-2
Hi,

Please use the stable version of the Moose 5.0 release (you might have to redownload). This issue is fixed there.

Doru

On Thu, Jan 8, 2015 at 3:34 PM, <[hidden email]> wrote:
Status: New
Owner: ----
Labels: Type-Defect Priority-Critical

New issue 1102 by [hidden email]: Error in GlamourRenderer configuration Moose 5.0
https://code.google.com/p/moose-technology/issues/detail?id=1102


Load a brand new Moose 5.0 image.
Execute some code from a playground.
There is an issue since the WorkspaceVariable class does not exist in Pharo 3.0 but only in Pharo 4.0.

I think that the issue comes from the fact that the ConfigurationOfGlamourRenderer load version 304 and not 303. We should do a ConfigurationOf for Pharo 3.0 and an other one for Pharo 4.0

Moose 5.0 should not evolve anymore.

Anne

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 1102 in moose-technology: Error in GlamourRenderer configuration Moose 5.0

Anne Etien
Hi,

I was using the PharoLauncher, (because it is a cool tool). But the Pharo launcher was creating the Moose 5.0 version from the last successfully built version. Damien Cassou has changed this in order to have the opportunity to create Moose 5.0 images from the stable version or to create Moose 5.1 images from the last successful built.

For Mac, Pharo launcher is available here: https://ci.inria.fr/pharo/view/all/job/Launcher-Mac/ 

Anne
Le 8 janv. 2015 à 15:41, Tudor Girba <[hidden email]> a écrit :

Hi,

Please use the stable version of the Moose 5.0 release (you might have to redownload). This issue is fixed there.

Doru

On Thu, Jan 8, 2015 at 3:34 PM, <[hidden email]> wrote:
Status: New
Owner: ----
Labels: Type-Defect Priority-Critical

New issue 1102 by [hidden email]: Error in GlamourRenderer configuration Moose 5.0
https://code.google.com/p/moose-technology/issues/detail?id=1102


Load a brand new Moose 5.0 image.
Execute some code from a playground.
There is an issue since the WorkspaceVariable class does not exist in Pharo 3.0 but only in Pharo 4.0.

I think that the issue comes from the fact that the ConfigurationOfGlamourRenderer load version 304 and not 303. We should do a ConfigurationOf for Pharo 3.0 and an other one for Pharo 4.0

Moose 5.0 should not evolve anymore.

Anne

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"
_______________________________________________
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