April 2020 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Pharo.org is down?

by Christophe Demarey

Yes, was down. I restarted it. > Le 18 avr. 2020 Ã 14:07, Tim Mackinnon <tim(a)testit.works> a Ã©crit : > > Is there planned maintenance on pharo.org? Is been down for a while todayâ¦.

April 18, 2020

Re: [Pharo-users] [Pharo-dev] [SPAM] Re: [ANN] Pharo Launcher 2.0 released!

by Esteban Maringolo

Thanks, I will check it as soon as Pharo.org gets back online! [1] https://downforeveryoneorjustme.com/pharo.org Esteban A. Maringolo On Sat, Apr 18, 2020 at 10:48 AM Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > > Hi Graham, > > > Le 18 avr. 2020 Ã 11:30, Graham McLeod <graham(a)inspired.org> a Ã©crit : > > Hi > > This looks like a major update with some very welcome features and improved UI. > Very welcome and thanks for the work! > > One item I would like to see is a mention in the help on implications of upgrading from the existing > Pharo launcher. Bit nervous to install when I don't know what will become of existing configurations in the old one. > I am assuming that the new one is independent and will simply start off blank. It would be nice to have this tackled in the > documentation. Maybe a short section on "Moving your configurations / images from the old Launcher Â». > > > Yes, youâre right! > Pharo Launcher is mostly compatible with the previous one. > When using Pharo Launcher 2.0, image metadata will be converted from the old format to the new one. > I added an upgrade section on Pharo Launcher documentation: https://pharo-project.github.io/pharo-launcher/installation/#upgrade-notes > > Tell me if this is enough. > Regards, > Christophe

April 18, 2020

Re: [Pharo-users] Rosetta Code

by Richard O'Keefe

I've tackled more than 600 of the RosettaCode problems in Smalltalk. Unfortunately, this was done as exercises in developing my own Smalltalk system. If anyone would like to have a zip file to serve as a shortcut for developing Pharo versions, you'd be very welcome. On Fri, 17 Apr 2020 at 21:31, Steffen MÃ¤rcker <merkste(a)web.de> wrote: > > Hi, > > some of you might have hear of Rosetta Code, a Wiki that presents > solutions to standard programming tasks in various languages. I figured > that in many categories no Smalltalk/Pharo solutions are shown. Maybe we > can contribute some pieces from time to time? I started with the following: > > https://rosettacode.org/wiki/Tree_traversal#Smalltalk > > Your comments are welcome. > > Best, Steffen >

April 18, 2020

Re: [Pharo-users] [Pharo-dev] [SPAM] Re: [ANN] Pharo Launcher 2.0 released!

by Christophe Demarey

Hi Graham, > Le 18 avr. 2020 Ã 11:30, Graham McLeod <graham(a)inspired.org> a Ã©crit : > > Hi > > This looks like a major update with some very welcome features and improved UI. > Very welcome and thanks for the work! > > One item I would like to see is a mention in the help on implications of upgrading from the existing > Pharo launcher. Bit nervous to install when I don't know what will become of existing configurations in the old one. > I am assuming that the new one is independent and will simply start off blank. It would be nice to have this tackled in the > documentation. Maybe a short section on "Moving your configurations / images from the old Launcher Â». Yes, youâre right! Pharo Launcher is mostly compatible with the previous one. When using Pharo Launcher 2.0, image metadata will be converted from the old format to the new one. I added an upgrade section on Pharo Launcher documentation: https://pharo-project.github.io/pharo-launcher/installation/#upgrade-notes Tell me if this is enough. Regards, Christophe

April 18, 2020

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo Launcher 2.0 released!

by Sven Van Caekenberghe

> On 18 Apr 2020, at 10:40, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > Super cool > Thanks a lot christophe for your effort. > PharoLauncher changes our life. +10 > S. > >> On 17 Apr 2020, at 18:08, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: >> >> Hi all, >> >> Pharo Launcher 2.0 has just been released! It is available from http://pharo.org/download. >> >> This new version introduces major changes: >> â¢ The UI has been fully rewritten using the new Spec2 framework and the Commander2 library. UI has been revamped to increase usability, especially for newcomers. The main window is now composed of a toolbar and the list of images. The template list is now available when clicking on the new image button. >> â¢ Documentation web site : All Pharo Launcher features are now explained in the new documentation available at https://pharo-project.github.io/pharo-launcher. You can contribute easily by clicking the *edit on GitHub* button. >> â¢ You can now have many launch configurations for an image (VM to use, vm and image arguments). It means you can use headless Pharo VM from Pharo Launcher. >> â¢ When creating a new image, you can specify an initialisation script that will be run once at the first image launch. It is useful to load your project code in a stock Pharo image for example. See https://pharo-project.github.io/pharo-launcher/create-images/#image-initial… >> â¢ You can now define your own template sources in addition to official sources (see https://pharo-project.github.io/pharo-launcher/templates/#create-your-own-l…) including authenticated sources. >> â¢ Improved image metadata. Pharo Launcher now manages all image metadata in a single STON file (including description, Pharo version). >> >> Big thanks to all contributors, including issue reports. It is also the opportunity to thanks Damien Cassou, the original author of Pharo Launcher. >> >> Here is the changelog: >> Pharo Launcher v2.0 >> >> The list of closed issue is too long (68) to be listed but you can browse it here: https://github.com/pharo-project/pharo-launcher/issues?q=is%3Aissue+is%3Acl… >> Here are some highlights: >> New features: >> >> â¢ Documentation web site >> â¢ Image initialisation script >> â¢ Launch configurations, headless VM support >> â¢ User template file in addition to the official template file >> â¢ Jenkins server template now support pipeline projects >> â¢ Support of private Jenkins server >> â¢ Support of authenticated HTTP server >> Improvements: >> >> â¢ Monitoring of image launch failures to give back the error message (if any) >> â¢ Newly created image is automatically selected in the image list >> â¢ Allow to set image description at creation time >> â¢ Better error management (you will have the choice to ignore them or debug them) >> â¢ Add a poor version column in image list >> â¢ Speedup (especially when image repository has a lot of images) >> >> Bug fixes: >> >> â¢ Fix use of system unzip on Windows >> >> Regards, >> The Pharo team. > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr / http://www.pharo.org > 03 59 35 87 52 > Assistant: Julie Jonas > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France >

April 18, 2020

Pharo.org is down?

by Tim Mackinnon

Is there planned maintenance on pharo.org? Is been down for a while todayâ¦.

April 18, 2020

Label truncation in new Pharo 8.0 64-bit (stable)

by Shaping

Hi everyone. Below is a Pharo 8.0 64-bit (stable) image (installed with the new Launcher 2.0) with two changes: -Light theme selected. -FiraCode 11 chosen as the default font. Truncated labels in the GUI on font change has always been a problem. Am I the only one experiencing this? Shaping From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Sanjay Minni Sent: Friday, 17 April, 2020 11:05 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] issues in setting up a new project on Github/Iceberg Thanks tried just https and this worked too I suppose once cloned it does not really matter whether it was done using "clone from github.com <http://github.com> " or "clone remote repository" --- Sanjay Minni +91-9900-902902 On Fri, 17 Apr 2020 at 19:43, Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com> > wrote: Hi, El 17 abr 2020, a las 15:30, Sanjay Minni <sm(a)planage.com <mailto:sm@planage.com> > escribiÃ³: Hi Guillermo, Ok then given your comments - right now got it working as such - initially created as private in Github - changed to public - created clone from github - (did a repair repository (dont know why) and created "src" and designated it as source folder) - did a commit and push - changed repository back to private seems to work can you give an example on how the "Remote URL" field is to be filled up - note its not taking HTTP as i am not sure about the syntax, assume SSH, Github, MyName, MyRepository, will try that as well you should be able to use the URLs provided by the clone buttons in Github/gitlab/bitbucket, both https and ssh. note Just for Info to other users: I am using Windows 10, it seems to have SSH tools inbuilt and was able to use ssh (with passphrase) without hiccup, by putting my key files path in pharo setting-> ...-> use custom SSH keys, and uploading the .pub key in Github :) Thanks --- Sanjay Minni +91-9900-902902 On Fri, 17 Apr 2020 at 18:36, Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com> > wrote: Hi Sanjay, This is a bug in Iceberg github integration that tries to access the repository to get metadata using Github REST API using anonymous access apparently. And since your project is private, this fails. As a workaroung, I suggest you to clone using the last option that requires an url only: <PastedGraphic-3.png> This option will not use the Github API, so you should find no problems. Iâm planning doing an Iceberg sprint and fix many issues in the coming weeks. (Also if somebody wants to join, this is an open call :)) Guille El 17 abr 2020, a las 12:49, Sanjay Minni <sm(a)planage.com <mailto:sm@planage.com> > escribiÃ³: Using Pharo 8 64 bit on Windows 10 I am trying to setup a new project on Github using Iceberg following the document "Manage your code with Iceberg dtd 25 March 2019) After creating the project in github when I try to clone from Github as (I am at doc item1.4) The system throws an error and the project does not appear in iceberg although the files are downloaded. This happen in both cases whether I use HTTP or SSH What is going wrong ? also: assuming the clone is made, as per next item in doc 1.5, the directory "src" is created after the clone is made. is that correct ?... then how will the packages sources be mapped to ..\src <http://forum.world.st/file/t368721/1-GettingFirstEmptyProjFromGit.jpg> <http://forum.world.st/file/t368721/0-GithubProjectCreation.jpg> ----- cheers, Sanjay -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

April 18, 2020

Re: [Pharo-users] [ANN] Pharo Launcher 2.0 released!

by CÃ©drick BÃ©ler

Great Job. It looks indeed nicer. I found the docs great too (https://pharo-project.github.io/pharo-launcher <https://pharo-project.github.io/pharo-launcher>). One suggestion would be to add the help contextually. I tried to look at. There is description of commands and SpLinkPresenter but donât think itâs easy to add. I wanted to add the ling in the help description. For instance, the one to create an image for template: WebBrowser openOn: 'https://pharo-project.github.io/pharo-launcher/create-images/â Any way of doing that ? Cheers, CÃ©drick > Le 17 avr. 2020 Ã 18:08, Christophe Demarey <christophe.demarey(a)inria.fr> a Ã©crit : > > Hi all, > > Pharo Launcher 2.0 has just been released! It is available from http://pharo.org/download <http://pharo.org/download>. > > This new version introduces major changes: > The UI has been fully rewritten using the new Spec2 framework <https://github.com/pharo-spec/Spec> and the Commander2 library <https://github.com/pharo-spec/Commander2>. UI has been revamped to increase usability, especially for newcomers. The main window is now composed of a toolbar and the list of images. The template list is now available when clicking on the new image button. > Documentation web site : All Pharo Launcher features are now explained in the new documentation available at https://pharo-project.github.io/pharo-launcher <https://pharo-project.github.io/pharo-launcher>. You can contribute easily by clicking the *edit on GitHub* button. > You can now have many launch configurations for an image (VM to use, vm and image arguments). It means you can use headless Pharo VM from Pharo Launcher. > When creating a new image, you can specify an initialisation script that will be run once at the first image launch. It is useful to load your project code in a stock Pharo image for example. See https://pharo-project.github.io/pharo-launcher/create-images/#image-initial… <https://pharo-project.github.io/pharo-launcher/create-images/#image-initial…> > You can now define your own template sources in addition to official sources (see https://pharo-project.github.io/pharo-launcher/templates/#create-your-own-l… <https://pharo-project.github.io/pharo-launcher/templates/#create-your-own-l…>), including authenticated sources. > Improved image metadata. Pharo Launcher now manages all image metadata in a single STON file (including description, Pharo version). > > Big thanks to all contributors, including issue reports. It is also the opportunity to thanks Damien Cassou, the original author of Pharo Launcher. > > Here is the changelog: > Pharo Launcher v2.0 <https://github.com/pharo-project/pharo-launcher/releases/tag/2.0> > > The list of closed issue is too long (68) to be listed but you can browse it here: https://github.com/pharo-project/pharo-launcher/issues?q=is%3Aissue+is%3Acl… <https://github.com/pharo-project/pharo-launcher/issues?q=is%3Aissue+is%3Acl…> > Here are some highlights: > New features: > > Documentation web site > Image initialisation script > Launch configurations, headless VM support > User template file in addition to the official template file > Jenkins server template now support pipeline projects > Support of private Jenkins server > Support of authenticated HTTP server > Improvements: > > Monitoring of image launch failures to give back the error message (if any) > Newly created image is automatically selected in the image list > Allow to set image description at creation time > Better error management (you will have the choice to ignore them or debug them) > Add a poor version column in image list > Speedup (especially when image repository has a lot of images) > > Bug fixes: > > Fix use of system unzip on Windows > > Regards, > The Pharo team.

April 18, 2020

[ANN] Pharo Launcher 2.0 released!

by Christophe Demarey

Hi all, Pharo Launcher 2.0 has just been released! It is available from http://pharo.org/download <http://pharo.org/download>. This new version introduces major changes: The UI has been fully rewritten using the new Spec2 framework <https://github.com/pharo-spec/Spec> and the Commander2 library <https://github.com/pharo-spec/Commander2>. UI has been revamped to increase usability, especially for newcomers. The main window is now composed of a toolbar and the list of images. The template list is now available when clicking on the new image button. Documentation web site : All Pharo Launcher features are now explained in the new documentation available at https://pharo-project.github.io/pharo-launcher. You can contribute easily by clicking the *edit on GitHub* button. You can now have many launch configurations for an image (VM to use, vm and image arguments). It means you can use headless Pharo VM from Pharo Launcher. When creating a new image, you can specify an initialisation script that will be run once at the first image launch. It is useful to load your project code in a stock Pharo image for example. See https://pharo-project.github.io/pharo-launcher/create-images/#image-initial… You can now define your own template sources in addition to official sources (see https://pharo-project.github.io/pharo-launcher/templates/#create-your-own-l…) including authenticated sources. Improved image metadata. Pharo Launcher now manages all image metadata in a single STON file (including description, Pharo version). Big thanks to all contributors, including issue reports. It is also the opportunity to thanks Damien Cassou, the original author of Pharo Launcher. Here is the changelog: Pharo Launcher v2.0 <https://github.com/pharo-project/pharo-launcher/releases/tag/2.0> The list of closed issue is too long (68) to be listed but you can browse it here: https://github.com/pharo-project/pharo-launcher/issues?q=is%3Aissue+is%3Acl… Here are some highlights: New features: Documentation web site Image initialisation script Launch configurations, headless VM support User template file in addition to the official template file Jenkins server template now support pipeline projects Support of private Jenkins server Support of authenticated HTTP server Improvements: Monitoring of image launch failures to give back the error message (if any) Newly created image is automatically selected in the image list Allow to set image description at creation time Better error management (you will have the choice to ignore them or debug them) Add a poor version column in image list Speedup (especially when image repository has a lot of images) Bug fixes: Fix use of system unzip on Windows Regards, The Pharo team.

April 17, 2020

Re: [Pharo-users] issues in setting up a new project on Github/Iceberg

by Sanjay Minni

Thanks tried just https and this worked too I suppose once cloned it does not really matter whether it was done using "clone from github.com" or "clone remote repository" --- Sanjay Minni +91-9900-902902 On Fri, 17 Apr 2020 at 19:43, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Hi, > > El 17 abr 2020, a las 15:30, Sanjay Minni <sm(a)planage.com> escribiÃ³: > > Hi Guillermo, > > Ok then given your comments - right now got it working as such > - initially created as private in Github > - changed to public > - created clone from github > - (did a repair repository (dont know why) and created "src" and > designated it as source folder) > - did a commit and push > - changed repository back to private > seems to work > > can you give an example on how the "Remote URL" field is to be filled up - > note its not taking HTTP as i am not sure about the syntax, assume SSH, > Github, MyName, MyRepository, > will try that as well > > > you should be able to use the URLs provided by the clone buttons in > Github/gitlab/bitbucket, both https and ssh. > > > > note Just for Info to other users: > I am using Windows 10, it seems to have SSH tools inbuilt and was able to > use ssh (with passphrase) without hiccup, by putting my key files path in > pharo setting-> ...-> use custom SSH keys, and uploading the .pub key in > Github > > > :) > > Thanks > > --- > Sanjay Minni > +91-9900-902902 > > > On Fri, 17 Apr 2020 at 18:36, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > >> Hi Sanjay, >> >> This is a bug in Iceberg github integration that tries to access the >> repository to get metadata using Github REST API using anonymous access >> apparently. >> And since your project is private, this fails. >> >> As a workaroung, I suggest you to clone using the last option that >> requires an url only: >> >> <PastedGraphic-3.png> >> >> This option will not use the Github API, so you should find no problems. >> >> Iâm planning doing an Iceberg sprint and fix many issues in the coming >> weeks. >> (Also if somebody wants to join, this is an open call :)) >> Guille >> >> El 17 abr 2020, a las 12:49, Sanjay Minni <sm(a)planage.com> escribiÃ³: >> >> Using Pharo 8 64 bit on Windows 10 >> >> I am trying to setup a new project on Github using Iceberg following the >> document "Manage your code with Iceberg dtd 25 March 2019) >> >> After creating the project in github when I try to clone from Github as (I >> am at doc item1.4) The system throws an error and the project does not >> appear in iceberg although the files are downloaded. This happen in both >> cases whether I use HTTP or SSH >> >> What is going wrong ? >> >> also: assuming the clone is made, as per next item in doc 1.5, the >> directory >> "src" is created after the clone is made. is that correct ?... then how >> will >> the packages sources be mapped to ..\src >> >> >> <http://forum.world.st/file/t368721/1-GettingFirstEmptyProjFromGit.jpg> >> >> <http://forum.world.st/file/t368721/0-GithubProjectCreation.jpg> >> >> >> >> >> >> ----- >> cheers, >> Sanjay >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >> >

April 17, 2020