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

Re: [Pharo-dev] [Pharo-users] Pumping FFI documentation [WAS] FFI beginner question

by ducasse

> On 25 Sep 2019, at 15:22, Ben Coman <btc(a)openinworld.com> wrote: > > > > On Wed, 25 Sep 2019 at 13:51, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> wrote: > Hi > > Normally each time a PR is integrated in a book, the CI is generating the PDF. > https://github.com/SquareBracketAssociates/Booklet-uFFI/releases <https://github.com/SquareBracketAssociates/Booklet-uFFI/releases> > > So what you can do is to not bother and copy-edit and we fix the corresponding pillar > if you break it. > > Hey Stef :) > I'm guessing you mean to encourage Ted to "not worry" rather than "not bother" > https://www.phrasemix.com/phrases/not-bother-doing-something <https://www.phrasemix.com/phrases/not-bother-doing-something> Yes :) > > cheers -ben

Sept. 25, 2019

Re: [Pharo-dev] [Pharo-users] Pumping FFI documentation [WAS] FFI beginner question

by Ben Coman

On Wed, 25 Sep 2019 at 13:51, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi > > Normally each time a PR is integrated in a book, the CI is generating the > PDF. > https://github.com/SquareBracketAssociates/Booklet-uFFI/releases > > So what you can do is to not bother and copy-edit and we fix the > corresponding pillar > if you break it. > Hey Stef :) I'm guessing you mean to encourage Ted to "not worry" rather than "not bother" https://www.phrasemix.com/phrases/not-bother-doing-something cheers -ben

Sept. 25, 2019

[Pharo 8.0] Build #780: 2523-Use-NativeFileSystemBrowser-instead-of-just-NativeBrowser

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

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

Sept. 25, 2019

Re: [Pharo-dev] [Pharo-users] Pumping FFI documentation [WAS] FFI beginner question

by StÃ©phane Ducasse

Hi Normally each time a PR is integrated in a book, the CI is generating the PDF. https://github.com/SquareBracketAssociates/Booklet-uFFI/releases So what you can do is to not bother and copy-edit and we fix the corresponding pillar if you break it. Stef > On 24 Sep 2019, at 10:34, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > 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 <mailto:wild.ideas@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 <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 -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Sept. 25, 2019

Re: [Pharo-dev] Difficulty to use Iceberg

by Jan Vrany

On 2019-09-23 23:25, Sean P. DeNigris wrote: > 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 Thanks! Unfortunately, this discards any changes in working copy. i.e., any files `git status` reports a "modified". Without any warning. Cheers, Jan > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 24, 2019

[Pharo 8.0] Build #779: Fixed typo in category

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

There is a new Pharo build available! The status of the build #779 was: FAILURE. The Pull Request #4717 was integrated: "Fixed typo in category" Pull request url: https://github.com/pharo-project/pharo/pull/4717 Issue Url: https://github.com/pharo-project/pharo/issues/fixed 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 ducasse

> On 24 Sep 2019, at 14:54, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Marcus Denker-4 wrote >> we coud back port the fix... > > That would be great if you think it's fairly safe. Although personally I > could roll back my stateful traits use until P8 since I just started using > them. BTW what is the ETA for P8 release? beta end of nov. release end of feb? Unclear yet > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Sept. 24, 2019

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

by Sean P. DeNigris

Marcus Denker-4 wrote > we coud back port the fix... That would be great if you think it's fairly safe. Although personally I could roll back my stateful traits use until P8 since I just started using them. BTW what is the ETA for P8 release? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 24, 2019

[Pharo 8.0] Build #778: 4706 convenient method to instantiate a form from a base64 encoded string

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

There is a new Pharo build available! The status of the build #778 was: FAILURE. The Pull Request #4708 was integrated: "4706 convenient method to instantiate a form from a base64 encoded string" Pull request url: https://github.com/pharo-project/pharo/pull/4708 Issue Url: https://github.com/pharo-project/pharo/issues/4706 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 24, 2019

[Pharo 8.0] Build #777: Add-copy-title-command-to-windows

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

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

Sept. 24, 2019