October 2016 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [ann] pillar text editor

by phil＠highoctane.be

Doru, This looks very nice. I used a previous version of this I think. Is performance better? Phil On Sun, Oct 9, 2016 at 11:23 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Pillar now ships with a text editor that also features a syntax > highlighter. > > So, now, if you load the development version of Pillar: > > Gofer new > smalltalkhubUser: 'Pier' project: 'Pillar'; > configuration; > loadDevelopment. > > You will have an extra presentation when inspecting a .pillar file: > > > The new thing here is that the highlighter is based on the Pillar > PetitParser, and it is extensible for highlighting more parts if needed. > The highlighting also can support actions. For example, the picture above > shows the file to the right after clicking on the reference. > > Please take a look and let me know what you think. > > Cheers, > Doru > > > -- > www.tudorgirba.com > www.feenk.com > > "Things happen when they happen, > not when you talk about them happening." > >

Oct. 9, 2016

Re: [Pharo-users] [Moose-dev] [ann] pillar text editor

by Dimitris Chloupis

Your awesomeness burns so bright you will be soon supernova Congrats and thank you On Mon, 10 Oct 2016 at 00:24, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Pillar now ships with a text editor that also features a syntax > highlighter. > > So, now, if you load the development version of Pillar: > > Gofer new > smalltalkhubUser: 'Pier' project: 'Pillar'; > configuration; > loadDevelopment. > > You will have an extra presentation when inspecting a .pillar file: > > > The new thing here is that the highlighter is based on the Pillar > PetitParser, and it is extensible for highlighting more parts if needed. > The highlighting also can support actions. For example, the picture above > shows the file to the right after clicking on the reference. > > Please take a look and let me know what you think. > > Cheers, > Doru > > > -- > www.tudorgirba.com > www.feenk.com > > "Things happen when they happen, > not when you talk about them happening." > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev >

Oct. 9, 2016

[ann] pillar text editor

by Tudor Girba

Hi, Pillar now ships with a text editor that also features a syntax highlighter. So, now, if you load the development version of Pillar: Gofer new smalltalkhubUser: 'Pier' project: 'Pillar'; configuration; loadDevelopment. You will have an extra presentation when inspecting a .pillar file: The new thing here is that the highlighter is based on the Pillar PetitParser, and it is extensible for highlighting more parts if needed. The highlighting also can support actions. For example, the picture above shows the file to the right after clicking on the reference. Please take a look and let me know what you think. Cheers, Doru -- www.tudorgirba.com www.feenk.com "Things happen when they happen, not when you talk about them happening."

Oct. 9, 2016

Re: [Pharo-users] Pillar book makefile or template is broken.

by Damien Pollet

On 9 October 2016 at 21:59, Damien Pollet <damien.pollet+pharo(a)gmail.com> wrote: > Might be that pillar archetype doesn't do a git clone but some kind of > archive extraction wait noâ¦ sbabook is a submodule, so it's like git clone :|

Oct. 9, 2016

Re: [Pharo-users] Pillar book makefile or template is broken.

by Damien Pollet

On 9 October 2016 at 21:52, stepharo <stepharo(a)free.fr> wrote: > I did a clean install. So I imagine that it should break on other machines > too. Might be that pillar archetype doesn't do a git clone but some kind of archive extractionâ¦ I know github and zip files have limitations with that

Oct. 9, 2016

Re: [Pharo-users] Pillar book makefile or template is broken.

by stepharo

Ok thanks! I will try tomorrow. Stef Le 9/10/16 Ã 21:29, Damien Pollet a Ã©crit : > > On 9 October 2016 at 20:03, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > I tried to add a title to a book > > { > "title":"Learning Programming with Pharo", > > > I think I tried with { "metadata": { "title": "bleb" } } in the > book.pillar and that worked. No clue why the one from the conf is not > inherited anymore.

Oct. 9, 2016

Re: [Pharo-users] Pillar book makefile or template is broken.

by stepharo

Le 9/10/16 Ã 21:23, Damien Pollet a Ã©crit : > > On 9 October 2016 at 19:47, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > - chmod +x support/latex/sbabook/gitinfo2.sh > > Now I have no idea where I should add this command. > > > That should be versioned as part of sbabook. On my machine when I > check it out it's executable, and apparently it's harder to make git > ignore file modes than to have it follow them, so I don't know what's > wrong. no idea. I did a clean install. So I imagine that it should break on other machines too.

Oct. 9, 2016

Re: [Pharo-users] Pillar book makefile or template is broken.

by Damien Pollet

On 9 October 2016 at 20:03, stepharo <stepharo(a)free.fr> wrote: > I tried to add a title to a book > > { > "title":"Learning Programming with Pharo", > I think I tried with { "metadata": { "title": "bleb" } } in the book.pillar and that worked. No clue why the one from the conf is not inherited anymore.

Oct. 9, 2016

Re: [Pharo-users] Pillar book makefile or template is broken.

by Damien Pollet

On 9 October 2016 at 19:49, stepharo <stepharo(a)free.fr> wrote: > Are the files in Chapters automatically added to the pillar.conf? > No, they don't have to be in it. The main file includes them. > Does it mean that all the files should be always compiling? > Yes, only the whole-book compilation works for now. Per-chapter compilation works in EnterprisePharo but it's done in the makefile. A proper solution would be to replace all the ${includeFile:foo.pillar}$ directives with something more semantic that does not lose track of which file was included.

Oct. 9, 2016

Re: [Pharo-users] Pillar book makefile or template is broken.

by stepharo

Hi doru > Hi Stef, > > I started from the Pharo image and now we have an editor that is working reasonably well inside Pharo. I will send more details shortly. Cool > This means that I do not have to edit the book somewhere else, and this also means that I can run the generation from inside Pharo, too. Nice. > So, the next step is to trigger the visitors to generate the book from within Pharo without relying on the command line. If we can manage that, I think that we should extract the commandline code into a separated object. I wanted to do that but I decided that I'm not allowed to start something new now. I wanted to generated also all the magritte black magic accessors so that we do not rely on DNU. > my guess is that the command line related logic will become simpler and more debuggable. I wanted to replace some unix commands by some pharo code snippet (because I can debug FileReference) but same reason as above (finish first three tasks before starting a new one). Stef > > Cheers, > Doru > > > >> On Oct 9, 2016, at 8:03 PM, stepharo <stepharo(a)free.fr> wrote: >> >> I tried to add a title to a book >> >> { >> "title":"Learning Programming with Pharo", >> "newLine":#unix, >> "configurations": { >> "LaTeX" : { >> "outputType":#'latex:sbabook', >> "separateOutputFiles":true >> }, >> "HTML" : { >> "outputType":#html, >> "separateOutputFiles":true >> } >> } >> } >> >> did not work :( >> >> { >> "title":"Learning Programming with Pharo" >> } >> >> !!Compilation >> >> ${inputFile:Chapters/Chapter1/chapter1.pillar}$ >> >> !!Edition and Templates >> >> ${inputFile:Chapters/Chapter2/chapter2.pillar}$ >> >> +>figures/pharo.png|width=30+ >> +>figures/rmod.png|width=30+ >> >> did not work :( >> >> No idea how to debug i t sadly. >> >> Stef >> >> >> Le 9/10/16 Ã 19:42, stepharo a Ã©crit : >>> Hi >>> >>> Is there anybody maintaining Pillar? >>> >>> >>> I did >>> >>> wget https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh >>> >>> chmod +x download.sh >>> >>> ./download.sh >>> >>> ./pillar archetype book >>> >>> ogrammingArchetype make pdf >>> git submodule update --init --recursive >>> mkdir -p ./build >>> ln -fs ../support ./build >>> support/latex/sbabook/gitinfo2.sh > build/gitHeadLocal.gin >>> /bin/sh: support/latex/sbabook/gitinfo2.sh: Permission denied >>> make: *** [build/gitHeadLocal.gin] Error 126 >>> >>> >>> I have no idea how to fix it. >>> >>> in the past I removed this git version script because it was going in my way. >>> >>> Stef >>> >>> >>> >> > -- > www.tudorgirba.com > www.feenk.com > > "Problem solving efficiency grows with the abstractness level of problem understanding." > > > > > >

Oct. 9, 2016