June 2015 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Environment-independent styler?

by Martin Dias

After debugging a bit and discovering the mess around... I think the best decision is to first migrate the DiffMorph to the new text widget, and then see... MartÃn On Mon, Jun 22, 2015 at 9:53 AM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > 2015-06-22 9:11 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: > >> >> > On 17 Jun 2015, at 18:54, Martin Dias <tinchodias(a)gmail.com> wrote: >> > >> > Hello, >> > >> > Suppose that you want to show the diff between the source code of two >> methods. In the case that both methods are in the same class, and that such >> class is present in the system, then no problem: In a DiffModel, one can >> set a context to the smalltalk syntax styler and get a nice output. >> > >> > DiffModel new >> > leftText: (Point >> #x) sourceCode; >> > rightText: (Point >> #y) sourceCode; >> > contextClass: Point; >> > openWithSpec. >> > >> > <Screen Shot 2015-06-17 at 18.33.22.png> >> > >> > But what happens in the case that the class does not exist in the >> system? >> > >> > If one doesn't set any context to the styler, then the string will be >> shown all in black, which is not nice. A partial solution could be to set >> Object as a context, then the styler will color the code, but instance >> variables are in red: >> > >> > DiffModel new >> > leftText: (Point >> #x) sourceCode; >> > rightText: (Point >> #y) sourceCode; >> > contextClass: Object; >> > openWithSpec. >> > >> > <Screen Shot 2015-06-17 at 18.33.27.png> >> > >> > Which is also not nice. In my opinion, there should be a styler that >> just colors the code following the syntax, without checking if the >> variables or classes are present in the system. It would be an >> environment-independent styler. >> > >> > What do you recommend to implement this? I guess it should be easy to >> subclass SHTextStylerST80 and override some methods to do not check >> anything in the environment. >> > >> > What's your opinion? >> > >> >> Right now we have the problem that we have 3 Stylersâ¦ (for the old text >> model one based on Shout, one AST, and one for TxText based on the AST. Ah, >> and Rubric subclasses the >> shout one, too. Which means 4. >> >> One question is: could a styler fall back onto a being environment >> independent as soon as the environment is not set? >> > > Yes. With a bit of ternary logic which says that symbols are in three > states: defined, undefined and unknown. First two require a context; third > one applies if you don't have a context. > > Thierry >

June 22, 2015

Re: [Pharo-users] <example> pragmas and example* methods use-cases

by Ben Coman

I'll revisit my previous suggestion. In real life... * a "sample" is a real object you can hold. You ask a supplier to "send you a sample" of their product so you can inspect it before you buy lots. In an industrial factory, you "take a sample" to take an item from the process stream to the lab to analyse. Both of these are real objects you can hold. In addition, Digital Signal Processing does sampling, it doesn't do exampling. * an "example" is one step removed from real life objects. The maths teacher works through an example. Someone's behaviour can set a good example. A programming script can provide an example of how to do something. People say "for example, how about my hypothetical** situation". None of these refer to a real object. Now you can use "example" to refer to real objects, but usually second hand when you are describing a general characteristic. It doesn't have the same concrete semantic of a real object as "sample". There were other suggestions that were reasonable. It might be better to have one pragma that is parameterized by what sort of example it is. cheers -ben ** Consider for a moment, what would the world be like without hypothetical situations? On Mon, Jun 22, 2015 at 6:49 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > 2015-06-22 12:03 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: >> >> Hi, >> >> there was a long discussion about the meaning of example* methods and >> <example> pragmas, however I do not know what was the final resolution. >> >> Basically I am interested in two use-cases >> >> 1. executable example (the one where Nautilus shows nice play icon) >> This is as I understand only through example* naming (on class-side). > > > Yes, but I would like to use a pragma again and don't rely naming > convention, we just wasn't able to agree on one. > >> >> >> 2. returning examples (example that returns some value that I can reuse) >> Is this what <example> pragma is for? How would I go about naming it >> considering that having play icon there would be counter-productive (user >> would be clicking on it and nothing would happen). > > > Inspector and spotter use gtExample* names in addition to an <gtExample> > pragma. > <gtExample> -> for finding those methods > gtExample*name -> for not getting the play icon. > > This is less than perfect. > >> >> >> Thanks, >> Peter > >

June 22, 2015

Re: [Pharo-users] About generating chapters with Pillar/Pier tools

by Damien Cassou

HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> writes: > Thank you Ben for taking the time to read. > > Do you (or anyone) mind to share which command do you use to convert from > Pillar generated .tex to .pdf in Linux or OS/X? > Cheers, we use the following Bash script to do everything for the EnterprisePharo book: https://github.com/SquareBracketAssociates/EnterprisePharo/blob/master/comp… To answer your question, converting a .tex to a .pdf is as simple as pdflatex thefile.tex or, if you use lualatex as we do in EnterprisePharo: lualatex thefile.tex -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

June 22, 2015

Re: [Pharo-users] About generating chapters with Pillar/Pier tools

by Damien Cassou

Ferlicot D. Cyril <cyril.ferlicot(a)gmail.com> writes: > Le 21/06/2015 05:21, HernÃ¡n Morales Durand a Ã©crit : >> About instructions given here >> >> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >> >> you do not need MinGW to export a Pier chapter. See here >> https://github.com/biosmalltalk/biopharo/blob/develop/doc/pier2tex.bat >> for an example > > We know that Pillar is not easy to use on Windows and we need to > improve that, but for now we have a lot of work to do with Pillar and > not enough time to do it. Using MinGW is only a temporary solution. I asked Cyril to work on integrating what's currently in Bash scripts inside Pillar itself (e.g.,, iterating over input files, generating pdf from latex). This should make porting much easier (as well as creating new Pillar-based projects). >> Another (worst) situation happened when I wanted to convert a generated >> LaTeX to PDF. I had to remove all tables, annotations and notes from the >> .pier file because errors reported in pdfLaTeX . >> >> For tables : >> >> ! Undefined control sequence. >> >> l.176 \toprule >> > > I'll try to take a look at that one. > Can you send me a pillar file that raise this please ? this one is related to a missing latex package in your latex template. Add this to your LaTeX template (or use the default template Pillar provides or use the template from https://github.com/SquareBracketAssociates/EnterprisePharo/) \usepackage{booktabs} >> For notes (i.e. @@note ) >> >> ! LaTeX Error: Environment note undefined. >> >> >> See the LaTeX manual or LaTeX Companion for explanation. >> >> Type H <return> for immediate help. >> >> ... >> >> l.178 \begin{note} each time you use @@XXXX, the LaTeX document will contain a \begin{XXXX}. This means you have to create the environments you need. So, if you write @@note in your Pillar document, you must add something like this to your LaTeX template: \newenvironment{note}{\begin{center}\begin{minipage}{8cm}\hrule\vspace{0.2cm} \textbf{Note:}}{\vspace{0.3cm}\hrule\end{minipage}\end{center}} Look here for what we use in EnterprisePharo: https://github.com/SquareBracketAssociates/EnterprisePharo/blob/master/supp… -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

June 22, 2015

Re: [Pharo-users] About generating chapters with Pillar/Pier tools

by Ben Coman

Sorry. It was nine months ago I made some small contribution. I don't remember and it may have changed since. cheers -ben On Mon, Jun 22, 2015 at 12:43 PM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > Thank you Ben for taking the time to read. > > Do you (or anyone) mind to share which command do you use to convert from > Pillar generated .tex to .pdf in Linux or OS/X? > Cheers, > > HernÃ¡n > > > 2015-06-21 12:15 GMT-03:00 Ben Coman <btc(a)openinworld.com>: >> >> >> >> On Sun, Jun 21, 2015 at 11:21 AM, HernÃ¡n Morales Durand >> <hernan.morales(a)gmail.com> wrote: >>> >>> >>> Now I am the only one generating PDF with Pillar in Windows? >> >> >> Back when I did a bit on Pillar, difficulties with latex was part of the >> reason I moved to OSX. >> cheers -ben > >

June 22, 2015

Re: [Pharo-users] <example> pragmas and example* methods use-cases

by Nicolai Hess

2015-06-22 12:03 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > Hi, > > there was a long discussion about the meaning of example* methods and > <example> pragmas, however I do not know what was the final resolution. > > Basically I am interested in two use-cases > > 1. executable example (the one where Nautilus shows nice play icon) > This is as I understand only through example* naming (on class-side). > Yes, but I would like to use a pragma again and don't rely naming convention, we just wasn't able to agree on one. > > 2. returning examples (example that returns some value that I can reuse) > Is this what <example> pragma is for? How would I go about naming it > considering that having play icon there would be counter-productive (user > would be clicking on it and nothing would happen). > Inspector and spotter use gtExample* names in addition to an <gtExample> pragma. <gtExample> -> for finding those methods gtExample*name -> for not getting the play icon. This is less than perfect. > > Thanks, > Peter >

June 22, 2015

<example> pragmas and example* methods use-cases

by Peter UhnÃ¡k

Hi, there was a long discussion about the meaning of example* methods and <example> pragmas, however I do not know what was the final resolution. Basically I am interested in two use-cases 1. executable example (the one where Nautilus shows nice play icon) This is as I understand only through example* naming (on class-side). 2. returning examples (example that returns some value that I can reuse) Is this what <example> pragma is for? How would I go about naming it considering that having play icon there would be counter-productive (user would be clicking on it and nothing would happen). Thanks, Peter

June 22, 2015

PetitParser ignorable parsers

by Peter UhnÃ¡k

Hi, is it possible to add such a parser that would consume input, but wouldn't return anything? Right now I do things like... MyParser>>rule ^ ($[ asParser, anotherRule, $] asParser) ==> [ :nodes | nodes second ] Of course when the rules are more complex, so is the block; however it seems that this is how it's done in the example parsers... So, would it be possible to add some kind of Null/Void/Ignore/Throwaway parser, that would consume the input, but would be omitted from the result? so the above method could be written as MyParser>>rule ^ $[ asNullPaser, anotherRule, $] asNullParser or MyParser>>rule ^ $[ asParser ignore, anotherRule, $[ asParser ignore or something else. Thanks, Peter

June 22, 2015

Re: [Pharo-users] About generating chapters with Pillar/Pier tools

by Ferlicot D. Cyril

Le 21/06/2015 05:21, HernÃ¡n Morales Durand a Ã©crit : > Hello, > > I have experimented several dissapointing errors when working with > updated Pillar tools. I am not doing anything special besides working > under Windows. > > Apparently the Pillar CommandLineHandler is not working because > OSEnvironment exception (Windows 8.1). When executing > > Pharo.exe Pillar.image export --to=html BioPharo.pier > > The attached exception raises. > This happens in all the images from: > > https://ci.inria.fr/pharo-contribution/job/Pillar/PHARO=40,VERSION=stable,V… > Pharo4.0 (Latest update: #40614) > https://ci.inria.fr/pharo-contribution/job/Pillar/PHARO=40,VERSION=developm… > Pharo4.0 (Latest update: #40614) > https://ci.inria.fr/pharo-contribution/job/Pillar/PHARO=50,VERSION=stable,V… > Pharo5.0 > Latest update: #50124 > > Changing the method #baseDirectory to use %CD% environment variable > doesn't fix it even when it works in command line: > > c:\MySmalltalkProjects\Pillar\pharo-vm>echo %PWD% > %PWD% > c:\MySmalltalkProjects\Pillar\pharo-vm>echo %CD% > c:\MySmalltalkProjects\Pillar\pharo-vm > > The solution I found was to replace the OSEnvironment line with > FileSystem workingDirectory as suggested at: > https://pharo.fogbugz.com/f/cases/15356/Pillar-command-line-script-doesn-t-… > > About instructions given here > > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… > > you do not need MinGW to export a Pier chapter. See here > https://github.com/biosmalltalk/biopharo/blob/develop/doc/pier2tex.bat > for an example Hi! We know that Pillar is not easy to use on Windows and we need to improve that, but for now we have a lot of work to do with Pillar and not enough time to do it. Using MinGW is only a temporary solution. > > Another (worst) situation happened when I wanted to convert a generated > LaTeX to PDF. I had to remove all tables, annotations and notes from the > .pier file because errors reported in pdfLaTeX . > > For tables : > > ! Undefined control sequence. > > l.176 \toprule > I'll try to take a look at that one. Can you send me a pillar file that raise this please ? > > For notes (i.e. @@note ) > > ! LaTeX Error: Environment note undefined. > > > See the LaTeX manual or LaTeX Companion for explanation. > > Type H <return> for immediate help. > > ... > > l.178 \begin{note} > > Same here, can you send me a file because I never saw this error with @@note. > Finally generated PDF looks different from previous versions. > > Previous Pillar version: > https://github.com/biosmalltalk/biopharo/blob/develop/doc/BioPharo.pier.pdf > > Current Pillar version (>= 0.56) : > https://github.com/biosmalltalk/biopharo/blob/develop/doc/BioPharo.pdf > This one is normal. We changed the way extensions was generated because the previous way wasn't right. When we export a .tex to a .pdf we don't want to have a file .tex.pdf, so when we want to export a .pillar to a .tex we don't want to get a .pillar.pdf! So we changed that. > Now I am the only one generating PDF with Pillar in Windows? I do it but I use some script with MinGW for now or I use Pillar directly from Pharo because the windows environment is not good for now. > > > HernÃ¡n > -- Cheers Cyril Ferlicot-Delbecque

June 22, 2015

Re: [Pharo-users] Environment-independent styler?

by Thierry Goubier

2015-06-22 9:11 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: > > > On 17 Jun 2015, at 18:54, Martin Dias <tinchodias(a)gmail.com> wrote: > > > > Hello, > > > > Suppose that you want to show the diff between the source code of two > methods. In the case that both methods are in the same class, and that such > class is present in the system, then no problem: In a DiffModel, one can > set a context to the smalltalk syntax styler and get a nice output. > > > > DiffModel new > > leftText: (Point >> #x) sourceCode; > > rightText: (Point >> #y) sourceCode; > > contextClass: Point; > > openWithSpec. > > > > <Screen Shot 2015-06-17 at 18.33.22.png> > > > > But what happens in the case that the class does not exist in the system? > > > > If one doesn't set any context to the styler, then the string will be > shown all in black, which is not nice. A partial solution could be to set > Object as a context, then the styler will color the code, but instance > variables are in red: > > > > DiffModel new > > leftText: (Point >> #x) sourceCode; > > rightText: (Point >> #y) sourceCode; > > contextClass: Object; > > openWithSpec. > > > > <Screen Shot 2015-06-17 at 18.33.27.png> > > > > Which is also not nice. In my opinion, there should be a styler that > just colors the code following the syntax, without checking if the > variables or classes are present in the system. It would be an > environment-independent styler. > > > > What do you recommend to implement this? I guess it should be easy to > subclass SHTextStylerST80 and override some methods to do not check > anything in the environment. > > > > What's your opinion? > > > > Right now we have the problem that we have 3 Stylersâ¦ (for the old text > model one based on Shout, one AST, and one for TxText based on the AST. Ah, > and Rubric subclasses the > shout one, too. Which means 4. > > One question is: could a styler fall back onto a being environment > independent as soon as the environment is not set? > Yes. With a bit of ternary logic which says that symbols are in three states: defined, undefined and unknown. First two require a context; third one applies if you don't have a context. Thierry

June 22, 2015