January 2019 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] naming convention for pharo-vm/lib/pharo/* directory?

by Nicolas Cellier

I'm afraid it also depends on the overly complex rules burried deep inside the VM... It would be a good thing to try and document it. And if we can't reasonably document it, then we might want to open an issue on opensmalltalk. Le ven. 25 janv. 2019 Ã 01:51, Dale Henrichs < dale.henrichs(a)gemtalksystems.com> a Ã©crit : > I am in the process of porting the GemStone-GCI[1] project to Pharo6.1 > (32 bit) and Pharo7.0 (64 bit) and I'm curious what the naming > convention for the library directories are. > > For Pharo5.0 and earlier, I copied my 32 bit gemstone gci library files > (.so on linux) into the pharo-vm directory. > > For Pharo6.1 I just figured out that I need to copy the gci library > files into the pharo-vm/lib/pharo/5.0-201806281256 directory ... at list > the libraries are found when I do so? > > I would like to be able to write a bash script that copies the gci > library files into the proper directory, but the directory for the > Pharo6.1 vm looks like some kind of magic number and I assume that > different builds of the 6.1 vm could have different names and possibly > even multiple directories under pharo-vm/lib/pharo/? > > I haven't looked at Pharo7.0 yet to see what it's pharo-vm directory > structure looks like... > > A pointer to where the naming conventions for these directories is > described for Pharo6.x, Pharo7.x and Pharo8.x would be greatly > appreciated ... would also be nice if the error message for the "module > not found" error could be a bit more descriptive as well ... > > Thanks, > > Dale > > [1] https://github.com/GsDevKit/GemStone-GCI > > >

Jan. 25, 2019

[Pharo 8.0] Build #23: 2302-Context comment typos

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

There is a new Pharo build available! The status of the build #23 was: FAILURE. The Pull Request #2286 was integrated: "2302-Context comment typos" Pull request url: https://github.com/pharo-project/pharo/pull/2286 Issue Url: https://pharo.fogbugz.com/f/cases/patch Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 25, 2019

naming convention for pharo-vm/lib/pharo/* directory?

by Dale Henrichs

I am in the process of porting the GemStone-GCI[1] project to Pharo6.1 (32 bit) and Pharo7.0 (64 bit) and I'm curious what the naming convention for the library directories are. For Pharo5.0 and earlier, I copied my 32 bit gemstone gci library files (.so on linux) into the pharo-vm directory. For Pharo6.1 I just figured out that I need to copy the gci library files into the pharo-vm/lib/pharo/5.0-201806281256 directory ... at list the libraries are found when I do so? I would like to be able to write a bash script that copies the gci library files into the proper directory, but the directory for the Pharo6.1 vm looks like some kind of magic number and I assume that different builds of the 6.1 vm could have different names and possibly even multiple directories under pharo-vm/lib/pharo/? I haven't looked at Pharo7.0 yet to see what it's pharo-vm directory structure looks like... A pointer to where the naming conventions for these directories is described for Pharo6.x, Pharo7.x and Pharo8.x would be greatly appreciated ... would also be nice if the error message for the "module not found" error could be a bit more descriptive as well ... Thanks, Dale [1] https://github.com/GsDevKit/GemStone-GCI

Jan. 25, 2019

Re: [Pharo-dev] Pharo 7 RC - Changing to larger font breaks scrolling in code browsers

by Sven Van Caekenberghe

I am still having this issue in Pharo 7.0.1 as released and downloaded today. The top menu bar also does not listen to font changes. > On 12 Nov 2018, at 19:03, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Sven, > > On Mon, 12 Nov 2018 at 17:08, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Hi, >> >> Here is an annoying usability bug that I am experiencing and that sometimes drives me nuts. It has been there a while. >> >> Take a stock Pharo 7 RC image and don't change any setting. Browse the method #testAsDateAndTime as implemented by DateAndTimeTest. This is a (too) long (test) method. Any long method will do. >> >> You can scroll it fine in both the implementors and well as in the full browser. >> >> Now switch to 'Medium' sized 'predefined style' Standard Fonts using the Settings Browser. >> >> It is now close to impossible to scroll in the implementors or the full browser: not using the scroll bar arrows, not dragging the scroll bar, not clicking above/below the scroll bar, not using the scroll gesture (track pad, mouse pad, wheel), not using cursor keys inside the editor. Scrolling seems to happen automatically and goes on until the top or bottom. >> >> Can anyone replicate this ? > > On Ubuntu 16.04 with recent images I can reproduce the behaviour, with > the following additional observations: > > - It doesn't seem to matter whether true type fonts are enabled or not. > - After increasing the font size to medium and opening the browser: > -- The (vertical) scroll bar isn't visible, it is possible to scroll > using the mouse wheel or cursor keys. > -- Increasing the width of the browser so the scroll bar is visible, > but not clicking on the scroll bar, scrolling using the mouse wheel or > cursor keys still works. > -- Once the scroll bar has been clicked on it fails as you describe. > > HTH, > Alistair.

Jan. 24, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

by Eric Gade

Which is now the canonical place to seek out these issues/bugs: manuscript or GitHub? On Thu, Jan 24, 2019, 14:37 Torsten Bergmann <astares(a)gmx.de wrote: > Hi, > > it's a nice release yes - and the best we ever provided indeed. I'm really > happy too that P7 image is an > official release now. > > > But still: > ========== > > In a post [1] in November 2017 I brought up the topic again to "increase > the quality level in Pharo 7 and onwards". > > With 762 commits [2] for Pharo 7 I devoted a lot of time in fixing often > simple and trivial things just to clean up > comments, code, typos, packages, manifests, tests and so on. > > Many others did the same and supported these cleaning efforts. This helped > adding a few more release tests to keep the > quality bar on the level reached. Special thanks to Marcus, Esteban, and > many others who helped reviewing, fighting a > shaky CI server, integrating quickly and so on ... > > Still THIS IS NOT FINISHED ... and it would be really help if more people > would participate in the cleaning or fixing bugs. > Also many external packages now need some love to work with Pharo 7. > > We have a large community with many, many users - but still only a few > contribute to the core system. > > I wonder why and would like to know: > - Is it due to the switch to git ? > - Is is due to the new contribution process? > - Is it for other reasons? > > Remember: Pharo is yours and even small steps could make a difference. So > please join! > > Thanks > T. > > > [1] > http://forum.world.st/Pharo-Quality-raising-the-quality-level-in-Pharo-7-an… > [2] https://github.com/pharo-project/pharo/graphs/contributors > > >

Jan. 24, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

by Torsten Bergmann

Hi, it's a nice release yes - and the best we ever provided indeed. I'm really happy too that P7 image is an official release now. But still: ========== In a post [1] in November 2017 I brought up the topic again to "increase the quality level in Pharo 7 and onwards". With 762 commits [2] for Pharo 7 I devoted a lot of time in fixing often simple and trivial things just to clean up comments, code, typos, packages, manifests, tests and so on. Many others did the same and supported these cleaning efforts. This helped adding a few more release tests to keep the quality bar on the level reached. Special thanks to Marcus, Esteban, and many others who helped reviewing, fighting a shaky CI server, integrating quickly and so on ... Still THIS IS NOT FINISHED ... and it would be really help if more people would participate in the cleaning or fixing bugs. Also many external packages now need some love to work with Pharo 7. We have a large community with many, many users - but still only a few contribute to the core system. I wonder why and would like to know: - Is it due to the switch to git ? - Is is due to the new contribution process? - Is it for other reasons? Remember: Pharo is yours and even small steps could make a difference. So please join! Thanks T. [1] http://forum.world.st/Pharo-Quality-raising-the-quality-level-in-Pharo-7-an… [2] https://github.com/pharo-project/pharo/graphs/contributors

Jan. 24, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

by Hilaire

It can't be more clearly articulated. Negative feedbacks are more valuable than positive feedbacks. Hilaire Le 23/01/2019 Ã 08:49, Norbert Hartl a Ã©critÂ : > Well, Iâm always amazed how negative people are. But on the other hand there is some truth in there. If we donât focus on how people encounter pharo the first time it is not getting easier. -- Dr. Geo http://drgeo.eu

Jan. 24, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

by Sven Van Caekenberghe

> On 24 Jan 2019, at 12:26, phil(a)highoctane.be wrote: > > > > On Thu, Jan 24, 2019 at 11:17 AM Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > >> On 24 Jan 2019, at 09:23, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >> >> >> Just want to congratulate for the big achievements in this new release. >> I am trying it right now and it looks very stable! >> Great work guys! > > :) > Just for the record, Iâm using same image since 3 monts (and to do some very heavy work). > And image has not grown more than normal, and everything still works smooth. > > So yes, bugs and limitations aside (there will always be one and the other), this may be the most stable version we have made since P3 :P > > Wonderful. Really. > > Stability is key indeed. > > Now, how do you deal with freezing images? Because let's be honest, this happens and is super frustrating. > > As the lead engineer on Pharo, you have for sure interesting tricks on that front. > > I have been also frustrated by Epica and code recovery because things happened that were "weird" (for the lack of a better factual word). > Tricks on that as well? Problems do happen for sure. But when Esteban or most Pharo developers are talking about 'Pharo' we usually mean the latest version (P7 right now). Epicea most probably improved quite a bit since it first appeared several versions ago, same for Iceberg, same for Calypso. > Phil > > Esteban > >> Cheers, >> >> HernÃ¡n >> >> >> El mar., 22 ene. 2019 a las 10:37, Esteban Lorenzano (<estebanlm(a)gmail.com>) escribiÃ³: >> Pharo 7.0 released! >> =============== >> >> Dear World and dynamic language lovers: >> >> The time has come for Pharo 7.0! >> >> Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. >> >> >> <pastedGraphic.png> >> >> >> This is our most significant release yet. Here are the key highlights of this release: >> >> â¢ Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability. The 64-bit version is now recommended for Linux and Mac, and is provided as technical preview for Windows. >> â¢ Pharo comes with a new version of the PharoLauncher (https://pharo.org/download) THE tool to manage your distributions (access to regular versions, jenkins builds, and older versions). >> â¢ Pharo build has a fully new build process that supports its full bootstrap from sources. This will enable the production to specific (micro) images. >> â¢ Iceberg, the git client for Pharo has been significantly improved, and is the default CMS. >> â¢ Calypso, the angular stone of PharoThings, is the new system Pharo browser. It replaces Nautilus and brings better remote working and more advanced browsing capabilities. >> â¢ IoT is now an important part of Pharo. Installing PharoThings (https://github.com/pharo-iot/PharoThings) provides an impressive amount of tools to develop applications in small devices. >> â¢ The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved to work properly on Windows 64-bit. >> >> Pharo 70âs new infrastructure and process set the stage for a new generation of version. >> The visibility of GitHub combined with the powerful tools that have been validated with more than one year of beta testing is massively pay off. >> >> These are just the more prominent highlights, but the details are just as important. >> >> We have closed a massive amount of issues: 2142 issues! (A comprehensive changelog can be found at: https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo70Change…) >> >> While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 7.0 image was contributed by more than 75 people. >> >> Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release: >> >> Gabriel Omar Cotelli, Gustavo Santos, Marcus Denker, Torsten Bergmann, Esteban Lorenzano, Bernardo Ezequiel Contreras, Guille Polito, Pablo Tesone, Yoan Geran, StÃ©phane Ducasse, Cyril Ferlicot, Vincent Blondeau, Denis Kudriashov, Julien Delplanque, Tim Mackinnon, Max Leske, Andrew P. Black, Tomohiro Oda, ClÃ©ment BÃ©ra, Ben Coman, Eric Gade, Yuriy Tymchuk, Nicolas Cellier, Biyalou-Sama Asbath, Myroslava, Sean DeNigris, Juraj Kubelka, Noury Bouraqadi, Holger Freyther, Geoff Reedy, Norbert Hartl, Paul DeBruicker, Alain Plantec, MartÃn Dias, Peter Uhnak, Tomohiro Oda, BenoÃ®t Verhaeghe, Santiago Bragagnolo, Wouter van Zuilen, Bernhard Pieber, Damien Pollet, Geoff Hill, Hans-Martin Mosner, Ronie Salgado, Philippe Back, Aliaksei Syrel, Dayne Guerra, Rafael Luque, Serge Stinckwich, Vincent Aranega, HernÃ¡n Morales Durand, Petr Fischer, Rajula Vineet Reddy, Alexandre Bergel, Esteban A. Maringolo, Jan BlizniÄenko, Johan Brichau, Luc Fabresse, Quentin Ducasse, SÃ©bastien Roccaserra, Stephan Eggermont, Sven Van Caekenberghe, Takano Mitsuhiro, Pavel Krivanek, Allex Oliveira, Christophe Demarey, Lionel Akue, Nicolai Hess, Martin McClure, Alistair Grant, Pierre Tsapliayev, Milton Mamani, Matteo Marra, Thomas Dupriez, Asbathou Biyalou-Sama. >> (If you contributed with Pharo 7.0 development in any way and we missed your name, please send us a mail and we will add you). >> >> Enjoy! >> The Pharo Team >> >> Try Pharo: http://pharo.org/download >> Learn Pharo: http://pharo.org/documentation

Jan. 24, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

by phil＠highoctane.be

On Thu, Jan 24, 2019 at 11:17 AM Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > On 24 Jan 2019, at 09:23, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> > wrote: > > > Just want to congratulate for the big achievements in this new release. > I am trying it right now and it looks very stable! > Great work guys! > > > :) > Just for the record, Iâm using same image since 3 monts (and to do some > very heavy work). > And image has not grown more than normal, and everything still works > smooth. > > So yes, bugs and limitations aside (there will always be one and the > other), this may be the most stable version we have made since P3 :P > Wonderful. Really. Stability is key indeed. Now, how do you deal with freezing images? Because let's be honest, this happens and is super frustrating. As the lead engineer on Pharo, you have for sure interesting tricks on that front. I have been also frustrated by Epica and code recovery because things happened that were "weird" (for the lack of a better factual word). Tricks on that as well? Phil > > Esteban > > Cheers, > > HernÃ¡n > > > El mar., 22 ene. 2019 a las 10:37, Esteban Lorenzano (<estebanlm(a)gmail.com>) > escribiÃ³: > >> Pharo 7.0 released! >> =============== >> >> Dear World and dynamic language lovers: >> >> The time has come for Pharo 7.0! >> >> Pharo is a pure object-oriented programming language and a powerful >> environment, focused on simplicity and immediate feedback. >> >> >> <pastedGraphic.png> >> >> >> This is our most significant release yet. Here are the key highlights of >> this release: >> >> â¢ Pharo is now provided in 64-bit version in Linux and OSX and brings >> even better performance and stability. The 64-bit version is >> now recommended for Linux and Mac, and is provided as technical preview for >> Windows. >> â¢ Pharo comes with a new version of the PharoLauncher ( >> https://pharo.org/download) THE tool to manage your distributions >> (access to regular versions, jenkins builds, and older versions). >> â¢ Pharo build has a fully new build process that supports its full >> bootstrap from sources. This will enable the production to specific (micro) >> images. >> â¢ Iceberg, the git client for Pharo has been significantly improved, and >> is the default CMS. >> â¢ Calypso, the angular stone of PharoThings, is the new system Pharo >> browser. It replaces Nautilus and brings better remote working and more >> advanced browsing capabilities. >> â¢ IoT is now an important part of Pharo. Installing PharoThings ( >> https://github.com/pharo-iot/PharoThings) provides an impressive amount >> of tools to develop applications in small devices. >> â¢ The unified foreign function interface (UnifiedFFI) for interfacing >> with the outside world is significantly improved to work properly on >> Windows 64-bit. >> >> Pharo 70âs new infrastructure and process set the stage for a new >> generation of version. >> The visibility of GitHub combined with the powerful tools that have been >> validated with more than one year of beta testing is massively pay off. >> >> These are just the more prominent highlights, but the details are just as >> important. >> >> We have closed a massive amount of issues: 2142 issues! (A comprehensive >> changelog can be found at: >> https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo70Change… >> ). >> >> While the technical improvements are significant, still the most >> impressive fact is that the new code that got in the main Pharo 7.0 image >> was contributed by more than 75 people. >> >> Pharo is more than code. It is an exciting project involving energetic >> people. We thank all the contributors of this release: >> >> Gabriel Omar Cotelli, Gustavo Santos, Marcus Denker, Torsten Bergmann, >> Esteban Lorenzano, Bernardo Ezequiel Contreras, Guille Polito, Pablo >> Tesone, Yoan Geran, StÃ©phane Ducasse, Cyril Ferlicot, Vincent Blondeau, >> Denis Kudriashov, Julien Delplanque, Tim Mackinnon, Max Leske, Andrew P. >> Black, Tomohiro Oda, ClÃ©ment BÃ©ra, Ben Coman, Eric Gade, Yuriy Tymchuk, >> Nicolas Cellier, Biyalou-Sama Asbath, Myroslava, Sean DeNigris, Juraj >> Kubelka, Noury Bouraqadi, Holger Freyther, Geoff Reedy, Norbert Hartl, Paul >> DeBruicker, Alain Plantec, MartÃn Dias, Peter Uhnak, Tomohiro Oda, BenoÃ®t >> Verhaeghe, Santiago Bragagnolo, Wouter van Zuilen, Bernhard Pieber, Damien >> Pollet, Geoff Hill, Hans-Martin Mosner, Ronie Salgado, Philippe Back, >> Aliaksei Syrel, Dayne Guerra, Rafael Luque, Serge Stinckwich, Vincent >> Aranega, HernÃ¡n Morales Durand, Petr Fischer, Rajula Vineet Reddy, >> Alexandre Bergel, Esteban A. Maringolo, Jan BlizniÄenko, Johan Brichau, Luc >> Fabresse, Quentin Ducasse, SÃ©bastien Roccaserra, Stephan Eggermont, Sven >> Van Caekenberghe, Takano Mitsuhiro, Pavel Krivanek, Allex Oliveira, >> Christophe Demarey, Lionel Akue, Nicolai Hess, Martin McClure, Alistair >> Grant, Pierre Tsapliayev, Milton Mamani, Matteo Marra, Thomas Dupriez, >> Asbathou Biyalou-Sama. >> (If you contributed with Pharo 7.0 development in any way and we missed >> your name, please send us a mail and we will add you). >> >> Enjoy! >> The Pharo Team >> >> Try Pharo: http://pharo.org/download >> Learn Pharo: http://pharo.org/documentation >> >> >

Jan. 24, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

by Esteban Lorenzano

> On 24 Jan 2019, at 09:23, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > > Just want to congratulate for the big achievements in this new release. > I am trying it right now and it looks very stable! > Great work guys! :) Just for the record, Iâm using same image since 3 monts (and to do some very heavy work). And image has not grown more than normal, and everything still works smooth. So yes, bugs and limitations aside (there will always be one and the other), this may be the most stable version we have made since P3 :P Esteban > Cheers, > > HernÃ¡n > > > El mar., 22 ene. 2019 a las 10:37, Esteban Lorenzano (<estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>) escribiÃ³: > Pharo 7.0 released! > =============== > > Dear World and dynamic language lovers: > > The time has come for Pharo 7.0! > > Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. > > > <pastedGraphic.png> > > > This is our most significant release yet. Here are the key highlights of this release: > > â¢ Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability. The 64-bit version is now recommended for Linux and Mac, and is provided as technical preview for Windows. > â¢ Pharo comes with a new version of the PharoLauncher (https://pharo.org/download <https://pharo.org/download>): THE tool to manage your distributions (access to regular versions, jenkins builds, and older versions). > â¢ Pharo build has a fully new build process that supports its full bootstrap from sources. This will enable the production to specific (micro) images. > â¢ Iceberg, the git client for Pharo has been significantly improved, and is the default CMS. > â¢ Calypso, the angular stone of PharoThings, is the new system Pharo browser. It replaces Nautilus and brings better remote working and more advanced browsing capabilities. > â¢ IoT is now an important part of Pharo. Installing PharoThings (https://github.com/pharo-iot/PharoThings <https://github.com/pharo-iot/PharoThings>) provides an impressive amount of tools to develop applications in small devices. > â¢ The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved to work properly on Windows 64-bit. > > Pharo 70âs new infrastructure and process set the stage for a new generation of version. > The visibility of GitHub combined with the powerful tools that have been validated with more than one year of beta testing is massively pay off. > > These are just the more prominent highlights, but the details are just as important. > > We have closed a massive amount of issues: 2142 issues! (A comprehensive changelog can be found at: https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo70Change… <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo70Change…>). > > While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 7.0 image was contributed by more than 75 people. > > Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release: > > Gabriel Omar Cotelli, Gustavo Santos, Marcus Denker, Torsten Bergmann, Esteban Lorenzano, Bernardo Ezequiel Contreras, Guille Polito, Pablo Tesone, Yoan Geran, StÃ©phane Ducasse, Cyril Ferlicot, Vincent Blondeau, Denis Kudriashov, Julien Delplanque, Tim Mackinnon, Max Leske, Andrew P. Black, Tomohiro Oda, ClÃ©ment BÃ©ra, Ben Coman, Eric Gade, Yuriy Tymchuk, Nicolas Cellier, Biyalou-Sama Asbath, Myroslava, Sean DeNigris, Juraj Kubelka, Noury Bouraqadi, Holger Freyther, Geoff Reedy, Norbert Hartl, Paul DeBruicker, Alain Plantec, MartÃn Dias, Peter Uhnak, Tomohiro Oda, BenoÃ®t Verhaeghe, Santiago Bragagnolo, Wouter van Zuilen, Bernhard Pieber, Damien Pollet, Geoff Hill, Hans-Martin Mosner, Ronie Salgado, Philippe Back, Aliaksei Syrel, Dayne Guerra, Rafael Luque, Serge Stinckwich, Vincent Aranega, HernÃ¡n Morales Durand, Petr Fischer, Rajula Vineet Reddy, Alexandre Bergel, Esteban A. Maringolo, Jan BlizniÄenko, Johan Brichau, Luc Fabresse, Quentin Ducasse, SÃ©bastien Roccaserra, Stephan Eggermont, Sven Van Caekenberghe, Takano Mitsuhiro, Pavel Krivanek, Allex Oliveira, Christophe Demarey, Lionel Akue, Nicolai Hess, Martin McClure, Alistair Grant, Pierre Tsapliayev, Milton Mamani, Matteo Marra, Thomas Dupriez, Asbathou Biyalou-Sama. > (If you contributed with Pharo 7.0 development in any way and we missed your name, please send us a mail and we will add you). > > Enjoy! > The Pharo Team > > Try Pharo: http://pharo.org/download <http://pharo.org/download> > Learn Pharo: http://pharo.org/documentation <http://pharo.org/documentation> >

Jan. 24, 2019