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

Re: [Pharo-dev] [ANN] Pharo open documentation

by Norbert Hartl

Very good initiative! Did you talk about the catalog, too? This list somehow mirrors the catalog. And as it is done in markdown it does not easily work as a parsable document, does it? Norbert > Am 30.01.2019 um 15:00 schrieb Cyril Ferlicot <cyril.ferlicot(a)gmail.com>: > > Hi everyone! > > With some other members of the community we are proud to announce a > new effort on Pharo documentation. > > We launched an organization pharo-open-documentation which is a > user-maintained documentation related to Pharo environment, language, > and libraries. > > Currently it has three main projects: > - pharo-wiki : Wiki related to the Pharo programming language and environment. > - awesome-pharo : A collection of awesome Pharo libraries, tools, > frameworks and software. We want to make this project a reference in > https://github.com/sindresorhus/awesome > - awesome-pharo-ml : List of projects, books, booklets, papers, and > applications related to machine learning, AI, data science in Pharo. > > Contributions are welcomed! > > If you own a cool project in Pharo others could use in their own > projects, send us a PR to awesome-pharo! > If you have knowledge on Pharo or projects of Pharo, we would be glad > if you could contribute to the pharo-wiki! Don't forget to read the > contribution guidelines. ;) > > We opened a Twitter to announce new entries on the pharo-wiki. > > https://twitter.com/PharoOpen > > Have a nice day! > > -- > Cyril Ferlicot > https://ferlicot.fr >

Jan. 31, 2019

Re: [Pharo-dev] Contribute to pharo8.0 ?

by Pavel Krivanek

It is working now again as expected. The only difference is that you need to use "Github-Create new branch for issue..." instead of "Pharo-Create new branch for issue..." for the new issues reported on GitHub. -- Pavel st 30. 1. 2019 v 9:42 odesÃlatel Guillermo Polito <guillermopolito(a)gmail.com> napsal: > Hi, > > there is an issue for this problem, > > https://github.com/pharo-project/pharo/issues/2379 > > We have identified the cause, I'll propose a fix now > > On Wed, Jan 30, 2019 at 8:44 AM ducasse <stepharo(a)netcourrier.com> wrote: > >> > >> > There is currently a bug eating one character of the commit hash. So >> > Iceberg does not find the hash and thinks we need a fetch. So currently >> > we need to checkout Pharo8.0 in order to be in a good state :( >> >> OOPs is there a bug entry? >> > >> >> I also don't understand how to make an issue branch for >> >> >> >> https://github.com/pharo-project/pharo/issues/2395 >> >> >> >> Is it Iceberg > Pharo > Create new branch for issue or Iceberg > >> Github > Create new branch for issue ? >> > >> > Just create a branch and choose the option to create a branch from a >> > Github option. >> > >> > The other one was for Manuscript and is now useless for Pharo 8. I >> > opened an issue in Iceberg to remove it but I did not got the time to >> > contribute the change. >> > >> >> What is the difference ? >> >> What about the Remote ? >> >> Can I work with only an issue on GitHub ? >> >> >> > >> > Yes! >> > >> > What I am doing currently: >> > >> > - Open an issue XX >> > - Sync my fork Pharo8.0 branch via command line (This is optional and >> > can also be done in Pharo. I just do it via command line because I like >> > it better that way) >> >> how do you do it? Pull? >> >> > - Download a Pharo 8 image >> > - Checkout the Pharo8.0 branch to get in a clean state because of the >> > hash eating bug I mentioned earlier >> > - Create a new branch from a github issue of the pharo remote >> > - Do the changes and commit. I add `Fixes #XX` in the commit message to >> > close automatically the issue when the PR is merged. >> > - Push to my remote >> > - Open a PR against Pharo8.0 through Iceberg > GitHub > Create new pull >> > request >> >> and checkout the pharo 8 branch to fix the next one. >> > >> >> Is the documentation >> >> >> >> https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo >> >> >> >> really up to date ? >> >> >> > >> > No >> > >> > We should correct the hash eating bug before updating it I think. >> > >> >> Sven >> >> >> >> >> > >> > >> > -- >> > Cyril Ferlicot >> > https://ferlicot.fr >> > >> >> >> >> > > -- > > > > 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 >

Jan. 31, 2019

Re: [Pharo-dev] [ANN] Pharo open documentation

by Cyril Ferlicot D.

Le 30/01/2019 Ã 21:25, HernÃ¡n Morales Durand a Ã©critÂ : > Hi Cyril, > > Nice project! > I think you forgot to add the URL : > https://github.com/pharo-open-documentation/awesome-pharo > > Note: the Zinc entry has a reference to Cytoscape.js? > Good catch! Just an error of copy past when I reorganized the entries :) It should go at the end of TelescopeCytoscape line. Thank you. > Cheers, > > HernÃ¡n > -- Cyril Ferlicot https://ferlicot.fr

Jan. 30, 2019

Re: [Pharo-dev] [ANN] Pharo open documentation

by ducasse

I fix it in the pharoweekly blog post :) > On 30 Jan 2019, at 21:27, Julien <julien.delplanque(a)inria.fr> wrote: > > Looks like an error. > > Will fix it. > > Julien > > --- > Julien Delplanque > Doctorant Ã lâUniversitÃ© de Lille > 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 30 janv. 2019 Ã 21:25, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com <mailto:hernan.morales@gmail.com>> a Ã©crit : >> >> Hi Cyril, >> >> Nice project! >> I think you forgot to add the URL : https://github.com/pharo-open-documentation/awesome-pharo <https://github.com/pharo-open-documentation/awesome-pharo> >> >> Note: the Zinc entry has a reference to Cytoscape.js? >> >> Cheers, >> >> HernÃ¡n >> >> >> >> El miÃ©., 30 ene. 2019 a las 11:01, Cyril Ferlicot (<cyril.ferlicot(a)gmail.com <mailto:cyril.ferlicot@gmail.com>>) escribiÃ³: >> Hi everyone! >> >> With some other members of the community we are proud to announce a >> new effort on Pharo documentation. >> >> We launched an organization pharo-open-documentation which is a >> user-maintained documentation related to Pharo environment, language, >> and libraries. >> >> Currently it has three main projects: >> - pharo-wiki : Wiki related to the Pharo programming language and environment. >> - awesome-pharo : A collection of awesome Pharo libraries, tools, >> frameworks and software. We want to make this project a reference in >> https://github.com/sindresorhus/awesome <https://github.com/sindresorhus/awesome> >> - awesome-pharo-ml : List of projects, books, booklets, papers, and >> applications related to machine learning, AI, data science in Pharo. >> >> Contributions are welcomed! >> >> If you own a cool project in Pharo others could use in their own >> projects, send us a PR to awesome-pharo! >> If you have knowledge on Pharo or projects of Pharo, we would be glad >> if you could contribute to the pharo-wiki! Don't forget to read the >> contribution guidelines. ;) >> >> We opened a Twitter to announce new entries on the pharo-wiki. >> >> https://twitter.com/PharoOpen <https://twitter.com/PharoOpen> >> >> Have a nice day! >> >> -- >> Cyril Ferlicot >> https://ferlicot.fr <https://ferlicot.fr/> >> >

Jan. 30, 2019

Re: [Pharo-dev] [ANN] Pharo open documentation

by Julien

Looks like an error. Will fix it. Julien --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille 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 30 janv. 2019 Ã 21:25, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> a Ã©crit : > > Hi Cyril, > > Nice project! > I think you forgot to add the URL : https://github.com/pharo-open-documentation/awesome-pharo <https://github.com/pharo-open-documentation/awesome-pharo> > > Note: the Zinc entry has a reference to Cytoscape.js? > > Cheers, > > HernÃ¡n > > > > El miÃ©., 30 ene. 2019 a las 11:01, Cyril Ferlicot (<cyril.ferlicot(a)gmail.com <mailto:cyril.ferlicot@gmail.com>>) escribiÃ³: > Hi everyone! > > With some other members of the community we are proud to announce a > new effort on Pharo documentation. > > We launched an organization pharo-open-documentation which is a > user-maintained documentation related to Pharo environment, language, > and libraries. > > Currently it has three main projects: > - pharo-wiki : Wiki related to the Pharo programming language and environment. > - awesome-pharo : A collection of awesome Pharo libraries, tools, > frameworks and software. We want to make this project a reference in > https://github.com/sindresorhus/awesome <https://github.com/sindresorhus/awesome> > - awesome-pharo-ml : List of projects, books, booklets, papers, and > applications related to machine learning, AI, data science in Pharo. > > Contributions are welcomed! > > If you own a cool project in Pharo others could use in their own > projects, send us a PR to awesome-pharo! > If you have knowledge on Pharo or projects of Pharo, we would be glad > if you could contribute to the pharo-wiki! Don't forget to read the > contribution guidelines. ;) > > We opened a Twitter to announce new entries on the pharo-wiki. > > https://twitter.com/PharoOpen <https://twitter.com/PharoOpen> > > Have a nice day! > > -- > Cyril Ferlicot > https://ferlicot.fr <https://ferlicot.fr/> >

Jan. 30, 2019

Re: [Pharo-dev] [ANN] Pharo open documentation

by HernÃ¡n Morales Durand

Hi Cyril, Nice project! I think you forgot to add the URL : https://github.com/pharo-open-documentation/awesome-pharo Note: the Zinc entry has a reference to Cytoscape.js? Cheers, HernÃ¡n El miÃ©., 30 ene. 2019 a las 11:01, Cyril Ferlicot (<cyril.ferlicot(a)gmail.com>) escribiÃ³: > Hi everyone! > > With some other members of the community we are proud to announce a > new effort on Pharo documentation. > > We launched an organization pharo-open-documentation which is a > user-maintained documentation related to Pharo environment, language, > and libraries. > > Currently it has three main projects: > - pharo-wiki : Wiki related to the Pharo programming language and > environment. > - awesome-pharo : A collection of awesome Pharo libraries, tools, > frameworks and software. We want to make this project a reference in > https://github.com/sindresorhus/awesome > - awesome-pharo-ml : List of projects, books, booklets, papers, and > applications related to machine learning, AI, data science in Pharo. > > Contributions are welcomed! > > If you own a cool project in Pharo others could use in their own > projects, send us a PR to awesome-pharo! > If you have knowledge on Pharo or projects of Pharo, we would be glad > if you could contribute to the pharo-wiki! Don't forget to read the > contribution guidelines. ;) > > We opened a Twitter to announce new entries on the pharo-wiki. > > https://twitter.com/PharoOpen > > Have a nice day! > > -- > Cyril Ferlicot > https://ferlicot.fr > >

Jan. 30, 2019

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

by Norbert Hartl

> Am 30.01.2019 um 20:23 schrieb ducasse <stepharo(a)netcourrier.com>: > > it means this is a call for fork :) > No! A fork from something not github to github is contraproductive. Norbert >>> On 30 Jan 2019, at 16:58, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>> >>> >>> Am 30.01.2019 um 16:13 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >>> >>> >>> >>>> On 3 Oct 2018, at 07:43, monty <monty2(a)programmer.net> wrote: >>>> >>>> I am the principal maintainer of those projects, but any PharoExtras dev can contribute. And the blog below (which I plan on updating) provides additional information on them. >>> >>> Has there been any progress in this area ? >>> >>> It would be really great if this important project moved to GitHub. >>> >> +100 >> >> Norbert >

Jan. 30, 2019

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

by ducasse

it means this is a call for fork :) > On 30 Jan 2019, at 16:58, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: > > > >> Am 30.01.2019 um 16:13 schrieb Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>>: >> >> >> >>> On 3 Oct 2018, at 07:43, monty <monty2(a)programmer.net <mailto:monty2@programmer.net>> wrote: >>> >>> I am the principal maintainer of those projects, but any PharoExtras dev can contribute. And the blog below (which I plan on updating) provides additional information on them. >> >> Has there been any progress in this area ? >> >> It would be really great if this important project moved to GitHub. >> > +100 > > Norbert

Jan. 30, 2019

Re: [Pharo-dev] [ANN] Pharo open documentation

by ducasse

super nice effort!!! > On 30 Jan 2019, at 15:00, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > Hi everyone! > > With some other members of the community we are proud to announce a > new effort on Pharo documentation. > > We launched an organization pharo-open-documentation which is a > user-maintained documentation related to Pharo environment, language, > and libraries. > > Currently it has three main projects: > - pharo-wiki : Wiki related to the Pharo programming language and environment. > - awesome-pharo : A collection of awesome Pharo libraries, tools, > frameworks and software. We want to make this project a reference in > https://github.com/sindresorhus/awesome > - awesome-pharo-ml : List of projects, books, booklets, papers, and > applications related to machine learning, AI, data science in Pharo. > > Contributions are welcomed! > > If you own a cool project in Pharo others could use in their own > projects, send us a PR to awesome-pharo! > If you have knowledge on Pharo or projects of Pharo, we would be glad > if you could contribute to the pharo-wiki! Don't forget to read the > contribution guidelines. ;) > > We opened a Twitter to announce new entries on the pharo-wiki. > > https://twitter.com/PharoOpen > > Have a nice day! > > -- > Cyril Ferlicot > https://ferlicot.fr >

Jan. 30, 2019

Debugger opening on user halt and not Object>>halt

by Thomas Dupriez

Hello, Does someone know which is the code responsible for the debugger opening on the halt of the user instead of Object>>halt (see picture)? It's neat but it's not the regular behaviour so I'm guessing it is handled somewhere specifically for halt messages? Thomas

Jan. 30, 2019