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

[Peter Uhnák]

> 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 
wrote:

> 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 August 2017 at 20:11, Dimitris Chloupis 
> wrote:
>
>> +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 produced as well as pdf
>>> - the pdf is stored on bintray
>>> - the release versions are stored on the github repo (I should verify)
>>>
>>> So now you can just do a PR and you get a super nice PDF.
>>>
>>> Have a look at Glorp or Voyage for example
>>>
>>> - https://github.com/SquareBracketAssociates/Booklet-Glorp
>>> - https://github.com/SquareBracketAssociates/Booklet-Voyage
>>>
>>> You can access the bintray files from the squarebracketassociates
>>> lovely binTray account :)
>>>
>>> https://bintray.com/squarebracketassociates/wip/download_
>>> file?file_path=voyage-wip.pdf
>>>
>>>
>>> I'm writing a doc of the process so that other people can do it for
>>> their private projects.
>>>
>>>
>>> Stef
>>>
>>>
>
>
> --
> Damien Pollet
> type less, do more [ | ] http://people.untyped.org/damien.pollet
>

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

[Damien Pollet]

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 August 2017 at 20:11, Dimitris Chloupis  wrote:

> +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 produced as well as pdf
>> - the pdf is stored on bintray
>> - the release versions are stored on the github repo (I should verify)
>>
>> So now you can just do a PR and you get a super nice PDF.
>>
>> Have a look at Glorp or Voyage for example
>>
>> - https://github.com/SquareBracketAssociates/Booklet-Glorp
>> - https://github.com/SquareBracketAssociates/Booklet-Voyage
>>
>> You can access the bintray files from the squarebracketassociates
>> lovely binTray account :)
>>
>> https://bintray.com/squarebracketassociates/wip/download_file?file_path=
>> voyage-wip.pdf
>>
>>
>> I'm writing a doc of the process so that other people can do it for
>> their private projects.
>>
>>
>> Stef
>>
>>


-- 
Damien Pollet
type less, do more [ | ] http://people.untyped.org/damien.pollet

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

[Dimitris Chloupis]

+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 produced as well as pdf
> - the pdf is stored on bintray
> - the release versions are stored on the github repo (I should verify)
>
> So now you can just do a PR and you get a super nice PDF.
>
> Have a look at Glorp or Voyage for example
>
> - https://github.com/SquareBracketAssociates/Booklet-Glorp
> - https://github.com/SquareBracketAssociates/Booklet-Voyage
>
> You can access the bintray files from the squarebracketassociates
> lovely binTray account :)
>
>
> https://bintray.com/squarebracketassociates/wip/download_file?file_path=voyage-wip.pdf
>
>
> I'm writing a doc of the process so that other people can do it for
> their private projects.
>
>
> Stef
>
>

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

[Serge Stinckwich]

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 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 should verify)
>
> So now you can just do a PR and you get a super nice PDF.
>
> Have a look at Glorp or Voyage for example
>
> - https://github.com/SquareBracketAssociates/Booklet-Glorp
> - https://github.com/SquareBracketAssociates/Booklet-Voyage
>
> You can access the bintray files from the squarebracketassociates
> lovely binTray account :)
>
> https://bintray.com/squarebracketassociates/wip/download_file?file_path=
> voyage-wip.pdf
>
>
> I'm writing a doc of the process so that other people can do it for
> their private projects.
>
>
> Stef
>
>


-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

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

[Serge Stinckwich]

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
>  which brings the live
> programming environment into IoT domain.
>
> It includes:
>
>- development tools to lively program, explore and debug remote boards
>(based on TelePharo )
>- board modeling library which simplifies board configuration
>   - Raspberry driven by WiringPi library
>   - Arduino driven by Firmata, soon
>   - Beaglebone, soon
>
> Follow github page  and videos
> to get a feeling of this project:
> - https://youtu.be/ezfjditHjq4
> - https://youtu.be/5i0tsgFtlOg
> - https://youtu.be/0H9of7PQet0
>
> Now PharoThings is in beta stage together with documentation and videos. I
> would like any feedback on how to improve them.
>
> If you are going to Esug conference you can see PharoThings in live at
> awards competition.
>
> Best regards,
> Denis
>



-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] ZnEasy question

[Sven Van Caekenberghe]

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 path segments (as would happen when 
2 consecutive slash occur in it) - simplify some of the code

Modify #testEncodedSlash and #testParsingEmpty in ZnUrlTests to follow the new 
behavior
===
Name: Zinc-Resource-Meta-Tests-SvenVanCaekenberghe.38
Author: SvenVanCaekenberghe
Time: 25 August 2017, 4:51:43.080273 pm
UUID: 4116fcd1-f613-0d00-b8a3-a70905cf217b
Ancestors: Zinc-Resource-Meta-Tests-SvenVanCaekenberghe.37

Adapt ZnUrl>>#parsePath: to allow for empty path segments (as would happen when 
2 consecutive slash occur in it) - simplify some of the code

Modify #testEncodedSlash and #testParsingEmpty in ZnUrlTests to follow the new 
behavior
===

Empty path segments are allowed and your example will work.

Since it returns JSON, I would suggest doing

ZnClient new 
  accept: ZnMimeType applicationJson;
  enforceAcceptContentType: true;
  contentReader: [ :entity | STONJSON fromString: entity contents ]; 
  get: 
'https://archive.softwareheritage.org/api/1/origin/git/url/https://github.com/hylang/hy'.

> On 17 Aug 2017, at 18:51, Sven Van Caekenberghe  wrote:
> 
> Hi Milton,
> 
>> On 5 Aug 2017, at 03:15, milton mamani  wrote:
>> 
>> Hi to all
>> 
>> I want to use the next instruction in my code
>> 
>> response := ZnEasy get: 
>> 'https://archive.softwareheritage.org/api/1/origin/git/url/https://github.com/hylang/hy'.
>> response.
>> 
>> The previous code works from command line or in a webbrowser, but I does not 
>> work with ZnEasy
>> Because it takes the previous link as:
>> a ZnRequest(GET /api/1/origin/git/url/https:/github.com/hylang/hy)
>> 
>> Could you please tell me what can I do for this situation?
>> 
>> Cheers,
>> Milton
> 
> ZnUrl has indeed a problem parsing this URL. It skips empty path segments, 
> we'll have to create an issue for that and we should try to fix it, 
> maintaining current behaviour. The parser is hand written and has evolved a 
> bit over the years, so it is a bit brittle. Seaside's WAUrl seems to have the 
> same problem. It is funny that this only now comes up. Thanks for reporting 
> it.
> 
> Here is a workaround, by manually creating a ZnUrl object from its elementary 
> components.
> 
> ZnUrl new scheme: #https; host: 'archive.softwareheritage.org'; 
> addPathSegments: #('api' '1' 'origin' 'git' 'url' 'https:' '' 'github.com' 
> 'hylang' 'hy'); yourself.
> 
> You can use this as follows.
> 
> ZnUrl new scheme: #https; host: 'archive.softwareheritage.org'; 
> addPathSegments: #('api' '1' 'origin' 'git' 'url' 'https:' '' 'github.com' 
> 'hylang' 'hy'); retrieveContents.
> 
> ZnEasy get: (ZnUrl new scheme: #https; host: 'archive.softwareheritage.org'; 
> addPathSegments: #('api' '1' 'origin' 'git' 'url' 'https:' '' 'github.com' 
> 'hylang' 'hy'); yourself).
> 
> Regards,
> 
> Sven
> 

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

[Thierry Goubier]

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 includes:
>
>- development tools to lively program, explore and debug remote boards
>(based on TelePharo )
>- board modeling library which simplifies board configuration
>   - Raspberry driven by WiringPi library
>   - Arduino driven by Firmata, soon
>   - Beaglebone, soon
>
> Follow github page  and videos
> to get a feeling of this project:
> - https://youtu.be/ezfjditHjq4
> - https://youtu.be/5i0tsgFtlOg
> - https://youtu.be/0H9of7PQet0
>
> Now PharoThings is in beta stage together with documentation and videos. I
> would like any feedback on how to improve them.
>
> If you are going to Esug conference you can see PharoThings in live at
> awards competition.
>
> Best regards,
> Denis
>

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

[Stephane Ducasse]

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 tools to lively program, explore and debug remote boards (based
> on TelePharo)
> board modeling library which simplifies board configuration
>
> Raspberry driven by WiringPi library
> Arduino driven by Firmata, soon
> Beaglebone, soon
>
> Follow github page and videos to get a feeling of this project:
> - https://youtu.be/ezfjditHjq4
> - https://youtu.be/5i0tsgFtlOg
> - https://youtu.be/0H9of7PQet0
>
> Now PharoThings is in beta stage together with documentation and videos. I
> would like any feedback on how to improve them.
>
> If you are going to Esug conference you can see PharoThings in live at
> awards competition.
>
> Best regards,
> Denis

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

[Stephane Ducasse]

 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 should verify)

So now you can just do a PR and you get a super nice PDF.

Have a look at Glorp or Voyage for example

- https://github.com/SquareBracketAssociates/Booklet-Glorp
- https://github.com/SquareBracketAssociates/Booklet-Voyage

You can access the bintray files from the squarebracketassociates
lovely binTray account :)

https://bintray.com/squarebracketassociates/wip/download_file?file_path=voyage-wip.pdf


I'm writing a doc of the process so that other people can do it for
their private projects.


Stef

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

[Denis Kudriashov]

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 )
   - board modeling library which simplifies board configuration
  - Raspberry driven by WiringPi library
  - Arduino driven by Firmata, soon
  - Beaglebone, soon

Follow github page  and videos to
get a feeling of this project:
- https://youtu.be/ezfjditHjq4
- https://youtu.be/5i0tsgFtlOg
- https://youtu.be/0H9of7PQet0

Now PharoThings is in beta stage together with documentation and videos. I
would like any feedback on how to improve them.

If you are going to Esug conference you can see PharoThings in live at
awards competition.

Best regards,
Denis

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

[Marcus Denker]

> 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 energy is spent trying to
>> backport/solve reported issues.
>> 
> 
> Yes, you are right… the strange thing is that the problem was introduced very 
> late and
> we do not yet really understand what it is…
> 
> (And I kind of suppressed my knowledge about it… just rememberd it when I 
> tried to 
> check a back port and it failed).
> 

I added an issue tracker entry. The very odd thing is that this test does *not* 
fail when you run it, it does
not fail when run as part of the image tests when doing an update, either.

https://pharo.fogbugz.com/f/cases/20339/Pharo6-test-runs-for-CI-fail-with-strange-error-in-ClassRenameFixTest-testRenameClassUsingClass
 


Marcus

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

[Marcus Denker]

> 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… the strange thing is that the problem was introduced very 
late and
we do not yet really understand what it is…

(And I kind of suppressed my knowledge about it… just rememberd it when I tried 
to 
check a back port and it failed).

Marcus

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

[Henrik Sperre Johansen]

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: 
http://forum.world.st/Pharo6-Issue-Tracker-Help-Needed-issues-tagged-Pharo6-tp4964056p4964077.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

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

[Henrik Sperre Johansen]

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
https://pharo.fogbugz.com/f/cases/20119/basicIdentityHash-and-only-basicIdentityHash-MUST-be-defined-in-every-immediate-class

(I imagine the same fix would be beneficial on Pharo7 as well, btw)

Cheers,
Henry



--
View this message in context: 
http://forum.world.st/Pharo6-Issue-Tracker-Help-Needed-issues-tagged-Pharo6-tp4964056p4964076.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

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

[Marcus Denker]

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

[Marcus Denker]

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: We can not fix 
everything
or even back port everything… we need to prioritise.

It would help if people could “help deciding” which issues do not need the 
Pharo6 milestone.

Marcus

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

[Stephane Ducasse]

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.

https://github.com/SquareBracketAssociates/PharoMooc/tree/master/Subtitles


Stef