Re: [Pharo-dev] [Ann][Pillar] Travis -> Bintray for PDFs

> A problem I anticipate is that since we only keep the latest build, how did you manage that? :-o When I was using bintray we had trouble that we could only store every commit; so I guess I am interested to see what your process is. :-) Peter On Fri, Aug 25, 2017 at 9:06 PM, Damien Pollet

Re: [Pharo-dev] [Ann][Pillar] Travis -> Bintray for PDFs

A problem I anticipate is that since we only keep the latest build, the PDF will only match master or any pull request until the next commit/build (I don't like storing stuff for each and every commit). But maybe that could be fixed by naming the PDF according to their originating branch… On 25

Re: [Pharo-dev] [Ann][Pillar] Travis -> Bintray for PDFs

+100 :) On Fri, Aug 25, 2017 at 5:45 PM Stephane Ducasse wrote: > Hi > > with Damien Pollet, we went over all the booklets and some of the > Pharo books currently written in Pillar and made sure that each time > you commit > > - a travis job is run > - latex is

Re: [Pharo-dev] [Ann][Pillar] Travis -> Bintray for PDFs

This is great Stef ! I'm waiting for the documentation to update all my projects with the new process. On Fri, Aug 25, 2017 at 4:42 PM, Stephane Ducasse wrote: > Hi > > with Damien Pollet, we went over all the booklets and some of the > Pharo books currently written

Re: [Pharo-dev] [Ann] PharoThings a live programming IoT platform based on Pharo

Really impressive work ! Definitively interested to have a look for projects I have in my research lab in Cameroon. On Fri, Aug 25, 2017 at 4:25 PM, Denis Kudriashov wrote: > Hi. > > I am glad to announce the project PharoThings >

Re: [Pharo-dev] ZnEasy question

With the following commits === Name: Zinc-Resource-Meta-Core-SvenVanCaekenberghe.63 Author: SvenVanCaekenberghe Time: 25 August 2017, 4:51:26.632889 pm UUID: b81e01d1-f613-0d00-b8a2-b72f05cf217b Ancestors: Zinc-Resource-Meta-Core-SvenVanCaekenberghe.62 Adapt ZnUrl>>#parsePath: to allow for empty

Re: [Pharo-dev] [Ann] PharoThings a live programming IoT platform based on Pharo

This is very interesting. Thanks Denis, Thierry 2017-08-25 16:25 GMT+02:00 Denis Kudriashov : > Hi. > > I am glad to announce the project PharoThings > which brings the live > programming environment into IoT domain. > > It

Re: [Pharo-dev] [Ann] PharoThings a live programming IoT platform based on Pharo

Nice videos :) So many exciting things moving in Pharo On Fri, Aug 25, 2017 at 4:25 PM, Denis Kudriashov wrote: > Hi. > > I am glad to announce the project PharoThings which brings the live > programming environment into IoT domain. > > It includes: > > development

[Pharo-dev] [Ann][Pillar] Travis -> Bintray for PDFs

Hi with Damien Pollet, we went over all the booklets and some of the Pharo books currently written in Pillar and made sure that each time you commit - a travis job is run - latex is produced as well as pdf - the pdf is stored on bintray - the release versions are stored on the github repo (I

[Pharo-dev] [Ann] PharoThings a live programming IoT platform based on Pharo

Hi. I am glad to announce the project PharoThings which brings the live programming environment into IoT domain. It includes: - development tools to lively program, explore and debug remote boards (based on TelePharo

Re: [Pharo-dev] [Pharo6] [Issue Tracker] Help Needed: issues tagged Pharo6

> On 25 Aug 2017, at 15:50, Marcus Denker wrote: > > >> On 25 Aug 2017, at 15:47, Henrik Sperre Johansen >> wrote: >> >> Less crassly, what I meant to say, was; it'd be really nice if the >> integration process was fixed before too much

Re: [Pharo-dev] [Pharo6] [Issue Tracker] Help Needed: issues tagged Pharo6

> On 25 Aug 2017, at 15:47, Henrik Sperre Johansen > wrote: > > Less crassly, what I meant to say, was; it'd be really nice if the > integration process was fixed before too much energy is spent trying to > backport/solve reported issues. > Yes, you are right…

Re: [Pharo-dev] [Pharo6] [Issue Tracker] Help Needed: issues tagged Pharo6

Less crassly, what I meant to say, was; it'd be really nice if the integration process was fixed before too much energy is spent trying to backport/solve reported issues. Cheers, Henry -- View this message in context:

Re: [Pharo-dev] [Pharo6] [Issue Tracker] Help Needed: issues tagged Pharo6

What's the point? Even if an issue has slice attached, is marked as Fixed, and has no failing tests in a local image, it'll be thrown out by a broken monkey / integration process, ref. for example

[Pharo-dev] [ Pharo 70 ] Build 59 PR 201

New build with one trivial fix (which will be back ported to Pharo6, too): [ Pharo 70 ] Build 59 PR 201 -DarkTheme-disabledTextColor-is-too-close-of-textColor https://github.com/pharo-project/pharo/pull/201 https://pharo.fogbugz.com/f/cases/20248

[Pharo-dev] [Pharo6] [Issue Tracker] Help Needed: issues tagged Pharo6

Hi, We have 40 issues that are tagged for Pharo6: https://pharo.fogbugz.com/f/filters/1192/6-0-All We should move as many of those to “Later”, so that we can focus on important fixes and back ports… sadly here we need to be realistic:

[Pharo-dev] Call for Spanish/ Portuguese and more subtitles for the PharoMooc

Hi guys The Pharo is a wonderful vehicule to promote Pharo and we need your help to translate the subtitles to different languages. This year we will have english voices paid by Inria (thanks) but we cannot do everything and we need your help.