Loading PetitParser in Pharo4 gives font issues
Locked
 
|
Hi all,
I am moving Live Robot Programming to Pharo 4, and I found an issue when loading PetitParser. Some fonts are changed (I guess) and this breaks rendering of text. To reproduce: in the current build open a playgound and do: Gofer it smalltalkhubUser: ‘Moose' project: ‘PetitParser'; configuration; loadDevelopment when everything is loaded, the playground text area changes to the red crossed error morph. (DNU: GLMBrickRenderer class>>render:on:) Opening a new playground and new browser goes OK. But when I open the Spotter and start typing all results are the red error morph (DNU: AthensCairoCanvas>>#line:to:width:color:) Can this be looked at, or can you tell me how I can at least fix the spotter while this is looked at? ---> 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 [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: Loading PetitParser in Pharo4 gives font issues
|
|
Hi, I did not have time to look into it, but I think this is because PetitParser loads a newer version of GlamourCore than the version of Spotter that is integrated. In fact, in order to load the latest Moose, I use the following preamble-script: Gofer new smalltalkhubUser: 'Moose' project: 'GToolkit'; package: 'ConfigurationOfGTSpotter'; package: 'ConfigurationOfGTPlayground'; package: 'ConfigurationOfGTInspector'; package: 'ConfigurationOfGTInspectorCore'; package: 'ConfigurationOfGTPlaygroundCore'; load. Gofer new smalltalkhubUser: 'Moose' project: 'Glamour'; package: 'ConfigurationOfGlamourCore'; load. You could try to use that before loading PetitParser. Cheers, Doru On Tue, Jan 6, 2015 at 2:07 PM, Johan Fabry <[hidden email]> wrote: Hi all, _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
Ah, versions incompatibility again :-( I’m not really happy with having to load a specific version of X to be able to get the default version of Y to work. I have a workaround right now which is to implement the missing message (doing nothing), so I guess that’s OK for me for now.
A more fundamental problem, to me, is why is PetitParser loading Glamour? Is this for the classes in the PetitGUI package? It should be possible to re-implement them using Spec and then there’d be one dependency less. I can have a look at that somewhere this month if you guys would be willing to integrate the results. > On Jan 6, 2015, at 10:41, Tudor Girba <[hidden email]> wrote: > > Hi, > > I did not have time to look into it, but I think this is because PetitParser loads a newer version of GlamourCore than the version of Spotter that is integrated. > > In fact, in order to load the latest Moose, I use the following preamble-script: > Gofer new > smalltalkhubUser: 'Moose' project: 'GToolkit'; > package: 'ConfigurationOfGTSpotter'; > package: 'ConfigurationOfGTPlayground'; > package: 'ConfigurationOfGTInspector'; > package: 'ConfigurationOfGTInspectorCore'; > package: 'ConfigurationOfGTPlaygroundCore'; > load. > Gofer new > smalltalkhubUser: 'Moose' project: 'Glamour'; > package: 'ConfigurationOfGlamourCore'; > load. > > You could try to use that before loading PetitParser. > > Cheers, > Doru > > > > > On Tue, Jan 6, 2015 at 2:07 PM, Johan Fabry <[hidden email]> wrote: > Hi all, > > I am moving Live Robot Programming to Pharo 4, and I found an issue when loading PetitParser. Some fonts are changed (I guess) and this breaks rendering of text. > > To reproduce: in the current build open a playgound and do: > > Gofer it > smalltalkhubUser: ‘Moose' project: ‘PetitParser'; > configuration; > loadDevelopment > > when everything is loaded, the playground text area changes to the red crossed error morph. (DNU: GLMBrickRenderer class>>render:on:) Opening a new playground and new browser goes OK. But when I open the Spotter and start typing all results are the red error morph (DNU: AthensCairoCanvas>>#line:to:width:color:) > > Can this be looked at, or can you tell me how I can at least fix the spotter while this is looked at? > > ---> 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 > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > _______________________________________________ > Moose-dev mailing list > [hidden email] > 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 [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: Loading PetitParser in Pharo4 gives font issues
|
|
Hi, On Tue, Jan 6, 2015 at 4:22 PM, Johan Fabry <[hidden email]> wrote: Ah, versions incompatibility again :-( I do not know what you mean by again. I’m not really happy with having to load a specific version of X to be able to get the default version of Y to work. Please, let's not overreact. This is an issue encountered after we spent 1 day of porting a major application between two major versions of Pharo. Surely, we can wait a little bit longer and solve the remaining problems. I have a workaround right now which is to implement the missing message (doing nothing), so I guess that’s OK for me for now. Yes. You are free to load it without the GUI if you want. It should be possible to re-implement them using Spec and then there’d be one dependency less. I do not see how this would be less. Glamour is already in the Pharo image. I can have a look at that somewhere this month if you guys would be willing to integrate the results. I would not integrate and not maintain such a UI at this point in time. Cheers, Doru
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
Oops, sorry if may mail came over stronger than I meant it to be. (answers inline) > On Jan 6, 2015, at 13:22, Tudor Girba <[hidden email]> wrote: > > > On Tue, Jan 6, 2015 at 4:22 PM, Johan Fabry <[hidden email]> wrote: >> Ah, versions incompatibility again :-( > > I do not know what you mean by again. It’s not specific to this exact case, but I have had a fair share of versioning issues in the past in Pharo. >> I’m not really happy with having to load a specific version of X to be able to get the default version of Y to work. >> > Please, let's not overreact. This is an issue encountered after we spent 1 day of porting a major application between two major versions of Pharo. Surely, we can wait a little bit longer and solve the remaining problems. Sure, it’s just that I understood your mail to mean that I should load (for now) a specific version to get things running. >> I have a workaround right now which is to implement the missing message (doing nothing), so I guess that’s OK for me for now. >> >> A more fundamental problem, to me, is why is PetitParser loading Glamour? Is this for the classes in the PetitGUI package? >> > Yes. You are free to load it without the GUI if you want. > >> It should be possible to re-implement them using Spec and then there’d be one dependency less. >> > I do not see how this would be less. Glamour is already in the Pharo image. I was not aware of that. Now I am. :-) So this is simply the case of updating the configuration to point to the right version? >> I can have a look at that somewhere this month if you guys would be willing to integrate the results. > > I would not integrate and not maintain such a UI at this point in time. OK, I was just trying to find a solution and offering to share it. But if you guys fix the bug in a different way one of these days I am very happy with that solution. :-) ---> 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 [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
In reply to this post by jfabry
Le 6/1/15 16:22, Johan Fabry a écrit : > Ah, versions incompatibility again :-( I’m not really happy with having to load a specific version of X to be able to get the default version of Y to work. I have a workaround right now which is to implement the missing message (doing nothing), so I guess that’s OK for me for now. > > A more fundamental problem, to me, is why is PetitParser loading Glamour? Is this for the classes in the PetitGUI package? It should be possible to re-implement them using Spec and then there’d be one dependency less. I can have a look at that somewhere this month if you guys would be willing to integrate the results. The assembly versus unit problems. PetitParser should come with a package PetitParserUI which loads glamour and petitParser. We are working on having dependencies at the package level with christophe and we should be soon performing an experience using Moose as acid test. Stef > >> On Jan 6, 2015, at 10:41, Tudor Girba <[hidden email]> wrote: >> >> Hi, >> >> I did not have time to look into it, but I think this is because PetitParser loads a newer version of GlamourCore than the version of Spotter that is integrated. >> >> In fact, in order to load the latest Moose, I use the following preamble-script: >> Gofer new >> smalltalkhubUser: 'Moose' project: 'GToolkit'; >> package: 'ConfigurationOfGTSpotter'; >> package: 'ConfigurationOfGTPlayground'; >> package: 'ConfigurationOfGTInspector'; >> package: 'ConfigurationOfGTInspectorCore'; >> package: 'ConfigurationOfGTPlaygroundCore'; >> load. >> Gofer new >> smalltalkhubUser: 'Moose' project: 'Glamour'; >> package: 'ConfigurationOfGlamourCore'; >> load. >> >> You could try to use that before loading PetitParser. >> >> Cheers, >> Doru >> >> >> >> >> On Tue, Jan 6, 2015 at 2:07 PM, Johan Fabry <[hidden email]> wrote: >> Hi all, >> >> I am moving Live Robot Programming to Pharo 4, and I found an issue when loading PetitParser. Some fonts are changed (I guess) and this breaks rendering of text. >> >> To reproduce: in the current build open a playgound and do: >> >> Gofer it >> smalltalkhubUser: ‘Moose' project: ‘PetitParser'; >> configuration; >> loadDevelopment >> >> when everything is loaded, the playground text area changes to the red crossed error morph. (DNU: GLMBrickRenderer class>>render:on:) Opening a new playground and new browser goes OK. But when I open the Spotter and start typing all results are the red error morph (DNU: AthensCairoCanvas>>#line:to:width:color:) >> >> Can this be looked at, or can you tell me how I can at least fix the spotter while this is looked at? >> >> ---> 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 >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> 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 > [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 |
Re: Loading PetitParser in Pharo4 gives font issues
|
I actually loaded PettitParser a few days ago, I had a few red boxes of doom but by the time i reopened my windows I had no issues. I am using Pharo 4 but not the latest image. On Tue, Jan 6, 2015 at 7:56 PM, stepharo <[hidden email]> wrote:
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
«
Return to Moose
|
1 view|%1 views
| Free forum by Nabble | Edit this page |