Hi all,
I don’t know if this is a know issue so I am reporting it: doing a ConfigurationOfPetitParser loadDevelopment in the latest Pharo 4 (40571) breaks some things. There is a DNU on opening the playground: AnObsoleteGLMLiveStringBrick(Object)>>doesNotUnderstand: #textLogic: It’s called from GTPlayground>>codeIn: where a ref to GLMLiveStringBrick is made.
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile
Now that Spotter and Playground are in Pharo updating Glamour to the later version without also updating Spotter and Playground can lead to errors. (Spotter and Playground depend on Glamour).
Right now the only way to sync everything is with the script below. It's not pretty but we do not have a better solution. After you executed the script loading petit parser should work fine.
{ { 'ConfigurationOfRubric'. 'AlainPlantec'. 'Rubric' }. { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGToolkitCore'. 'Moose'. 'GToolkit' }. } do: [ :spec | Gofer new smalltalkhubUser: spec second project: spec third; package: spec first; load ]. ConfigurationOfGToolkitCore loadDevelopment.
Cheers, Andrei
On Fri, Mar 20, 2015 at 10:14 PM, Johan Fabry jfabry@dcc.uchile.cl wrote:
Hi all,
I don’t know if this is a know issue so I am reporting it: doing a ConfigurationOfPetitParser loadDevelopment in the latest Pharo 4 (40571) breaks some things. There is a DNU on opening the playground: AnObsoleteGLMLiveStringBrick(Object)>>doesNotUnderstand: #textLogic: It’s called from GTPlayground>>codeIn: where a ref to GLMLiveStringBrick is made.
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.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
OK, thanks for explaining! Any idea when this will stabilize? Will I need to wait for the release of Pharo4?
On Mar 20, 2015, at 18:38, Andrei Chis chisvasileandrei@gmail.com wrote:
Now that Spotter and Playground are in Pharo updating Glamour to the later version without also updating Spotter and Playground can lead to errors. (Spotter and Playground depend on Glamour).
Right now the only way to sync everything is with the script below. It's not pretty but we do not have a better solution. After you executed the script loading petit parser should work fine.
{ { 'ConfigurationOfRubric'. 'AlainPlantec'. 'Rubric' }. { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGToolkitCore'. 'Moose'. 'GToolkit' }. } do: [ :spec | Gofer new smalltalkhubUser: spec second project: spec third; package: spec first; load ]. ConfigurationOfGToolkitCore loadDevelopment.
Cheers, Andrei
On Fri, Mar 20, 2015 at 10:14 PM, Johan Fabry <jfabry@dcc.uchile.cl mailto:jfabry@dcc.uchile.cl> wrote: Hi all,
I don’t know if this is a know issue so I am reporting it: doing a ConfigurationOfPetitParser loadDevelopment in the latest Pharo 4 (40571) breaks some things. There is a DNU on opening the playground: AnObsoleteGLMLiveStringBrick(Object)>>doesNotUnderstand: #textLogic: It’s called from GTPlayground>>codeIn: where a ref to GLMLiveStringBrick is made.
---> Save our in-boxes! http://emailcharter.org http://emailcharter.org/ <---
Johan Fabry - http://pleiad.cl/~jfabry http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile
Moose-dev mailing list Moose-dev@iam.unibe.ch mailto:Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev 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
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile
Seems you would have this problem even after Pharo 4 Release? cheers -ben
On Sat, Mar 21, 2015 at 11:25 PM, Johan Fabry jfabry@dcc.uchile.cl wrote:
OK, thanks for explaining! Any idea when this will stabilize? Will I need to wait for the release of Pharo4?
On Mar 20, 2015, at 18:38, Andrei Chis chisvasileandrei@gmail.com wrote:
Now that Spotter and Playground are in Pharo updating Glamour to the later version without also updating Spotter and Playground can lead to errors. (Spotter and Playground depend on Glamour).
Right now the only way to sync everything is with the script below. It's not pretty but we do not have a better solution. After you executed the script loading petit parser should work fine.
{ { 'ConfigurationOfRubric'. 'AlainPlantec'. 'Rubric' }. { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGToolkitCore'. 'Moose'. 'GToolkit' }. } do: [ :spec | Gofer new smalltalkhubUser: spec second project: spec third; package: spec first; load ]. ConfigurationOfGToolkitCore loadDevelopment.
Cheers, Andrei
On Fri, Mar 20, 2015 at 10:14 PM, Johan Fabry jfabry@dcc.uchile.cl wrote:
Hi all,
I don’t know if this is a know issue so I am reporting it: doing a ConfigurationOfPetitParser loadDevelopment in the latest Pharo 4 (40571) breaks some things. There is a DNU on opening the playground: AnObsoleteGLMLiveStringBrick(Object)>>doesNotUnderstand: #textLogic: It’s called from GTPlayground>>codeIn: where a ref to GLMLiveStringBrick is made.
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.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
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.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
yes… this is a metacello bug, not a pharo one… so it will need to wait until a metacello fix :)
On 22 Mar 2015, at 09:57, Ben Coman btc@openInWorld.com wrote:
Seems you would have this problem even after Pharo 4 Release? cheers -ben
On Sat, Mar 21, 2015 at 11:25 PM, Johan Fabry <jfabry@dcc.uchile.cl mailto:jfabry@dcc.uchile.cl> wrote:
OK, thanks for explaining! Any idea when this will stabilize? Will I need to wait for the release of Pharo4?
On Mar 20, 2015, at 18:38, Andrei Chis <chisvasileandrei@gmail.com mailto:chisvasileandrei@gmail.com> wrote:
Now that Spotter and Playground are in Pharo updating Glamour to the later version without also updating Spotter and Playground can lead to errors. (Spotter and Playground depend on Glamour).
Right now the only way to sync everything is with the script below. It's not pretty but we do not have a better solution. After you executed the script loading petit parser should work fine.
{ { 'ConfigurationOfRubric'. 'AlainPlantec'. 'Rubric' }. { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGToolkitCore'. 'Moose'. 'GToolkit' }. } do: [ :spec | Gofer new smalltalkhubUser: spec second project: spec third; package: spec first; load ]. ConfigurationOfGToolkitCore loadDevelopment.
Cheers, Andrei
On Fri, Mar 20, 2015 at 10:14 PM, Johan Fabry <jfabry@dcc.uchile.cl mailto:jfabry@dcc.uchile.cl> wrote: Hi all,
I don’t know if this is a know issue so I am reporting it: doing a ConfigurationOfPetitParser loadDevelopment in the latest Pharo 4 (40571) breaks some things. There is a DNU on opening the playground: AnObsoleteGLMLiveStringBrick(Object)>>doesNotUnderstand: #textLogic: It’s called from GTPlayground>>codeIn: where a ref to GLMLiveStringBrick is made.
---> Save our in-boxes! http://emailcharter.org http://emailcharter.org/ <---
Johan Fabry - http://pleiad.cl/~jfabry http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile
Moose-dev mailing list Moose-dev@iam.unibe.ch mailto:Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch mailto:Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev https://www.iam.unibe.ch/mailman/listinfo/moose-dev
---> Save our in-boxes! http://emailcharter.org http://emailcharter.org/ <---
Johan Fabry - http://pleiad.cl/~jfabry http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile
Moose-dev mailing list Moose-dev@iam.unibe.ch mailto:Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev 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
Still in this case even with metacello updating all configurations, loading the development configuration of glamour can break Spotter and Playground if they are not also updated. So what about having the development version of PetitParser depend on the #stable version of glamour?
Cheers, Andrei
On Mon, Mar 23, 2015 at 1:39 PM, Esteban Lorenzano estebanlm@gmail.com wrote:
yes… this is a metacello bug, not a pharo one… so it will need to wait until a metacello fix :)
On 22 Mar 2015, at 09:57, Ben Coman btc@openInWorld.com wrote:
Seems you would have this problem even after Pharo 4 Release? cheers -ben
On Sat, Mar 21, 2015 at 11:25 PM, Johan Fabry jfabry@dcc.uchile.cl wrote:
OK, thanks for explaining! Any idea when this will stabilize? Will I need to wait for the release of Pharo4?
On Mar 20, 2015, at 18:38, Andrei Chis chisvasileandrei@gmail.com wrote:
Now that Spotter and Playground are in Pharo updating Glamour to the later version without also updating Spotter and Playground can lead to errors. (Spotter and Playground depend on Glamour).
Right now the only way to sync everything is with the script below. It's not pretty but we do not have a better solution. After you executed the script loading petit parser should work fine.
{ { 'ConfigurationOfRubric'. 'AlainPlantec'. 'Rubric' }. { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGToolkitCore'. 'Moose'. 'GToolkit' }. } do: [ :spec | Gofer new smalltalkhubUser: spec second project: spec third; package: spec first; load ]. ConfigurationOfGToolkitCore loadDevelopment.
Cheers, Andrei
On Fri, Mar 20, 2015 at 10:14 PM, Johan Fabry jfabry@dcc.uchile.cl wrote:
Hi all,
I don’t know if this is a know issue so I am reporting it: doing a ConfigurationOfPetitParser loadDevelopment in the latest Pharo 4 (40571) breaks some things. There is a DNU on opening the playground: AnObsoleteGLMLiveStringBrick(Object)>>doesNotUnderstand: #textLogic: It’s called from GTPlayground>>codeIn: where a ref to GLMLiveStringBrick is made.
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.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
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.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
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
Is that the Metacello fix that was rejected fro the Pharo4 release?
Stephan
On 23/03/15 13:39, Esteban Lorenzano wrote:
yes… this is a metacello bug, not a pharo one… so it will need to wait until a metacello fix :)
On 22 Mar 2015, at 09:57, Ben Coman <btc@openInWorld.com mailto:btc@openInWorld.com> wrote:
Seems you would have this problem even after Pharo 4 Release? cheers -ben
On Sat, Mar 21, 2015 at 11:25 PM, Johan Fabry <jfabry@dcc.uchile.cl mailto:jfabry@dcc.uchile.cl> wrote:
OK, thanks for explaining! Any idea when this will stabilize? Will I need to wait for the release of Pharo4?On Mar 20, 2015, at 18:38, Andrei Chis <chisvasileandrei@gmail.com <mailto:chisvasileandrei@gmail.com>> wrote: Now that Spotter and Playground are in Pharo updating Glamour to the later version without also updating Spotter and Playground can lead to errors. (Spotter and Playground depend on Glamour). Right now the only way to sync everything is with the script below. It's not pretty but we do not have a better solution. After you executed the script loading petit parser should work fine. { { 'ConfigurationOfRubric'. 'AlainPlantec'. 'Rubric' }. { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGToolkitCore'. 'Moose'. 'GToolkit' }. } do: [ :spec | Gofer new smalltalkhubUser: spec second project: spec third; package: spec first; load ]. ConfigurationOfGToolkitCore loadDevelopment. Cheers, Andrei On Fri, Mar 20, 2015 at 10:14 PM, Johan Fabry <jfabry@dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>> wrote: Hi all, I don’t know if this is a know issue so I am reporting it: doing a ConfigurationOfPetitParser loadDevelopment in the latest Pharo 4 (40571) breaks some things. There is a DNU on opening the playground: AnObsoleteGLMLiveStringBrick(Object)>>doesNotUnderstand: #textLogic: It’s called from GTPlayground>>codeIn: where a ref to GLMLiveStringBrick is made. ---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <--- Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/%7Ejfabry> PLEIAD lab - Computer Science Department (DCC) - University of Chile _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <--- Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/%7Ejfabry> PLEIAD lab - Computer Science Department (DCC) - University of Chile _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch mailto: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 haven't seen any recent bug reports against Metacello ... sooooo, are you referring to the fact that the latest version of Metacello is not loaded into Pharo4.0 or???
Dale
On 03/23/2015 05:39 AM, Esteban Lorenzano wrote:
yes… this is a metacello bug, not a pharo one… so it will need to wait until a metacello fix :)
On 22 Mar 2015, at 09:57, Ben Coman <btc@openInWorld.com mailto:btc@openInWorld.com> wrote:
Seems you would have this problem even after Pharo 4 Release? cheers -ben
On Sat, Mar 21, 2015 at 11:25 PM, Johan Fabry <jfabry@dcc.uchile.cl mailto:jfabry@dcc.uchile.cl> wrote:
OK, thanks for explaining! Any idea when this will stabilize? Will I need to wait for the release of Pharo4?On Mar 20, 2015, at 18:38, Andrei Chis <chisvasileandrei@gmail.com <mailto:chisvasileandrei@gmail.com>> wrote: Now that Spotter and Playground are in Pharo updating Glamour to the later version without also updating Spotter and Playground can lead to errors. (Spotter and Playground depend on Glamour). Right now the only way to sync everything is with the script below. It's not pretty but we do not have a better solution. After you executed the script loading petit parser should work fine. { { 'ConfigurationOfRubric'. 'AlainPlantec'. 'Rubric' }. { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGToolkitCore'. 'Moose'. 'GToolkit' }. } do: [ :spec | Gofer new smalltalkhubUser: spec second project: spec third; package: spec first; load ]. ConfigurationOfGToolkitCore loadDevelopment. Cheers, Andrei On Fri, Mar 20, 2015 at 10:14 PM, Johan Fabry <jfabry@dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>> wrote: Hi all, I don’t know if this is a know issue so I am reporting it: doing a ConfigurationOfPetitParser loadDevelopment in the latest Pharo 4 (40571) breaks some things. There is a DNU on opening the playground: AnObsoleteGLMLiveStringBrick(Object)>>doesNotUnderstand: #textLogic: It’s called from GTPlayground>>codeIn: where a ref to GLMLiveStringBrick is made. ---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <--- Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/%7Ejfabry> PLEIAD lab - Computer Science Department (DCC) - University of Chile _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <--- Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/%7Ejfabry> PLEIAD lab - Computer Science Department (DCC) - University of Chile _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch mailto: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
Esteban,
Perhaps you were referring to this freshly reported bug[1]? If there's another bug out there lurking, I'd like to know about it so I could take care of while I'm hunting down and killing issue #339:)
Dale
[1] https://github.com/dalehenrich/metacello-work/issues/339
On 04/06/2015 02:53 PM, Dale Henrichs wrote:
I haven't seen any recent bug reports against Metacello ... sooooo, are you referring to the fact that the latest version of Metacello is not loaded into Pharo4.0 or???
Dale
On 03/23/2015 05:39 AM, Esteban Lorenzano wrote:
yes… this is a metacello bug, not a pharo one… so it will need to wait until a metacello fix :)
On 22 Mar 2015, at 09:57, Ben Coman <btc@openInWorld.com mailto:btc@openInWorld.com> wrote:
Seems you would have this problem even after Pharo 4 Release? cheers -ben
On Sat, Mar 21, 2015 at 11:25 PM, Johan Fabry <jfabry@dcc.uchile.cl mailto:jfabry@dcc.uchile.cl> wrote:
OK, thanks for explaining! Any idea when this will stabilize? Will I need to wait for the release of Pharo4?On Mar 20, 2015, at 18:38, Andrei Chis <chisvasileandrei@gmail.com <mailto:chisvasileandrei@gmail.com>> wrote: Now that Spotter and Playground are in Pharo updating Glamour to the later version without also updating Spotter and Playground can lead to errors. (Spotter and Playground depend on Glamour). Right now the only way to sync everything is with the script below. It's not pretty but we do not have a better solution. After you executed the script loading petit parser should work fine. { { 'ConfigurationOfRubric'. 'AlainPlantec'. 'Rubric' }. { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGToolkitCore'. 'Moose'. 'GToolkit' }. } do: [ :spec | Gofer new smalltalkhubUser: spec second project: spec third; package: spec first; load ]. ConfigurationOfGToolkitCore loadDevelopment. Cheers, Andrei On Fri, Mar 20, 2015 at 10:14 PM, Johan Fabry <jfabry@dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>> wrote: Hi all, I don’t know if this is a know issue so I am reporting it: doing a ConfigurationOfPetitParser loadDevelopment in the latest Pharo 4 (40571) breaks some things. There is a DNU on opening the playground: AnObsoleteGLMLiveStringBrick(Object)>>doesNotUnderstand: #textLogic: It’s called from GTPlayground>>codeIn: where a ref to GLMLiveStringBrick is made. ---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <--- Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/%7Ejfabry> PLEIAD lab - Computer Science Department (DCC) - University of Chile _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <--- Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/%7Ejfabry> PLEIAD lab - Computer Science Department (DCC) - University of Chile _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch mailto: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
-
Andrei Chis -
Ben Coman -
Dale Henrichs -
Esteban Lorenzano -
Johan Fabry -
Stephan Eggermont