I have no fundamenta solution, but would it be possible to create a version of the configuration that loads development of everything except the UI tools? That would create a version that would be a bit more stable in the face of GlamourCore / Brick changes.
On Jan 26, 2015, at 14:36, Tudor Girba tudor@tudorgirba.com wrote:
The situation is like this: PetitParser depends on Glamour Glamour depends on GlamourCore GlamourCore contains Brick which is still very much changing these days At the same time, GlamourCore already exists in the Pharo image (because of GT)
The problem is that if you load PetitParser, the newer packages of GlamourCore do not get loaded for some reason and this leads to the mentioned issues. I do not know how to solve this actually, and I could use some help.
Doru
On Mon, Jan 26, 2015 at 2:02 PM, Johan Fabry <jfabry@dcc.uchile.cl mailto:jfabry@dcc.uchile.cl> wrote: Hi all,
just to notify that in today’s Pharo 40461 doing a ConfigurationOfPetitParser loadDevelopment leads to a broken image: red morphs of death appear in already open windows and opening the spotter gives a DNU GLMBrick>>widthBlock It would be cool if some knowledgeable person had a look at this, thanks :-)
Greetings.
---> 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
-- www.tudorgirba.com http://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
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile