- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #827: 20878-Alien-tests-should-be-in-a-Alien-Tests-package

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

There is a new Pharo build available! The status of the build #827 was: SUCCESS. The Pull Request #1202 was integrated: "20878-Alien-tests-should-be-in-a-Alien-Tests-package" Pull request url: https://github.com/pharo-project/pharo/pull/1202 Issue Url: https://pharo.fogbugz.com/f/cases/20878 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 3, 2018

[Pharo 7.0-dev] Build #826: 21737-NullStream-sends-self-positionError-but-does-not-implement-it

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

There is a new Pharo build available! The status of the build #826 was: SUCCESS. The Pull Request #1279 was integrated: "21737-NullStream-sends-self-positionError-but-does-not-implement-it" Pull request url: https://github.com/pharo-project/pharo/pull/1279 Issue Url: https://pharo.fogbugz.com/f/cases/21737 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 3, 2018

Re: [Pharo-dev] Fix for 21809

by Hilaire

Thanks Marcus Le 02/05/2018 Ã 12:53, Marcus Denker a Ã©critÂ : >> I don't learn yet the current procedure to integrate fixes so I let it for someone with the know how. >> > I merged the Pull Request. > > Marcus > > > -- Dr. Geo http://drgeo.eu

May 3, 2018

Re: [Pharo-dev] Pharo Bootstrap familiarity

by Guillermo Polito

Hi Ben, as Nicolas said, yes, MOP is for Meta Object Protocol (really nice book btw https://www.amazon.com/Art-Metaobject-Protocol-Gregor-Kiczales/dp/0262610744 ). Ben, the process is not carved in stone and we are fully aware that it can be enhanced :). Any enhancement, even the littlest one, is important. If it is important for your workflows to add more logging information, let's add them! Nicolas, Actually the special interpreter is not the simulator. We do not use the bytecode interpreter in the simulator, we use an AST interpreter that has "lazy class creation" semantics plus some other little tricks to initialize the circular dependencies of metaclasses and so on... Behind, we use the simulator only to store the objects and decouple ourselves from the object format (this removed for example a lot of work when migrating from V3 to Spur). On Wed, May 2, 2018 at 10:04 PM, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > Nice reverse engineering! > > MOP is Meta Object Protocol (serach in reference [9]). > > Maybe you miss a reference to the definition of BaselineOfPharoBootstrap > https://github.com/pharo-project/pharo/blob/development/bootstrap/src/ > Pharo30Bootstrap.package/PBBootstrap.class/instance/ > allPackagesForHermes.st > https://github.com/pharo-project/pharo/blob/development/bootstrap/src/ > Pharo30Bootstrap.package/PBBootstrap.class/instance/ > ensureBaselineOfPharoBootstrap.st > > And the simulator too (the special interpreter). > > 2018-05-02 20:53 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > >> I found it hard to find info on the Pharo Bootstrap, so I went looking to >> understand the it by identifying very first creation on disk of the >> smallest "seed".image file that will later become the final build >> artifact. I'm sharing here to have a record I can refer to later, and >> maybe others find interesting. >> >> Looking at the log from the latest build... >> https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20p >> ull%20request%20and%20branch%20Pipeline/job/development/822/consoleFull >> >> Searching on "BUILD_NUMBER=" indicates the first major CI step is... >> >> + BUILD_NUMBER=822 BOOTSTRAP_ARCH=32 bash ./bootstrap/scripts/2-download.sh >> [1] >> which downloads 24MB " bootstrapImage.zip" [2] >> which I presume is an almost full image to run the bootstrap process. >> >> [1] https://github.com/pharo-project/pharo/blob/development/ >> bootstrap/scripts/2-download.sh >> [2] https://github.com/guillep/PharoBootstrap/releases/download/ >> v1.4.1/bootstrapImage.zip >> >> >> The next major CI step is... >> >> + BUILD_NUMBER=822 BOOTSTRAP_ARCH=32 bash ./bootstrap/scripts/3-prepare.sh >> [3] >> which uses the downloaded "Pharo.image" to (I presume) produce the seed >> "bootstrap.image" file. >> (This is not indicated explicitly in the logs, but step 4 copies that file >> with a shell command, so my presumption. It would be nice for this to be >> explicitly logged" >> >> prepare.sh executes two commands... >> >> ./pharo Pharo.image ..../bootstrap/scripts/prepare_image.st --save >> --quit [4] >> which seems to modify the downloaded "Pharo.image", >> not create bootstrap.image >> >> ./pharo Pharo.image ..../bootstrap/scripts/bootstrap.st --ARCH=32 >> --BUILD_NUMBER=822 --quit [5] >> which does... "PBBootstrap fromCommandLine bootstrap" [6] [7] >> which does... >> PBBootstrap>>#bootstrap >> PBStepStartedSignal log: 'Starting Process.'. >> self prepareBootstrap. >> [self createImage ] on:AssertionFailure do: [ :e | e resume ]. >> self initializeImage. >> PBStepFinishedSignal log: 'Process ended.' >> and digging a bit... >> >> PBBootstrap>>#createImage >> | builder | >> builder := PBImageBuilderSpur50 forArchitecture: architecture. >> builder definitionFetcher: versionFetcher. >> builder buildNumber: buildNumber. >> builder imageFileReference: imageReference. >> builder systemDefinition: ringEnvironment. >> builder espellBackend instanceVariableMapping: >> (PBInstanceVariableMapping onEnvironment: ringEnvironment ). >> builder bootstrap >> >> >> PBImageBuilderSpur50-class>>#forArchitecture: architecture >> | candidates | >> candidates := self subclasses select: [ :sc | sc name endsWith: >> architecture, 'bit' ]. >> candidates >> ifEmpty: [ self error: 'No candidates for architecture: ', >> architecture ]. >> candidates size > 1 >> ifTrue: [ self error: 'More than one candidate for >> architecture: ', architecture ]. >> ^ candidates anyOne new >> >> >> PBImageBuilderSpur50 >>#initialize >> super initialize. >> statistics := PBBootstrapStatistics new. >> logger := PBBootstrapLogger new. >> imageFileReference := 'bootstrap.image' asFileReference. >> >> "the default espell backend for the bootstrap" >> self initializeBackend. >> self instantiateClassLoader. >> >> ahh, there is the reference to "bootstrap.image" >> >> So just to round out a high level overview, the last two messages sent >> are defined as... >> >> PBImageBuilderSpur5032bit>>#initializeBackend >> espellBackend := EPSimulatorBackend for32Bit forBootstrap >> >> which I won't dig further but the class seems available at [8] >> and Espell is described briefly at [9] (but what is a "MOP"? the term is >> not defined there) >> >> >> PBImageBuilderSpur50>>#instantiateClassLoader >> classLoader := PBSpurClassLoader new. >> >> which is defined at [10], and there is an interesting example at [11]. >> >> >> [3] https://github.com/pharo-project/pharo/blob/development/ >> bootstrap/scripts/3-prepare.sh >> [4] https://github.com/pharo-project/pharo/blob/development/ >> bootstrap/scripts/prepare_image.st >> [5] https://github.com/pharo-project/pharo/blob/development/ >> bootstrap/scripts/bootstrap.st >> [6] https://github.com/pharo-project/pharo/blob/development/ >> bootstrap/src/Pharo30Bootstrap.package/PBBootstrap.class/ >> class/fromCommandLine.st >> [7] https://github.com/pharo-project/pharo/blob/development/ >> bootstrap/src/Pharo30Bootstrap.package/PBBootstrap.class/ >> instance/bootstrap.st >> [8] https://github.com/guillep/espell/blob/master/src/ >> EspellSimulator.package/EPSimulatorBackend.class/class/for32Bit.st >> [9] https://rmod.inria.fr/archives/papers/Poli15a-Onward- >> Bootstrapping.pdf >> [10] https://github.com/pharo-project/pharo/tree/development >> /bootstrap/src/Pharo30Bootstrap.package/PBSpurClassLoader.class >> [11] https://github.com/pharo-project/pharo/blob/development >> /bootstrap/src/Pharo30Bootstrap.package/PBImageBuilderSpur50 >> .class/class/example5617.st >> >> >> So now I guess that bootstrap.image has been generated? >> Just curious, what is the size of this file right now, before the next >> step? >> Perhaps an `ls -l` could echo this to the build log. >> >> >> The penultimate major CI step seems to then start adding packages to >> bootstrap.image... >> >> + BUILD_NUMBER=822 BOOTSTRAP_ARCH=32 bash ./bootstrap/scripts/4-build.sh >> >> located at [12] and searching on "${VM}" is enlightening. >> Its help information says... >> Pharo Build Script >> ================== >> This script assumes the existence of a new uninitialized image. Then it >> proceeds to its initialization and \"growing\". >> * Step 1: >> - Initialize the image >> - output: core.image >> * Step 2: >> - Bootstrap Monticello local repositories >> - output: monticello_bootstrap.image and changes file >> * Step 3: >> - Load Monticello remote repositories >> - output: monticello.image and changes file >> * Step 4: >> - Load Metacello >> - output: metacello.image and changes file >> * Step 5: >> - Load the rest of the image using BaselineOfIDE >> - output: Pharo.image and changes file >> >> Unfortunately those steps are labelled in the script, >> but the first action shown in the log is... >> cp bootstrap.image Pharo7.0-compiler-32bit-9912d7c.image >> Initializing Bootstraped Image >> pharo --headless Pharo7.0-compiler-32bit-9912d7c.image >> >> [12] https://github.com/pharo-project/pharo/blob/development >> /bootstrap/scripts/4-build.sh >> >> >> >> The final major CI step was a fair way past what I was interested in >> right now. ... >> >> + BUILD_NUMBER=822 bash ../bootstrap/scripts/prepare_for_upload.sh >> >> >> >> cheers -ben >> >> > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

May 3, 2018

[Pharo 7.0-dev] Build #825: 21783 Better tagging in Collections-Abstract

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

There is a new Pharo build available! The status of the build #825 was: SUCCESS. The Pull Request #1256 was integrated: "21783 Better tagging in Collections-Abstract" Pull request url: https://github.com/pharo-project/pharo/pull/1256 Issue Url: https://pharo.fogbugz.com/f/cases/21783 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 2, 2018

Re: [Pharo-dev] Pharo Bootstrap familiarity

by Nicolas Cellier

Nice reverse engineering! MOP is Meta Object Protocol (serach in reference [9]). Maybe you miss a reference to the definition of BaselineOfPharoBootstrap https://github.com/pharo-project/pharo/blob/development/bootstrap/src/Pharo… https://github.com/pharo-project/pharo/blob/development/bootstrap/src/Pharo… And the simulator too (the special interpreter). 2018-05-02 20:53 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > I found it hard to find info on the Pharo Bootstrap, so I went looking to > understand the it by identifying very first creation on disk of the > smallest "seed".image file that will later become the final build > artifact. I'm sharing here to have a record I can refer to later, and > maybe others find interesting. > > Looking at the log from the latest build... > https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending% > 20pull%20request%20and%20branch%20Pipeline/job/development/822/consoleFull > > Searching on "BUILD_NUMBER=" indicates the first major CI step is... > > + BUILD_NUMBER=822 BOOTSTRAP_ARCH=32 bash ./bootstrap/scripts/2-download.sh > [1] > which downloads 24MB " bootstrapImage.zip" [2] > which I presume is an almost full image to run the bootstrap process. > > [1] https://github.com/pharo-project/pharo/blob/ > development/bootstrap/scripts/2-download.sh > [2] https://github.com/guillep/PharoBootstrap/releases/download/v1.4.1/ > bootstrapImage.zip > > > The next major CI step is... > > + BUILD_NUMBER=822 BOOTSTRAP_ARCH=32 bash ./bootstrap/scripts/3-prepare.sh > [3] > which uses the downloaded "Pharo.image" to (I presume) produce the seed > "bootstrap.image" file. > (This is not indicated explicitly in the logs, but step 4 copies that file > with a shell command, so my presumption. It would be nice for this to be > explicitly logged" > > prepare.sh executes two commands... > > ./pharo Pharo.image ..../bootstrap/scripts/prepare_image.st --save > --quit [4] > which seems to modify the downloaded "Pharo.image", > not create bootstrap.image > > ./pharo Pharo.image ..../bootstrap/scripts/bootstrap.st --ARCH=32 > --BUILD_NUMBER=822 --quit [5] > which does... "PBBootstrap fromCommandLine bootstrap" [6] [7] > which does... > PBBootstrap>>#bootstrap > PBStepStartedSignal log: 'Starting Process.'. > self prepareBootstrap. > [self createImage ] on:AssertionFailure do: [ :e | e resume ]. > self initializeImage. > PBStepFinishedSignal log: 'Process ended.' > and digging a bit... > > PBBootstrap>>#createImage > | builder | > builder := PBImageBuilderSpur50 forArchitecture: architecture. > builder definitionFetcher: versionFetcher. > builder buildNumber: buildNumber. > builder imageFileReference: imageReference. > builder systemDefinition: ringEnvironment. > builder espellBackend instanceVariableMapping: > (PBInstanceVariableMapping onEnvironment: ringEnvironment ). > builder bootstrap > > > PBImageBuilderSpur50-class>>#forArchitecture: architecture > | candidates | > candidates := self subclasses select: [ :sc | sc name endsWith: > architecture, 'bit' ]. > candidates > ifEmpty: [ self error: 'No candidates for architecture: ', > architecture ]. > candidates size > 1 > ifTrue: [ self error: 'More than one candidate for > architecture: ', architecture ]. > ^ candidates anyOne new > > > PBImageBuilderSpur50 >>#initialize > super initialize. > statistics := PBBootstrapStatistics new. > logger := PBBootstrapLogger new. > imageFileReference := 'bootstrap.image' asFileReference. > > "the default espell backend for the bootstrap" > self initializeBackend. > self instantiateClassLoader. > > ahh, there is the reference to "bootstrap.image" > > So just to round out a high level overview, the last two messages sent are > defined as... > > PBImageBuilderSpur5032bit>>#initializeBackend > espellBackend := EPSimulatorBackend for32Bit forBootstrap > > which I won't dig further but the class seems available at [8] > and Espell is described briefly at [9] (but what is a "MOP"? the term is > not defined there) > > > PBImageBuilderSpur50>>#instantiateClassLoader > classLoader := PBSpurClassLoader new. > > which is defined at [10], and there is an interesting example at [11]. > > > [3] https://github.com/pharo-project/pharo/blob/ > development/bootstrap/scripts/3-prepare.sh > [4] https://github.com/pharo-project/pharo/blob/ > development/bootstrap/scripts/prepare_image.st > [5] https://github.com/pharo-project/pharo/blob/ > development/bootstrap/scripts/bootstrap.st > [6] https://github.com/pharo-project/pharo/blob/development/bootstrap/src/ > Pharo30Bootstrap.package/PBBootstrap.class/class/fromCommandLine.st > [7] https://github.com/pharo-project/pharo/blob/development/bootstrap/src/ > Pharo30Bootstrap.package/PBBootstrap.class/instance/bootstrap.st > [8] https://github.com/guillep/espell/blob/master/ > src/EspellSimulator.package/EPSimulatorBackend.class/class/for32Bit.st > [9] https://rmod.inria.fr/archives/papers/Poli15a-Onward-Bootstrapping.pdf > [10] https://github.com/pharo-project/pharo/tree/ > development/bootstrap/src/Pharo30Bootstrap.package/PBSpurClassLoader.class > [11] https://github.com/pharo-project/pharo/blob/ > development/bootstrap/src/Pharo30Bootstrap.package/ > PBImageBuilderSpur50.class/class/example5617.st > > > So now I guess that bootstrap.image has been generated? > Just curious, what is the size of this file right now, before the next > step? > Perhaps an `ls -l` could echo this to the build log. > > > The penultimate major CI step seems to then start adding packages to > bootstrap.image... > > + BUILD_NUMBER=822 BOOTSTRAP_ARCH=32 bash ./bootstrap/scripts/4-build.sh > located at [12] and searching on "${VM}" is enlightening. > Its help information says... > Pharo Build Script > ================== > This script assumes the existence of a new uninitialized image. Then it > proceeds to its initialization and \"growing\". > * Step 1: > - Initialize the image > - output: core.image > * Step 2: > - Bootstrap Monticello local repositories > - output: monticello_bootstrap.image and changes file > * Step 3: > - Load Monticello remote repositories > - output: monticello.image and changes file > * Step 4: > - Load Metacello > - output: metacello.image and changes file > * Step 5: > - Load the rest of the image using BaselineOfIDE > - output: Pharo.image and changes file > > Unfortunately those steps are labelled in the script, > but the first action shown in the log is... > cp bootstrap.image Pharo7.0-compiler-32bit-9912d7c.image > Initializing Bootstraped Image > pharo --headless Pharo7.0-compiler-32bit-9912d7c.image > > [12] https://github.com/pharo-project/pharo/blob/ > development/bootstrap/scripts/4-build.sh > > > > The final major CI step was a fair way past what I was interested in > right now. ... > > + BUILD_NUMBER=822 bash ../bootstrap/scripts/prepare_for_upload.sh > > > > cheers -ben > >

May 2, 2018

Pharo Bootstrap familiarity

by Ben Coman

I found it hard to find info on the Pharo Bootstrap, so I went looking to understand the it by identifying very first creation on disk of the smallest "seed".image file that will later become the final build artifact. I'm sharing here to have a record I can refer to later, and maybe others find interesting. Looking at the log from the latest build... https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… Searching on "BUILD_NUMBER=" indicates the first major CI step is... + BUILD_NUMBER=822 BOOTSTRAP_ARCH=32 bash ./bootstrap/scripts/2-download.sh [1] which downloads 24MB " bootstrapImage.zip" [2] which I presume is an almost full image to run the bootstrap process. [1] https://github.com/pharo-project/pharo/blob/development/bootstrap/scripts/2… [2] https://github.com/guillep/PharoBootstrap/releases/download/v1.4.1/bootstra… The next major CI step is... + BUILD_NUMBER=822 BOOTSTRAP_ARCH=32 bash ./bootstrap/scripts/3-prepare.sh [3] which uses the downloaded "Pharo.image" to (I presume) produce the seed "bootstrap.image" file. (This is not indicated explicitly in the logs, but step 4 copies that file with a shell command, so my presumption. It would be nice for this to be explicitly logged" prepare.sh executes two commands... ./pharo Pharo.image ..../bootstrap/scripts/prepare_image.st --save --quit [4] which seems to modify the downloaded "Pharo.image", not create bootstrap.image ./pharo Pharo.image ..../bootstrap/scripts/bootstrap.st --ARCH=32 --BUILD_NUMBER=822 --quit [5] which does... "PBBootstrap fromCommandLine bootstrap" [6] [7] which does... PBBootstrap>>#bootstrap PBStepStartedSignal log: 'Starting Process.'. self prepareBootstrap. [self createImage ] on:AssertionFailure do: [ :e | e resume ]. self initializeImage. PBStepFinishedSignal log: 'Process ended.' and digging a bit... PBBootstrap>>#createImage | builder | builder := PBImageBuilderSpur50 forArchitecture: architecture. builder definitionFetcher: versionFetcher. builder buildNumber: buildNumber. builder imageFileReference: imageReference. builder systemDefinition: ringEnvironment. builder espellBackend instanceVariableMapping: (PBInstanceVariableMapping onEnvironment: ringEnvironment ). builder bootstrap PBImageBuilderSpur50-class>>#forArchitecture: architecture | candidates | candidates := self subclasses select: [ :sc | sc name endsWith: architecture, 'bit' ]. candidates ifEmpty: [ self error: 'No candidates for architecture: ', architecture ]. candidates size > 1 ifTrue: [ self error: 'More than one candidate for architecture: ', architecture ]. ^ candidates anyOne new PBImageBuilderSpur50 >>#initialize super initialize. statistics := PBBootstrapStatistics new. logger := PBBootstrapLogger new. imageFileReference := 'bootstrap.image' asFileReference. "the default espell backend for the bootstrap" self initializeBackend. self instantiateClassLoader. ahh, there is the reference to "bootstrap.image" So just to round out a high level overview, the last two messages sent are defined as... PBImageBuilderSpur5032bit>>#initializeBackend espellBackend := EPSimulatorBackend for32Bit forBootstrap which I won't dig further but the class seems available at [8] and Espell is described briefly at [9] (but what is a "MOP"? the term is not defined there) PBImageBuilderSpur50>>#instantiateClassLoader classLoader := PBSpurClassLoader new. which is defined at [10], and there is an interesting example at [11]. [3] https://github.com/pharo-project/pharo/blob/development/bootstrap/scripts/3… [4] https://github.com/pharo-project/pharo/blob/development/bootstrap/scripts/p… [5] https://github.com/pharo-project/pharo/blob/development/bootstrap/scripts/b… [6] https://github.com/pharo-project/pharo/blob/development/bootstrap/src/Pharo… [7] https://github.com/pharo-project/pharo/blob/development/bootstrap/src/Pharo… [8] https://github.com/guillep/espell/blob/master/src/EspellSimulator.package/E… [9] https://rmod.inria.fr/archives/papers/Poli15a-Onward-Bootstrapping.pdf [10] https://github.com/pharo-project/pharo/tree/development/bootstrap/src/Pharo… [11] https://github.com/pharo-project/pharo/blob/development/bootstrap/src/Pharo… So now I guess that bootstrap.image has been generated? Just curious, what is the size of this file right now, before the next step? Perhaps an `ls -l` could echo this to the build log. The penultimate major CI step seems to then start adding packages to bootstrap.image... + BUILD_NUMBER=822 BOOTSTRAP_ARCH=32 bash ./bootstrap/scripts/4-build.sh located at [12] and searching on "${VM}" is enlightening. Its help information says... Pharo Build Script ================== This script assumes the existence of a new uninitialized image. Then it proceeds to its initialization and \"growing\". * Step 1: - Initialize the image - output: core.image * Step 2: - Bootstrap Monticello local repositories - output: monticello_bootstrap.image and changes file * Step 3: - Load Monticello remote repositories - output: monticello.image and changes file * Step 4: - Load Metacello - output: metacello.image and changes file * Step 5: - Load the rest of the image using BaselineOfIDE - output: Pharo.image and changes file Unfortunately those steps are labelled in the script, but the first action shown in the log is... cp bootstrap.image Pharo7.0-compiler-32bit-9912d7c.image Initializing Bootstraped Image pharo --headless Pharo7.0-compiler-32bit-9912d7c.image [12] https://github.com/pharo-project/pharo/blob/development/bootstrap/scripts/4… The final major CI step was a fair way past what I was interested in right now. ... + BUILD_NUMBER=822 bash ../bootstrap/scripts/prepare_for_upload.sh cheers -ben

May 2, 2018

[Pharo 7.0-dev] Build #824: 21760-cleanup-AbstractTool-remove-all-unsent-message

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

There is a new Pharo build available! The status of the build #824 was: SUCCESS. The Pull Request #1278 was integrated: "21760-cleanup-AbstractTool-remove-all-unsent-message" Pull request url: https://github.com/pharo-project/pharo/pull/1278 Issue Url: https://pharo.fogbugz.com/f/cases/21760 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 2, 2018

Re: [Pharo-dev] [ANN] ba-st Web Stack family gets a new member: Willow-Mixpanel and new releases

by Tim Mackinnon

Iâve also been digging in - and it has inspired me to try and solve a few internal reporting problems and actually have a way to make them look decentâ¦ looking forward to a few more medium posts that cover some of the harder bits. > On 2 May 2018, at 08:45, Julien <julien.delplanque(a)inria.fr> wrote: > > Hello, > > I played a little with Willow yesterday evening and it looks really cool. > > Thanks for this project. > > Julien > > --- > Julien Delplanque > Doctorant Ã lâUniversitÃ© de Lille 1 > http://juliendelplanque.be/phd.html <http://juliendelplanque.be/phd.html> > Equipe Rmod, Inria > BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq > NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40 > >> Le 1 mai 2018 Ã 15:28, Gabriel Cotelli <g.cotelli(a)gmail.com <mailto:g.cotelli@gmail.com>> a Ã©crit : >> >> Hi, >> >> We're happy to announce a new member in the Web Stack family hosted at https://github.com/ba-st/ <https://github.com/ba-st/> : Willow-Mixpanel <https://github.com/ba-st/Willow-Mixpanel>. >> >> This is also a multi-release announcement of the following project versions: >> Willow-Mixpanel <https://github.com/ba-st/Willow-Mixpanel> v1.0.0 >> Provides Integration between Willow <https://github.com/ba-st/Willow/> and the Mixpanel Javascript API making easy to send events directly from the browser >> HighchartsSt <https://github.com/ba-st/HighchartsSt> v7.0.0 >> Updated Highcharts and Highstock JS libraries to version 6.0.7 >> Improved Importing Tools >> Migrated sources to Tonel >> Willow <https://github.com/ba-st/Willow> v8.0.2. Changes since latest announcement: >> Migrate sources to Tonel format >> Improve ScrollIntoViewCommand >> Updated JQuery to 3.3.1 >> Improve libraries test cases to verify the file contents >> Fixed Bug #108 <https://github.com/ba-st/Willow/issues/108>: Senders of #identifier must ensure the component has assigned an id >> Added FAQs to documentation >> Added an easy way to add additional libraries to a WillowApplication >> Added table footer support >> Added to interaction interpreters: >> show:whileCallingServerToRender: This will replace anIdentifiedWebView contents with aRenderable in the DOM before doing the server call, and replace it again with the rendering obtained from the server call response >> transform:into: This will replace anIdentifiedWebView content with aRenderable on the browser side >> >> Willow-Bootstrap <https://github.com/ba-st/Willow-Bootstrap> v8.0.2 >> Improve file deployment tests >> Update datepicker plugin to v1.8.0 >> Migrated sources to Tonel format >> Willow-JQueryUI <https://github.com/ba-st/Willow-JQueryUI> v7.1.0 >> Added JQuery UI dialog builder to component supplier >> Improve file deployment tests >> Migrated sources to Tonel format >> Willow-SpinKit <https://github.com/ba-st/Willow-SpinKit> v5.0.2 >> Improve file deployment tests >> Migrated sources to Tonel format >> Willow-Playground <https://github.com/ba-st/Willow-Playground/> v5.0.0 >> Improve package tagging and rename some classes to make the code more uniform >> Use the new interaction facilities >> RenoirSt <https://github.com/ba-st/RenoirSt> v5.0.0 >> Migrated sources to Tonel format >> Updated dependencies >> Find a more detailed changelog and migration instructions on the release pages of each repository. >> >> Special thanks to Tim Mackinnon <https://github.com/macta> for the constructive feedback driving some of the improvements in Willow and Francisco Ortiz <https://github.com/fortizpenaloza> for the Mixpanel support. >> >> Anyone interested in joining our ba-st projects <https://github.com/ba-st/> is welcomed. >> >> Regards, >> Gabriel Cotelli, Maxi Tabacman and all the contributors. >

May 2, 2018

[Pharo 7.0-dev] Build #823: 21778-Some-more-small-cleanups-in-OpalCompiler

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

There is a new Pharo build available! The status of the build #823 was: SUCCESS. The Pull Request #1276 was integrated: "21778-Some-more-small-cleanups-in-OpalCompiler" Pull request url: https://github.com/pharo-project/pharo/pull/1276 Issue Url: https://pharo.fogbugz.com/f/cases/21778 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 2, 2018