- Pharo-dev - lists.pharo.org

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

by ducasse

> On 25 Sep 2019, at 17:56, Brainstorms <wild.ideas(a)gmail.com> wrote: > > I can offer my writing/editing/proofreading skills for this work, too. > > As Guillermo pointed out, the documentation is "super important". And I can > be immediately productive there, as my English skills are way ahead of my > Pharo coding skills. Read what you want. I would like to produce a booklet out of the excellent libraries sven is developing over the years so that we can update the documentation that he wrote in Entreprise Pharo. > I'm also approaching this as a relative newbie, and as someone with > aspirations to start teaching Pharo (informally, at least at first) where I > workâ¦ The mooc contains a lot of material that is under CC so feel free to use, ask for feedback we can also help with a remote lecture if you see fit. > > -t > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Sept. 25, 2019

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

by Brainstorms

I can offer my writing/editing/proofreading skills for this work, too. As Guillermo pointed out, the documentation is "super important". And I can be immediately productive there, as my English skills are way ahead of my Pharo coding skills. I'm also approaching this as a relative newbie, and as someone with aspirations to start teaching Pharo (informally, at least at first) where I work... -t -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 25, 2019

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

by ducasse

It has probably some rough edges so to not hesitate to come back to us. Iâm currently migrating all the books, booklets, to the latest tagged version. >> On 25 Sep 2019, at 16:51, Brainstorms <wild.ideas(a)gmail.com> wrote: >> >> Hi Stef, >> >> Okay, that's in line with what I expected. No worries! >> >> The devops part of me still wants to know how the process works, though. I >> like the format it produces, and I could see adopting it for a documentation >> tool outside of Pharo (assuming everything is open source). > > Yes it is fully open-source. > It has a way to plug different âbookâ templates. > I know some companies that used it to generate documentation. > Now with guillermo we spent some days there and there to improve (all my slides, books, â¦.) > are based on pillar. > > Stef >> >> -Ted >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >> > > >

Sept. 25, 2019

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

by ducasse

> On 25 Sep 2019, at 16:51, Brainstorms <wild.ideas(a)gmail.com> wrote: > > Hi Stef, > > Okay, that's in line with what I expected. No worries! > > The devops part of me still wants to know how the process works, though. I > like the format it produces, and I could see adopting it for a documentation > tool outside of Pharo (assuming everything is open source). Yes it is fully open-source. It has a way to plug different âbookâ templates. I know some companies that used it to generate documentation. Now with guillermo we spent some days there and there to improve (all my slides, books, â¦.) are based on pillar. Stef > > -Ted > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Sept. 25, 2019

Re: [Pharo-dev] Difficulty to use Iceberg

by Brainstorms

Hi Jan, (I wasn't subscribed to the Dev list until today, so now I can respond here, in the same thread.) Would "git worktree add" solve your problem? This allows you to create multiple working trees that are all associated with the same repository. I haven't tried this myself (yet), but I expect this would allow Pharo to interact normally with the original working copy, while providing a second working directory for your C++ co-development, all without the need to clone an additional working copy. -Ted -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 25, 2019

[Pharo 8.0] Build #781: Add-example-to-RBRenameClassRefactoring

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

There is a new Pharo build available! The status of the build #781 was: FAILURE. The Pull Request #4725 was integrated: "Add-example-to-RBRenameClassRefactoring" Pull request url: https://github.com/pharo-project/pharo/pull/4725 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. 25, 2019

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

by Brainstorms

Hi Stef, Okay, that's in line with what I expected. No worries! The devops part of me still wants to know how the process works, though. I like the format it produces, and I could see adopting it for a documentation tool outside of Pharo (assuming everything is open source). -Ted -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 25, 2019

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