June 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] Epicea, Ombu and Hiedra packages have new "official" repository

by Martin Dias

On Wed, Jun 6, 2018 at 4:27 AM Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > > On 5 Jun 2018, at 20:49, Martin Dias <tinchodias(a)gmail.com> wrote: > > > > On Tue, Jun 5, 2018 at 3:30 PM HernÃ¡n Morales Durand > > <hernan.morales(a)gmail.com> wrote: > >> What are Ombu and Hiedra? > > > > Hello HernÃ¡n, this is how I described them: > > > > Ombu: > > "Epicea has a small subproject, named Ombu, which provides simple > > persistence. By default, Ombu uses STON to write the events when they > > are announced in the system." > > ------- from http://smalltalkhub.com/#!/~MartinDias/Epicea > > > > Hiedra: > > "It is a small Pharo project to visually connect items in a > > history-like graph. It uses Athens, and provides support for Morphic > > and Spec." > > ------- from https://github.com/tinchodias/hiedra which is a repo that > > I might close or should say in readme that it's not the official repo > > > > But not sure if I described correctly... in concrete, Hiedra is what's > > used from Epicea Spec UI in a TableModel to draw the links between > > epicea logs in the left panel. > > > > We should add exactly those description as package level comments. > > https://pharo.fogbugz.com/f/cases/22079/package-comments-for-Ombu-and-Hiedra Fine > > > What I do not like is that the package name gives no clue what this is > aboutâ¦ > Not even the âneighbourhoodâ. E.g. it does not even get clear that Ombu > and Epicea are relatedâ¦ > But we have that problem with many packages. > > I agree. In the beginning, when this was a prototype, it made sense to me to have 2 separate projects but at the end they are so closely related that it could be good to move Ombu classes into Epicea. > Marcus > > > >

June 6, 2018

[Pharo 7.0-dev] Build #1019: 22050-Menubar-should-reject-event-that-are-not-on-the-menu-to-let-the-user-drag-its-windows

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

There is a new Pharo build available! The status of the build #1019 was: FAILURE. The Pull Request #1477 was integrated: "22050-Menubar-should-reject-event-that-are-not-on-the-menu-to-let-the-user-drag-its-windows" Pull request url: https://github.com/pharo-project/pharo/pull/1477 Issue Url: https://pharo.fogbugz.com/f/cases/22050 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 6, 2018

[Pharo 7.0-dev] Build #1018: 22077-Remove-dead-code-in-RPackage-tests

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

There is a new Pharo build available! The status of the build #1018 was: SUCCESS. The Pull Request #1493 was integrated: "22077-Remove-dead-code-in-RPackage-tests" Pull request url: https://github.com/pharo-project/pharo/pull/1493 Issue Url: https://pharo.fogbugz.com/f/cases/22077 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 6, 2018

Re: [Pharo-dev] [PROPOSAL] Put the WorldMenu in a Menu bar

by Guillermo Polito

Hi Hilaire, On Tue, Jun 5, 2018 at 9:38 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > Can the bar menu be customized as it is the case with the World menu ? > (i.e. DrGeo world menu) > > The menu bar is populated the same way as the World menu. So if you change the world menu, or the world menu pragma and you rebuild the menu the menu bar will be updated accordingly.

June 6, 2018

[Pharo 7.0-dev] Build #1016: 14447-META-Case-restructure-Tests-and-test-packages

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

There is a new Pharo build available! The status of the build #1016 was: SUCCESS. The Pull Request #1495 was integrated: "14447-META-Case-restructure-Tests-and-test-packages" Pull request url: https://github.com/pharo-project/pharo/pull/1495 Issue Url: https://pharo.fogbugz.com/f/cases/14447 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 6, 2018

Re: [Pharo-dev] ApplicationSecurity Questions

by HernÃ¡n Morales Durand

Hi Sean 2018-06-05 0:17 GMT-03:00 Sean P. DeNigris <sean(a)clipperadams.com>: > I'm very excited about this library. I always wished for an off the shelf web > app security solution! Not sure if this is the right ML, but since the > library was announced hereâ¦ > > 1. I read that the project was ported to GH. While there is a baseline > there, there is also a configuration on GH, but (the weird part) - it still > points to StHub instead of loading the baseline from GH I just updated the README with the install script. Thanks for reporting. > 2. How does one actually use the library in practice e.g. for a web app with > protected content? The 3 blog posts cover adding a user, but I don't > understand how to tie AS in with say Seaside. Is there an example project > using it or some docs on that? > You can check a project making use of ApplicationSecurity here: http://www.smalltalkhub.com/#!/~hernan/IGEVET I still should test in a Pharo 6.x image but there is a Configuration which could work: ConfigurationOfIGEVETWebSite, it uses Iliad plus some extensions such as PureCSS, so it could take some time to load. Maybe I should sit down tomorrow and take some time to write documentation. Cheers, HernÃ¡n > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

June 6, 2018

Re: [Pharo-dev] [ANN] Epicea, Ombu and Hiedra packages have new "official" repository

by Marcus Denker

> On 5 Jun 2018, at 20:49, Martin Dias <tinchodias(a)gmail.com> wrote: > > On Tue, Jun 5, 2018 at 3:30 PM HernÃ¡n Morales Durand > <hernan.morales(a)gmail.com> wrote: >> What are Ombu and Hiedra? > > Hello HernÃ¡n, this is how I described them: > > Ombu: > "Epicea has a small subproject, named Ombu, which provides simple > persistence. By default, Ombu uses STON to write the events when they > are announced in the system." > ------- from http://smalltalkhub.com/#!/~MartinDias/Epicea > > Hiedra: > "It is a small Pharo project to visually connect items in a > history-like graph. It uses Athens, and provides support for Morphic > and Spec." > ------- from https://github.com/tinchodias/hiedra which is a repo that > I might close or should say in readme that it's not the official repo > > But not sure if I described correctly... in concrete, Hiedra is what's > used from Epicea Spec UI in a TableModel to draw the links between > epicea logs in the left panel. > We should add exactly those description as package level comments. https://pharo.fogbugz.com/f/cases/22079/package-comments-for-Ombu-and-Hiedra What I do not like is that the package name gives no clue what this is aboutâ¦ Not even the âneighbourhoodâ. E.g. it does not even get clear that Ombu and Epicea are relatedâ¦ But we have that problem with many packages. Marcus

June 6, 2018

Re: [Pharo-dev] [ANN] Epicea, Ombu and Hiedra packages have new "official" repository

by Marcus Denker

> On 5 Jun 2018, at 18:55, Martin Dias <tinchodias(a)gmail.com> wrote: > > On Tue, Jun 5, 2018 at 12:35 PM Cyril Ferlicot D. > <cyril.ferlicot(a)gmail.com> wrote: >>> >> >> Hello Martin, >> >> Thank you for the clarification. >> >> Can we start to change things in Epicea (like renaming tests packages to >> follow the convention) or do you still need to sync the Pharo version? >> >> Have a nice day. >> > > Yes, you can start. > > Could this be reopen? > https://github.com/pharo-project/pharo/pull/377 > but it was only for Ombu and don't know if it's outdated.. I would not re-open. This is very old. Even from before we moved to the new GIT format. Which means it can not be merged. Marcus

June 6, 2018

[Pharo 7.0-dev] Build #1015: 22065-add-a-factory-method-that-includes-classInstVarNames-for-stateful-traits

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

There is a new Pharo build available! The status of the build #1015 was: FAILURE. The Pull Request #1485 was integrated: "22065-add-a-factory-method-that-includes-classInstVarNames-for-stateful-traits" Pull request url: https://github.com/pharo-project/pharo/pull/1485 Issue Url: https://pharo.fogbugz.com/f/cases/22065 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 6, 2018

[Pharo 7.0-dev] Build #1014: 22078-Fix-randomly-failing-tests

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

There is a new Pharo build available! The status of the build #1014 was: SUCCESS. The Pull Request #1494 was integrated: "22078-Fix-randomly-failing-tests" Pull request url: https://github.com/pharo-project/pharo/pull/1494 Issue Url: https://pharo.fogbugz.com/f/cases/22078 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 6, 2018