- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #791: 4745-OSSDL2-is-ignoring-characters-entered-with-AltGr
by ci-pharo-ci-jenkins2＠inria.fr Sept. 27, 2019

Sept. 27, 2019

There is a new Pharo build available! The status of the build #791 was: FAILURE. The Pull Request #4747 was integrated: "4745-OSSDL2-is-ignoring-characters-entered-with-AltGr" Pull request url: https://github.com/pharo-project/pharo/pull/4747 Issue Url: https://github.com/pharo-project/pharo/issues/4745 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Pumping FFI documentation [WAS] FFI beginner question
by Guillermo Polito Sept. 26, 2019

Sept. 26, 2019

Hi Ted, I split this in a separate thread to avoid noise :) > El 23 sept 2019, a las 23:14, Brainstorms <wild.ideas(a)gmail.com> escribiÃ³: > > Guillermo, > > I'm interested in helping, but at this point, I think I'd be most helpful > working at improving documentation (mainly editing) rather than working on > Pharo code itself. (I'd like to work toward that, though.) Iâve been doing a pass on the structure, and I was thinking on a rough structure as follows: 1) Intro to FFI (callouts, function and library lookup, intro to value marshalling) 2) Marshalling (sending arguments, literal arguments, more on marshalling, basic C types: ints, floats, pointers and how they are transformed to pharo objects and vice-versaâ¦) 3) Complex types: strings, unions, arrays, opaque types 4) Derived types on the Pharo side: How to design nice classes with all this 5) Callbacks 6) Memory management I did already a pass on 1), and I got blocked in 2), though I want to release a version of it this week. If youâre up for it, there are several things we can do: - review the english :) - give feedback on what is missing, what is not understandable, what can be explained better - testing the examples? > > I'm still a newbie with Pharo, but I am a good writer/editor. And I expect > that working with Pharo documentation would be another means of increasing > my knowledge of the Pharo ecosystem -- so that's additional incentive for > me. Cool :) > I gather that the PDF books are written using Pillar, which I know nothing > about. Are there resources & guides for this tool/format that would help me > learn how to make & edit these kinds of documents? Pillar is a markup syntax (from Pierâs CMS, if you know it). https://github.com/pillar-markup/pillar <https://github.com/pillar-markup/pillar> Pillar comes with a document model, parser and generators to html, pdf (through latex), and othersâ¦ In Pillarâs readme there are the installation instructions + usage. If you check the travis file in the ffi booklet repository https://github.com/SquareBracketAssociates/Booklet-uFFI/blob/version2/.trav… <https://github.com/SquareBracketAssociates/Booklet-uFFI/blob/version2/.trav…> Youâll see it is built with pillar 7.4.1. In other words # install pillar $ git clone https://github.com/pillar-markup/pillar.git -b v7.4.1 $ cd pillar && ./scripts/build.sh && cd .. # go into the booklet repository and build the pdf $ ./pillar/build/pillar build pdf Although youâll need a mostly up-to-date latex version (latexmk required, plus several other packages, check Pillarâs readme) > Also, I've never contributed to an open source project; Pharo seems to be a > good place to start doing so. I see that most of the documentation, web > pages, booklets, etc. are in English so there's the advantage that English > is my first language (and I actually paid attention in school :^). I'm > also aware, from experience, that Documentation is rarely the first choice > for developers to apply their time & enthusiasmâ¦ And itâs super important nevertheless ^^. Guille

5 17

[Pharo 8.0] Build #790: Smalltalk at removal
by ci-pharo-ci-jenkins2＠inria.fr Sept. 26, 2019

Sept. 26, 2019

There is a new Pharo build available! The status of the build #790 was: FAILURE. The Pull Request #4721 was integrated: "Smalltalk at removal" Pull request url: https://github.com/pharo-project/pharo/pull/4721 Issue Url: https://github.com/pharo-project/pharo/issues/Smalltalk_at_removal Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #789: 4735-Implement-pcRange-on-Context-using-sourceNodeExecuted
by ci-pharo-ci-jenkins2＠inria.fr Sept. 26, 2019

Sept. 26, 2019

There is a new Pharo build available! The status of the build #789 was: SUCCESS. The Pull Request #4740 was integrated: "4735-Implement-pcRange-on-Context-using-sourceNodeExecuted" Pull request url: https://github.com/pharo-project/pharo/pull/4740 Issue Url: https://github.com/pharo-project/pharo/issues/4735 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #788: 4736-MethodMapExamples-should-not-use-MethodMap-directly
by ci-pharo-ci-jenkins2＠inria.fr Sept. 26, 2019

Sept. 26, 2019

There is a new Pharo build available! The status of the build #788 was: FAILURE. The Pull Request #4738 was integrated: "4736-MethodMapExamples-should-not-use-MethodMap-directly" Pull request url: https://github.com/pharo-project/pharo/pull/4738 Issue Url: https://github.com/pharo-project/pharo/issues/4736 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] [Pharo-users] [ANN] New Windows VM - Fixes 1903 error
by Serge Stinckwich Sept. 26, 2019

Sept. 26, 2019

Yes this what I want to know. How to know there is an update, without downloading the update ? On Fri, Sep 20, 2019 at 10:26 PM Richard O'Keefe <raoknz(a)gmail.com> wrote: > I understood Serge Stinkwich's question to be "at any given time, how do > we know whether > the VM we have is the latest one for our platform?" Certainly that was > what I wanted to > know. When I use the Launcher, I don't see any way to ask "is this VM > I've selected up- > to-date". If I click on Update, the Launcher starts an HTTP request or > not, and after > enough time to make me think it is downloading quite a lot, just stops. > If I repeat the > action, the whole process repeats. This makes me think that the Launcher > is not looking > to see whether there is a new version, just downloading whatever is latest > at the other > end. > > It would be nice to have an "is this image/VM up todate?" button > somewhere, that just > gets a few bytes of version number + checksum. > > On Sat, 21 Sep 2019 at 01:40, Pablo Tesone <tesonep(a)gmail.com> wrote: > >> Hi Serge, >> >> in any Pharo Image (7 or 8) in the Option System / System Reporter >> >> There should be something like: >> >> >> Cheers, >> >> Pablo >> >> >> On 20/09/2019 13:24, Serge Stinckwich wrote: >> >> >> >> On Fri, Sep 20, 2019 at 11:07 AM tesonep(a)gmail.com <tesonep(a)gmail.com> >> wrote: >> >>> Hello, >>> a new stable VM has been deployed. This VM uses a new version of >>> libSSH allowing us to work in the latest Windows version. >>> >>> It can be directly updated using Pharo Launcher or downloaded using >>> ZeroConf scripts. >>> >>> To update from Pharo Launcher you have to access to the VM Manager >>> window. >>> Just click on the marked button and then in "Update" >>> [image: updateVM.png] >>> >>> >> This great Pablo, I didn't know that there is a VM manager. >> I want to save my bandwidth. >> How do we know, we have the last VM ? >> >> >> -- >> Serge Stinckwic >> h >> >> Int. Research Unit >> on Modelling/Simulation of Complex Systems (UMMISCO) >> Sorbonne University >> (SU) >> French National Research Institute for Sustainable Development (IRD) >> U >> niversity of YaoundÃ© I, Cameroon >> "Programs must be written for people to read, and only incidentally for >> machines to execute." >> https://twitter.com/SergeStinckwich >> >> -- Serge Stinckwic âhâ Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) âSorbonne University (SU) French National Research Institute for Sustainable Development (IRD)â U âniversity of YaoundÃ© Iâ, Cameroon "Programs must be written for people to read, and only incidentally for machines to execute." https://twitter.com/SergeStinckwich â

1 0

[Pharo 8.0] Build #787: 4718-implement-ContextsourceNode-in-terms-of-sourceNodeExecuted
by ci-pharo-ci-jenkins2＠inria.fr Sept. 26, 2019

Sept. 26, 2019

There is a new Pharo build available! The status of the build #787 was: SUCCESS. The Pull Request #4729 was integrated: "4718-implement-ContextsourceNode-in-terms-of-sourceNodeExecuted" Pull request url: https://github.com/pharo-project/pharo/pull/4729 Issue Url: https://github.com/pharo-project/pharo/issues/4718 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Pharo TechTalk Sept 26
by Marcus Denker Sept. 26, 2019

Sept. 26, 2019

A regular chat about Pharo. Happens on Discord. The Tech talks are open to both members and non-members! Topic: Spec2 and GTK NOTE: one week later then originally planned! https://association.pharo.org/event-3419544

2 2

[Pharo 8.0] Build #786: 4670-Deprecation-transfrom-make-sure-the-fallback-is-signal
by ci-pharo-ci-jenkins2＠inria.fr Sept. 26, 2019

Sept. 26, 2019

There is a new Pharo build available! The status of the build #786 was: FAILURE. The Pull Request #4723 was integrated: "4670-Deprecation-transfrom-make-sure-the-fallback-is-signal" Pull request url: https://github.com/pharo-project/pharo/pull/4723 Issue Url: https://github.com/pharo-project/pharo/issues/4670 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #785: OpalSemanticCleanup
by ci-pharo-ci-jenkins2＠inria.fr Sept. 26, 2019

Sept. 26, 2019

There is a new Pharo build available! The status of the build #785 was: FAILURE. The Pull Request #4731 was integrated: "OpalSemanticCleanup" Pull request url: https://github.com/pharo-project/pharo/pull/4731 Issue Url: https://github.com/pharo-project/pharo/issues/OpalSemanticCleanup Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0