- Pharo-dev - lists.pharo.org

PharoInProgress CI Failing

by Sean P. DeNigris

It looks like it's related to the added Launcher chapter: ./AllWorkInProgress.tex:4366: Package pdftex.def Error: File `figures/pharolaun cher_edited_new.png' not found. But the apparently-offending line: +Pharo Launcher>file://figures/pharolauncher_edited_new.png|width=100|label=obj+ Does not seem materially different to me than this one from Bloc which does not seem to be causing the same error: +A more complex use of anchor.>file://figures/moreComplexAnchor.png|width=80|label=moreComplex+ The file seems to be there https://github.com/SquareBracketAssociates/PharoInProgress/blob/master/Phar… Any ideas? ----- Cheers, Sean -- View this message in context: http://forum.world.st/PharoInProgress-CI-Failing-tp4819380.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 13, 2015

Wrap handling (pretty printer)

by Franck Warlouzet

Hello, Working on the pretty printer I have a situation : The max line length of the pretty printer is 120 by default (hard value). Let's see the case of a line too long for the text area but not for the max line length, like this one (unformatted) : Formatted : This is ugly ... (not just because of my tmp variable) because it prints a carriage return after the max length (120 here) but the text editor already did wrap. The pretty printer and the text editor are independant so I do not see how can I adapt the max line length according to the text area bounds. I would like to have something like that : Does anyone know a bit about that ? I would like to relate the max line length with the text area size. Cheers, Franck

April 13, 2015

Re: [Pharo-dev] PharoV40.sources for 40606

by Marcus Denker

> On 13 Apr 2015, at 17:35, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On 13 Apr 2015, at 16:52, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >>> On 13 Apr 2015, at 16:49, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> >>>> On 13 Apr 2015, at 16:35, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>> Yes, that is bad. >>>> >>>> Can you write a short mail or issue entry about what you did exactly, so that others can try to debug this situation ? >>> >>> I did >>> >>> PharoSourcesCondenser condenseNewSources >>> >>> and the after the class comment of LargePositiveInteger is empty, the class comment of others are wrong. >>> (e.g. LargeNegativeInteger is >>> >>> "s >>> ^ separatorsâ >> >> >> The method sources seem to be ok: I can recompile everything with no problem. >> (that I tested already some weeks ago not to run into the famous âcondense sources does not workâ issue >> a day before the releaseâ¦ of course, it was not enough). >> > > I think we fixed itâ¦ slice incoming. > https://pharo.fogbugz.com/f/cases/15336/Writing-a-new-souces-brakes-class-c… <https://pharo.fogbugz.com/f/cases/15336/Writing-a-new-souces-brakes-class-c…> Marcus

April 13, 2015

Re: [Pharo-dev] PharoV40.sources for 40606

by Marcus Denker

> On 13 Apr 2015, at 16:52, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 13 Apr 2015, at 16:49, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >>> On 13 Apr 2015, at 16:35, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> Yes, that is bad. >>> >>> Can you write a short mail or issue entry about what you did exactly, so that others can try to debug this situation ? >> >> I did >> >> PharoSourcesCondenser condenseNewSources >> >> and the after the class comment of LargePositiveInteger is empty, the class comment of others are wrong. >> (e.g. LargeNegativeInteger is >> >> "s >> ^ separatorsâ > > > The method sources seem to be ok: I can recompile everything with no problem. > (that I tested already some weeks ago not to run into the famous âcondense sources does not workâ issue > a day before the releaseâ¦ of course, it was not enough). > I think we fixed itâ¦ slice incoming. Marcus

April 13, 2015

Re: [Pharo-dev] PetitMarkdown

by H. Hirzel

Are there any news on this? --Hannes On 12/28/14, Norbert Hartl <norbert(a)hartl.name> wrote: > I found markdown parsers in smalltalkhub and in the configuration browser. > > http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/ > <http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/> > > and the one in the configuration browser > > PPMarkdown > > If I understand it correctly both are rooted into work Camillo did. The one > in PharoExtras looks newer to me. So I assume the best would be to copy the > ConfigurationOfPetitMarkdown from PharoExtras to MetacelloRepo and remove > the ConfigurationOfPPMarkdown. Right? Or are there any objections? > > Norbert

April 13, 2015

Re: [Pharo-dev] PharoV40.sources for 40606

by Marcus Denker

> On 13 Apr 2015, at 16:49, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 13 Apr 2015, at 16:35, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Yes, that is bad. >> >> Can you write a short mail or issue entry about what you did exactly, so that others can try to debug this situation ? > > I did > > PharoSourcesCondenser condenseNewSources > > and the after the class comment of LargePositiveInteger is empty, the class comment of others are wrong. > (e.g. LargeNegativeInteger is > > "s > ^ separatorsâ The method sources seem to be ok: I can recompile everything with no problem. (that I tested already some weeks ago not to run into the famous âcondense sources does not workâ issue a day before the releaseâ¦ of course, it was not enough). Marcus

April 13, 2015

Re: [Pharo-dev] PharoV40.sources for 40606

by Marcus Denker

> On 13 Apr 2015, at 16:35, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Yes, that is bad. > > Can you write a short mail or issue entry about what you did exactly, so that others can try to debug this situation ? I did PharoSourcesCondenser condenseNewSources and the after the class comment of LargePositiveInteger is empty, the class comment of others are wrong. (e.g. LargeNegativeInteger is "s ^ separatorsâ Marcus

April 13, 2015

Re: [Pharo-dev] PharoV40.sources for 40606

by Sven Van Caekenberghe

Yes, that is bad. Can you write a short mail or issue entry about what you did exactly, so that others can try to debug this situation ? > On 13 Apr 2015, at 16:32, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On 13 Apr 2015, at 16:28, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> >>> On 13 Apr 2015, at 16:17, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>>> >>>> On 13 Apr 2015, at 15:48, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>>> >>>> >>>>> We have to generate a new .source file. We will do that for 40606. >>>>> >>>>> This means that there will be two versions of 40606: one that has a V3 Sources and one with a V4 source. >>>>> To not get confused, the best is to wait for 607. >>>>> >>>> >>>> Ok: >>>> >>>> -> sources file is on >>>> http://files.pharo.org/sources/ >>>> >>>> -> the latest image (40606) use it: >>>> >>>> http://files.pharo.org/image/40/latest.zip >>>> >>>> Next: >>>> >>>> - fix get.pharo.org >>>> - fix the scripts that build the downloads >>>> - do a 607 >>> >>> We did it all. >>> >>> Result: it is all broken. We will revert it all. >> >> All broken is a bit harsh, but yes this is not fun. >> > > It is all broken: when you look at a class comment it shows you parts of method sources. > > Marcus

April 13, 2015

Re: [Pharo-dev] PharoV40.sources for 40606

by Marcus Denker

> On 13 Apr 2015, at 16:28, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > >> On 13 Apr 2015, at 16:17, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >>> >>> On 13 Apr 2015, at 15:48, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> >>>> We have to generate a new .source file. We will do that for 40606. >>>> >>>> This means that there will be two versions of 40606: one that has a V3 Sources and one with a V4 source. >>>> To not get confused, the best is to wait for 607. >>>> >>> >>> Ok: >>> >>> -> sources file is on >>> http://files.pharo.org/sources/ >>> >>> -> the latest image (40606) use it: >>> >>> http://files.pharo.org/image/40/latest.zip >>> >>> Next: >>> >>> - fix get.pharo.org >>> - fix the scripts that build the downloads >>> - do a 607 >> >> We did it all. >> >> Result: it is all broken. We will revert it all. > > All broken is a bit harsh, but yes this is not fun. > It is all broken: when you look at a class comment it shows you parts of method sources. Marcus

April 13, 2015

Re: [Pharo-dev] PharoV40.sources for 40606

by Sven Van Caekenberghe

> On 13 Apr 2015, at 16:17, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On 13 Apr 2015, at 15:48, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >>> We have to generate a new .source file. We will do that for 40606. >>> >>> This means that there will be two versions of 40606: one that has a V3 Sources and one with a V4 source. >>> To not get confused, the best is to wait for 607. >>> >> >> Ok: >> >> -> sources file is on >> http://files.pharo.org/sources/ >> >> -> the latest image (40606) use it: >> >> http://files.pharo.org/image/40/latest.zip >> >> Next: >> >> - fix get.pharo.org >> - fix the scripts that build the downloads >> - do a 607 > > We did it all. > > Result: it is all broken. We will revert it all. All broken is a bit harsh, but yes this is not fun. > What do we learn from it? The artefact on the build server needs to be the artefact of release. > Everything that does not support this needs to be changes. Yes, of course. > Marcus

April 13, 2015