April 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Is Pharo Launcher Ready?

by Sean P. DeNigris

Marcus Denker-4 wrote > Yes, but not for Pharo4. Then I think for now we should change the ppa to install an image+VM like the rest. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Is-Pharo-Launcher-Ready-tp4819384p4819390.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 13, 2015

Re: [Pharo-dev] PharoInProgress CI Failing

by Sean P. DeNigris

Dmitri Zagidulin wrote > you also have to add the new chapter to > support/templates/book.latex.template, in the graphicspath section. Thanks! The build is green again and I passed your other suggestions to Jigyasa ----- Cheers, Sean -- View this message in context: http://forum.world.st/PharoInProgress-CI-Failing-tp4819380p4819389.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 13, 2015

Re: [Pharo-dev] PharoInProgress CI Failing

by Dmitri Zagidulin

I had something very similar happen to me today, when porting the Environment chapter of UPBE (the same error in a figure reference, where one line would work, but a similar one (or, actually an exact same one that I retyped) line would compile fine). It turned out that, somehow, there were non-printable characters in the file name. You can see if this is the case for you by either doing a 'cat -v' of your file, or just re-typing the line yourself. I have no idea how those weird characters made it into there, by the way! Maybe something exotic with cut&paste, or a find&replace with regexes in Atom. Actually, I just pulled a fresh copy of the repo, and it doesn't look like there's trouble characters. But, I've noticed a couple of other things: 1) In https://github.com/SmalltalkZen/UpdatedPharoByExample/blob/master/CONTRIBUT… , in Caveats section, it says "You must neither use spaces nor underscores ( _) in file names." Though I doubt it's causing the problem above, why have just the pharo launcher chapter use underscore, when the rest of the chapter names use camel case? 2) All of the labels for the figures are the same, 'obj'. The labels are used for in-line figure references, so having all of the same labels is not helpful (I'm surprised the compiler doesn't complain). 3) Most importantly (this is what actually fixed the error and allowed the book to compile), you also have to add the new chapter to support/templates/book.latex.template, in the graphicspath section. (It can't find the file because it doesn't know to search PharoLauncherTutorial/figures/). (This is mentioned in https://github.com/SmalltalkZen/UpdatedPharoByExample/blob/master/CONTRIBUT… in the 'adding a chapter' section). On Mon, Apr 13, 2015 at 12:32 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > 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

Re: [Pharo-dev] Is Pharo Launcher Ready?

by Marcus Denker

> On 13 Apr 2015, at 19:01, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > IIUC we are planning on making Pharo Launcher the default download. Yes, but not for Pharo4. > Right > now, our installation options are a bit scattered. The Ubuntu package > installs Launcher, and the Mac and Windows buttons at > http://pharo.org/download download image+VM zip files. Should we change the > ppa to install an image+VM? Or should we change the Mac/Windows buttons to > download Launcher installers? A possible reservation about the second option > is that there was a recent report on this list of failed installation on > Windows 8. Was that ever investigated? > > Once we converge on one process, I will update the other GNU/Linux distro > instructions to mirror that. > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Is-Pharo-Launcher-Ready-tp4819384.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

April 13, 2015

Is Pharo Launcher Ready?

by Sean P. DeNigris

IIUC we are planning on making Pharo Launcher the default download. Right now, our installation options are a bit scattered. The Ubuntu package installs Launcher, and the Mac and Windows buttons at http://pharo.org/download download image+VM zip files. Should we change the ppa to install an image+VM? Or should we change the Mac/Windows buttons to download Launcher installers? A possible reservation about the second option is that there was a recent report on this list of failed installation on Windows 8. Was that ever investigated? Once we converge on one process, I will update the other GNU/Linux distro instructions to mirror that. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Is-Pharo-Launcher-Ready-tp4819384.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 13, 2015

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