September 2019 - Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #776: 2174-withoutDuplicates

by ci-pharo-ci-jenkins2＠inria.fr

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

Sept. 24, 2019

Re: [Pharo-dev] Fuel Not Serializing Stateful Traits

by Marcus Denker

we coud back port the fix... > On 24 Sep 2019, at 08:38, Max Leske <maxleske(a)gmail.com> wrote: > > Hi, > > As I wrote to Sean on Discord, Marcus fixed that bug during ESUG. I realize now, however, that it is only fixed in Pharo 8. I would need to write a patch for Fuel to make it work in Pharo 7. > > Alternatively, you could include the patch in your code, then Fuel should work. > > > Cheers, > Max > > > On 24 Sep 2019, at 7:59, Alistair Grant wrote: > >> Hi Sean, >> >> >> On Mon, 23 Sep 2019 at 23:37, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >>> >>> Sean P. DeNigris wrote >>>> I see commit 1dd... back in March 2018 says it should work >>> >>> Investigating a bit further, maybe the problem is in Pharo, because another >>> test in Pharo 8 didn't show the issue. instanceVariableNamesDo: doesn't seem >>> to have changed, so I guess it's deeper. Any ideas? Otherwise I'll have to >>> rollback my stateful trait usage until Pharo 8! >> >> This might provide a bit more info: >> https://github.com/pharo-project/pharo/issues/3546 >> >> Cheers, >> Alistair >

Sept. 24, 2019

Pumping FFI documentation [WAS] FFI beginner question

by Guillermo Polito

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

Sept. 24, 2019

Re: [Pharo-dev] Difficulty to use Iceberg

by Stephan Eggermont

Jan Vrany <jan.vrany(a)fit.cvut.cz> wrote: > Hi, > > I'm experiencing difficulties (code loss, even) when trying to > commit code using Iceberg. > > I have a project with consist of some Pharo code and some > C++ code. Both parts kind of depend on each other. >... > Any suggestions? https://github.com/jecisc/GitBridge might be of help here Stephan

Sept. 24, 2019

Re: [Pharo-dev] Fuel Not Serializing Stateful Traits

by Max Leske

Hi, As I wrote to Sean on Discord, Marcus fixed that bug during ESUG. I realize now, however, that it is only fixed in Pharo 8. I would need to write a patch for Fuel to make it work in Pharo 7. Alternatively, you could include the patch in your code, then Fuel should work. Cheers, Max On 24 Sep 2019, at 7:59, Alistair Grant wrote: > Hi Sean, > > > On Mon, 23 Sep 2019 at 23:37, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: >> >> Sean P. DeNigris wrote >>> I see commit 1dd... back in March 2018 says it should work >> >> Investigating a bit further, maybe the problem is in Pharo, because >> another >> test in Pharo 8 didn't show the issue. instanceVariableNamesDo: >> doesn't seem >> to have changed, so I guess it's deeper. Any ideas? Otherwise I'll >> have to >> rollback my stateful trait usage until Pharo 8! > > This might provide a bit more info: > https://github.com/pharo-project/pharo/issues/3546 > > Cheers, > Alistair

Sept. 24, 2019

[Pharo 8.0] Build #775: 4686-code-completion-not-working-properly-on-inspectors

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #775 was: FAILURE. The Pull Request #4689 was integrated: "4686-code-completion-not-working-properly-on-inspectors" Pull request url: https://github.com/pharo-project/pharo/pull/4689 Issue Url: https://github.com/pharo-project/pharo/issues/4686 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 24, 2019

Re: [Pharo-dev] Fuel Not Serializing Stateful Traits

by Alistair Grant

Hi Sean, On Mon, 23 Sep 2019 at 23:37, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Sean P. DeNigris wrote > > I see commit 1dd... back in March 2018 says it should work > > Investigating a bit further, maybe the problem is in Pharo, because another > test in Pharo 8 didn't show the issue. instanceVariableNamesDo: doesn't seem > to have changed, so I guess it's deeper. Any ideas? Otherwise I'll have to > rollback my stateful trait usage until Pharo 8! This might provide a bit more info: https://github.com/pharo-project/pharo/issues/3546 Cheers, Alistair

Sept. 24, 2019

[Pharo 8.0] Build #774: 4654-Add-comment-to-RBProgramNodeisFaulty

by ci-pharo-ci-jenkins2＠inria.fr

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

Sept. 24, 2019

Re: [Pharo-dev] Fuel Not Serializing Stateful Traits

by Sean P. DeNigris

Sean P. DeNigris wrote > I see commit 1dd... back in March 2018 says it should work Investigating a bit further, maybe the problem is in Pharo, because another test in Pharo 8 didn't show the issue. instanceVariableNamesDo: doesn't seem to have changed, so I guess it's deeper. Any ideas? Otherwise I'll have to rollback my stateful trait usage until Pharo 8! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 23, 2019

Re: [Pharo-dev] Difficulty to use Iceberg

by Sean P. DeNigris

Jan Vrany wrote > What is the correct workflow to end up with: > --- A --- B --- C --- D --- E Not in front of an image, but IIU/RC if youâre seeing âdetachedâ, click repair, then the option where you use the repository version (which I think I the last one), then - if the outside changes didnât effect the Smalltalk code - from the drop down choose âdonât check anything outâ which is confusing but means that it wonât try to reload any packages in Pharo. The result of those steps should be that Pharo recognizes the latest commit. Let me know whether it works and Iâll be more exact when I get in front of a computer ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 23, 2019