Re: [Pharo-dev] Pharo booklet collection

2017-05-23 Thread Tim Mackinnon
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 wrote: > > Check the travis configuration file. It has the docker invocation that

Re: [Pharo-dev] Pharo booklet collection

2017-05-23 Thread Damien Pollet
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 You can also build without docker but that requires an up-to-date TeXlive 2016 (unfortunately

Re: [Pharo-dev] 60494 Red-pane-of-death when sources file missing

2017-05-23 Thread Eliot Miranda
Hi Ben, On May 21, 2017, at 9:01 AM, Ben Coman wrote: We must be getting close to Pharo 6 Release. Due to missing PharoV60.soruces file, image 60494 get a red-pane-of-death in class pane. Even though the release would bypass this by including the file, we should be more

Re: [Pharo-dev] FileTree/Iceberg and SSDs, change the file format

2017-05-23 Thread Jan Vrany
Hi, > > Is it possible to build a file responder right into Pharo and > > expose packages through WebDAV or FUSE or sshfs service? Then the > > contents can go directly from RAM (pharo) to RAM (repo server or > > git) without going through slow disk filesystem. > > Yes it's possible and really

Re: [Pharo-dev] Class syntax brainstorming

2017-05-23 Thread Luc Fabresse
2017-05-22 16:26 GMT+02:00 Mariano Martinez Peck : > Honestly, I do not like that much having a more declarative (less > Smalltalksish) definition. In fact, one of the things I was always proud of > showing to Smalltalk newcomers, that when they created a class, all they >

Re: [Pharo-dev] Class syntax brainstorming

2017-05-23 Thread Luc Fabresse
2017-05-22 15:06 GMT+02:00 Milan Vavra via Pharo-dev < pharo-dev@lists.pharo.org>: > > > -- Message transféré -- > From: Milan Vavra > To: pharo-dev@lists.pharo.org > Cc: > Bcc: > Date: Mon, 22 May 2017 06:06:26 -0700 (PDT) > Subject: Re: Class syntax

[Pharo-dev] [pharo-project/pharo-core]

2017-05-23 Thread GitHub
Branch: refs/tags/60497 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] ed847b: 60497

2017-05-23 Thread GitHub
Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: ed847b82140bc72ef6cf1191fdd1c3e483651c85 https://github.com/pharo-project/pharo-core/commit/ed847b82140bc72ef6cf1191fdd1c3e483651c85 Author: Jenkins Build Server Date:

Re: [Pharo-dev] FileTree/Iceberg and SSDs, change the file format

2017-05-23 Thread Dale Henrichs
Stephan, Out of curiosity. Why are you copying the git repo? In my normal usage, I clone a git repository on disk and then share that repository amongst all of the image/stones on that machine ... The upshot is that I almost never copy the repo. I use push to publish changes to common git

Re: [Pharo-dev] FileTree/Iceberg and SSDs, change the file format

2017-05-23 Thread Ben Coman
On Tue, May 23, 2017 at 1:33 PM, Stephan Eggermont wrote: > On 22/05/17 04:38, Ben Coman wrote: > >> On Sun, May 21, 2017 at 11:25 PM, Stephan Eggermont >> > > wrote: >> So this was copying files at the OS level? Which OS? >> > >

[Pharo-dev] [pharo-project/pharo-core]

2017-05-23 Thread GitHub
Branch: refs/tags/60496 Home: https://github.com/pharo-project/pharo-core