Thanks Damien - installing docker now, and I’ll see how I get on (I’m still 
working through the reddit booklet - which is proving quite fun)

Tim

> On 23 May 2017, at 22:11, Damien Pollet <[email protected]> wrote:
> 
> Check the travis configuration file. It has the docker invocation that will 
> get the correct image and build the booklet.
> https://github.com/SquareBracketAssociates/Booklet-Reddit/blob/master/.travis.yml
>  
> <https://github.com/SquareBracketAssociates/Booklet-Reddit/blob/master/.travis.yml>
> 
> You can also build without docker but that requires an up-to-date TeXlive 
> 2016 (unfortunately we rely on some fixes that are not in the installation 
> iso, so you'd have to either use the net installer or do `tlmgr update --self 
> --all` after installing the iso snapshot)
> 
> On 23 May 2017 at 15:25, Tim Mackinnon <[email protected] 
> <mailto:[email protected]>> wrote:
> Hi - so I forked a repo (the Reddit one), and am reading through it to check 
> for typos (I’ve see a few). Obviously I can correct those, but how do I 
> actually preview my changes to ensure I haven’t screwed it all up?
> 
> I’m guessing I need to install Docker and pull down a specific image - which 
> I can then use to generate the output to test it? Or, is there an ST image 
> that I can run on this directory?
> 
> As a quick scan of whats in a book repo - it all looks a bit more complicated 
> than I expected - with make files and what look like “inplace templates” (as 
> in format1.format2.format3 etc). Having played around with Metalsmith.io 
> <http://metalsmith.io/> I think its sort of similar, but It seems like there 
> is more to learn somehow? 
> 
> Tim
> 
>> On 6 May 2017, at 11:36, Stephane Ducasse <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> Hi phil
>> 
>> yes I loved this idea. We got burned by that too. 
>> 
>> About pillar. The departure of Damien was not expected and it slows us quite 
>> a bit. 
>> 
>> We (mainly me helped with maxime) are working on 
>> - making the pillar core nicer
>> - less dependencies
>> - and with a small in image renderer :) We had fun with guille 
>> 
>> 
>> - In the pharo 60 version I started to clean the command-line. 
>> - merged many unmerged changes.
>> 
>> But even with all the tests it is not easy....
>> I'm testing in addition with reall 
>> - book production
>> - slides
>> - html
>> 
>> But it takes time and energy. I'm trying to remove the dependencies to 
>> magritte for example. 
>> 
>> Stef
>> 
>> 
>> <Screen Shot 2017-05-06 at 12.33.18.png>
>> 
>> 
>> On Sat, May 6, 2017 at 9:30 AM, [email protected] 
>> <mailto:[email protected]> <[email protected] <mailto:[email protected]>> 
>> wrote:
>> For books, there is the docker-texlive thing from Damien that we
>> looked into yesterday because TexLive was giving some headaches.
>> 
>> https://github.com/philippeback/docker-texlive 
>> <https://github.com/philippeback/docker-texlive>
>> 
>> has my current thing for one to build a container with all
>> prerequisites for TexLive and Pharo installed.
>> 
>> Idea is to clone the book repo on the host and get into an container
>> to build the book.
>> 
>> There is a /work volume that can be mapped onto the host with the
>> docker run's -v command.
>> 
>> Then just use ./download.sh in there to install Pharo and pillar in
>> the container. Do not do that in the host or you'll end up with wrong
>> versions (like my host is CentOS and the container is Ubuntu, even
>> worse with host is macOS or Windows).
>> 
>> Then "make book" should give a book in build/
>> There is a "make wipeout" command that obliterates the build folder
>> for good so you can start clean. No harm done on your files.
>> 
>> Will document more of this but woul dbe nice if someone could check
>> this out too.
>> 
>> There is a script in base/ to build the docker image.
>> 
>> Phil
>> 
>> On Sat, May 6, 2017 at 9:20 AM, Stephane Ducasse
>> <[email protected] <mailto:[email protected]>> wrote:
>> > I fixed it.
>> > The code for the web site in on github.
>> >
>> > Stef
>> >
>> > On Tue, May 2, 2017 at 10:32 PM, Esteban A. Maringolo 
>> > <[email protected] <mailto:[email protected]>>
>> > wrote:
>> >>
>> >> Correct link seems to be
>> >>
>> >>
>> >> http://files.pharo.org/books-pdfs/booklet-Glorp/2017-05-02-Glorp.spiral.pdf
>> >>  
>> >> <http://files.pharo.org/books-pdfs/booklet-Glorp/2017-05-02-Glorp.spiral.pdf>
>> >> Esteban A. Maringolo
>> >>
>> >>
>> >> 2017-05-02 17:28 GMT-03:00 [email protected] <mailto:[email protected]> 
>> >> <[email protected] <mailto:[email protected]>>:
>> >> > link for glorp gives smacc book error
>> >> >
>> >> > On Tue, May 2, 2017 at 10:25 PM, Stephane Ducasse
>> >> > <[email protected] <mailto:[email protected]>>
>> >> > wrote:
>> >> >>
>> >> >> Hi Pharoers
>> >> >>
>> >> >> You are lucky. The "Pharo booklet collection" edited by S. Ducasse is
>> >> >> arriving...
>> >> >>
>> >> >> Are you ready to read nice and focused booklets?
>> >> >>
>> >> >> You can find at http://files.pharo.org/books/ 
>> >> >> <http://files.pharo.org/books/> in beta version:
>> >> >>
>> >> >> Smacc: the Smalltalk Compiler Compiler by J. Brant, T. Goubier, J.
>> >> >> Lecerf
>> >> >> and S. Ducasse.
>> >> >> Glorp: the Object Relational Mapper framework by E. Maringolo, N. Pratt
>> >> >> and R. Withney
>> >> >>
>> >> >> All the book material is hosted on
>> >> >> https://github.com/SquareBracketAssociates 
>> >> >> <https://github.com/SquareBracketAssociates> so you can contribute! Fix
>> >> >> typos
>> >> >> and propose new material.
>> >> >>
>> >> >> We are planning a booklet on Magritte, Reddit in 10 cool classes,
>> >> >> Voyage,
>> >> >> and Mocking with BabyMock and Mocketry, XML (but we need a writer) and
>> >> >> potentially PetitParser.
>> >> >>
>> >> >> If you have material for a tutorial and you would like to be part of
>> >> >> the
>> >> >> Pharo Booklet Collection contact S. Ducasse.
>> >> >>
>> >> >> S. Ducasse
>> >> >
>> >> >
>> >>
>> >
>> 
>> 
> 
> 
> 
> 
> -- 
> Damien Pollet
> type less, do more [ | ] http://people.untyped.org/damien.pollet 
> <http://people.untyped.org/damien.pollet>

Reply via email to