- Pharo-dev - lists.pharo.org

State of Pillar
by Stephen Smith April 1, 2020

April 1, 2020

Hi all, due to the current state of the world I'm trying to spend some time helping with the Pharo books on the SquareBracketsAssociate's GitHub site (editing, contributing, etc.) I am very familiar with LaTeX, but I see that almost everything is using Pillar now. So I figured I would jump in and give Pillar a try. I've come to a screeching halt. Well, almost. I'm being dramatic, but the process has been a bit frustrating. Here's a small list of some of the frustrations I'm facing: 1. Most of the books appear to have been written in an older version of Pillar (7.7.4 according to the main page of the pillar-markup site, but I'm not sure how true this is). 2. After generating Html versions of several books (using 'pillar build html') I get readable output, but none of the chapters are numbered. This happens with existing book(lets) and also when I create a brand new book from the book archetype. I tried v8.0.2, then downgraded to 7.7.5, then to 7.7.4, and did not see any changes - I still have no chapter numbers. Perhaps I need to go back even further? If so, how can I tell which version of Pillar the last successful build of a booklet was created with? (other than comparing last publish dates with release dates of Pillar, and am I heading into dependency hell by installing older versions of Pillar?) 3. Pdf output halts with an error and doesn't even build. I'm getting errors related to OSSUnixSubprocess, so I'm assuming it's having trouble with my texlive config - I see some scripts have hardcoded texlive as being installed in the home folder (of which mine is not - I'm using ubuntu 19.10 with a standard texlive install). 4. The releases tab for most of the booklets sometimes contains a pdf, but most of the time, it doesn't. I'm sure it has to do with changes in the CI process over the years, but I would think this should be an important consistency to maintain? Anyway, I get it; it's a complicated tool (Pillar), and to produce Pdf, Html, whatever-custom-output-you-want, from a single source is no simple task. However, if we are to improve the situation, we need to improve the process and bring all the booklets up to date using pillar v8.0.X. Also, not an easy task and time-consuming. I'm willing to give some time to this, but I don't see any documentation for Pillar v8.0.X? Or much for any previous versions, either? Especially useful would be a document describing the differences in Pillar markup from previous versions. I see a chapter in Enterprise Pharo (pillar 4.0, I believe?), and two booklets (one outdated, one not so much). Neither of the booklets are produced with 100% correct output using pillar v8.0.2. What happened to pillar 5 and 6? There was also a mention in the Pillar booklet about a pillarhub open-access shared blog, but the link seems to be dead? http://pillarhub.pharocloud.com/ (I think pharocloud.com is long gone, no?) Can anyone point me to some recent docs on Pillar? If I have to read the source and figure things out myself, I'm willing to, but I guess I'm asking if anyone else is working on this stuff, is there a wiki, or has it been abandoned? Is it worth the effort to create yet another markdown-based publishing system? There are plenty in use already that might allow the effort to be put into the content instead of the framework to produce the content? My comments here are not meant as criticism in any way, just trying to get a pulse on the Pillar project, and I'd like to start committing changes to content (via pull-requests of course). Cheers, Stephen Smith Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

3 2

[Pharo 9.0] Build #210: Fixing spotter error
by ci-pharo-ci-jenkins2＠inria.fr April 1, 2020

April 1, 2020

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

1 0

[Pharo 9.0] Build #209: 5988-Executing-rewrite-on-classes-using-traits-then-commiting-remove-class-side-traits
by ci-pharo-ci-jenkins2＠inria.fr April 1, 2020

April 1, 2020

There is a new Pharo build available! The status of the build #209 was: SUCCESS. The Pull Request #6048 was integrated: "5988-Executing-rewrite-on-classes-using-traits-then-commiting-remove-class-side-traits" Pull request url: https://github.com/pharo-project/pharo/pull/6048 Issue Url: https://github.com/pharo-project/pharo/issues/5988 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #208: Improve UITestCase
by ci-pharo-ci-jenkins2＠inria.fr April 1, 2020

April 1, 2020

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

1 0

[Pharo 9.0] Build #207: [Opinion required] Add this context tester on the AST
by ci-pharo-ci-jenkins2＠inria.fr April 1, 2020

April 1, 2020

There is a new Pharo build available! The status of the build #207 was: SUCCESS. The Pull Request #6033 was integrated: "[Opinion required] Add this context tester on the AST" Pull request url: https://github.com/pharo-project/pharo/pull/6033 Issue Url: https://github.com/pharo-project/pharo/issues/addIsThisContext Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #206: Replace-exists-ifFalse-by-ifAbsent
by ci-pharo-ci-jenkins2＠inria.fr April 1, 2020

April 1, 2020

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

1 0

[Pharo 9.0] Build #205: CharacterKeyCombinationTest should be in a test package
by ci-pharo-ci-jenkins2＠inria.fr March 31, 2020

March 31, 2020

There is a new Pharo build available! The status of the build #205 was: FAILURE. The Pull Request #6077 was integrated: "CharacterKeyCombinationTest should be in a test package" Pull request url: https://github.com/pharo-project/pharo/pull/6077 Issue Url: https://github.com/pharo-project/pharo/issues/6076 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #204: Casing in Debugger step labels should be aligned
by ci-pharo-ci-jenkins2＠inria.fr March 31, 2020

March 31, 2020

There is a new Pharo build available! The status of the build #204 was: FAILURE. The Pull Request #6071 was integrated: "Casing in Debugger step labels should be aligned" Pull request url: https://github.com/pharo-project/pharo/pull/6071 Issue Url: https://github.com/pharo-project/pharo/issues/6070 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #203: Fix minimal Pharo on Window
by ci-pharo-ci-jenkins2＠inria.fr March 31, 2020

March 31, 2020

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

1 0

[ANN] Complishon: efficient heuristics for code completion
by Guillermo Polito March 31, 2020

March 31, 2020

Hi all, Since yesterday, Pharo 9 contains a new alternative code completion engine. The idea behind this engine is to be pluggable, to be efficient and to be more accurate through the introduction of heuristics. The completion engine implements a couple of nice heuristics, like - chances are `anOrderedCollection` references an ordered collection - chances are you want to auto-complete messages implemented in the same package New heuristics can be added easily (I was playing with plugging heuristics using type inference like roel typer). If you want more details, check the blogpost: https://masteringobjects.wordpress.com/2020/03/30/complishon-efficient-heur… <https://masteringobjects.wordpress.com/2020/03/30/complishon-efficient-heur…> And if you have ideas for new heuristics that could make your Pharo experience better, let us know! Cheers, Guille

1 0