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

> Pay attention because Pharo could be better for supplanting bash. That was one of the first things I was evaluating Pharo on, to see its potential for replacing Bash (and therefore Lua, which I was also considering for this, initially; I'm one of those holdouts who hasn't learned Python -- I

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

> On 26 Sep 2019, at 20:14, Brainstorms wrote: > > I have found a project that I think is a good fit in size & complexity, one > that can operate at that "CLI level" (i.e., doesn't need a GUI or a web > front end). > > We ("we" being my group and a number of projects around the Laboratory

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

I have found a project that I think is a good fit in size & complexity, one that can operate at that "CLI level" (i.e., doesn't need a GUI or a web front end). We ("we" being my group and a number of projects around the Laboratory we've been associated with) are migrating code from a Subversion

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

> > Schmidt Pro looks like a U.S. firm. no this is a german one. > There are multiple Lifewares, but I > think you may be referring to the INRIA associate? Lifeware.ch > >> Also what is important is that Mooc is a key assets: why because it >> represents >> 15 years of teaching

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

Hi Stef, > What I can tell you is that we are growing :). > When a company with more than 30 millions lines of code wants to migrate > to Pharo. > It means something :) and we are helping them and they actively support > the consortium > with immediate impact. Pablo is working full time to

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

Hi ted > Thank you, I will; community support will be important -- developers (and > their managers!) are very conscious of the "critical mass" issue. What I can tell you is that we are growing :). When a company with more than 30 millions lines of code wants to migrate to Pharo. It means

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

Thank you, I will; community support will be important -- developers (and their managers!) are very conscious of the "critical mass" issue. They all want to know that if they make an investment in learning and using a new language, tools, development paradigm, etc. that there's a company/support

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

Ok! Let us know how we can help. There is also the Pharo consortium: it is free for “academix” but is a nice way to show that we are working in a sound robust eco-“system”. There is enough space for everyone willing to contribute. And I do not know if you saw some of our talks but Pharo is

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

I'll likely start working with Guillermo on the UFFI booklet. I also see the 'by example' booklets as being /very/ important, as they give critical first impressions to those new to the whole concept of Smalltalk. I want to enroll others in Pharo, and that means I need good docs/web pages to

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

> On 25 Sep 2019, at 17:56, Brainstorms 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

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

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

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

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 wrote: >> >> Hi Stef, >> >> Okay, that's in line with what I expected. No worries! >> >> The

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

> On 25 Sep 2019, at 16:51, Brainstorms 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

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

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

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

> On 25 Sep 2019, at 15:22, Ben Coman wrote: > > > > On Wed, 25 Sep 2019 at 13:51, Stéphane Ducasse > wrote: > Hi > > Normally each time a PR is integrated in a book, the CI is generating the > PDF. >

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

On Wed, 25 Sep 2019 at 13:51, Stéphane Ducasse 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

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

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,