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

Re: [Pharo-users] How to contribute to Pharo Launcher?

by Tim Mackinnon

Ok - Iâve done a save for both packages - hopefully they are useful: Name: PharoLauncher-Spec-TimM.70 Author: TimM Time: 18 June 2018, 5:32:00.928101 pm UUID: 5e888bd7-4e2b-0d00-85bb-537409965ccd Ancestors: PharoLauncher-Spec-TimM.69 Name: PharoLauncher-Core-TimM.172 Author: TimM Time: 18 June 2018, 5:34:46.055084 pm UUID: 6a2b63e1-4e2b-0d00-85bc-0fed09965ccd Ancestors: PharoLauncher-Core-TimM.171 > On 18 Jun 2018, at 16:30, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > On 18/06/2018 17:27, Tim Mackinnon wrote: >> Hi Cyril - I have to confess that I donât recall what the steps are to safely commit in Monticello. I have smallish changes to 2 packages Core and Spec, and I can see that smalltalkhub repo in the MC browser and can browse my changes against it - but how do I commit both packages in there? I vaguely recall something about slices - but wasnât that a Pharo core thing? >> >> I get the impression that I donât just press save on each package against sthub do I? >> >> Sorry to be so dumb - Iâve just swapped out Monticello usage for Git usage these days. Just need a few hints to get back on track >> > > You need to save the two packages individually. > > While git is project oriented, StHub is package oriented. > > Slices are only for Pharo development. (One could adapt them to make > Monticello more project oriented but it is currently not the case). > > So in conclusion, yes you need to press save on each package. :) > >> Tim >> >> >> > > > -- > Cyril Ferlicot > https://ferlicot.fr >

June 18, 2018

Re: [Pharo-users] [Ann] Iceberg v1.1.1

by Norbert Hartl

Thanks again for the new things. Just a little maneuver critique. The amount of changes you did should be iceberg 1.2.0 and 1.1.1. Versions are cheap ;) and everything which is not really a hot-fix should be a new minor version. Norbert > Am 18.06.2018 um 17:47 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: > > Hi everybody, > > This week we have a small patch release of Iceberg, version v1.1.1. > This version will be available in the next Pharo build. > > In summary, this release fixes two issues with the new credentials manager, and introduces a couple of other enhancements/bugfixes. > > Below you will find the detailed changes log. > Enjoy, > Guille > > Integrate Iceberg 1.1.1 > https://pharo.fogbugz.com/f/cases/22168/Integrate-Iceberg-1-1-1 <https://pharo.fogbugz.com/f/cases/22168/Integrate-Iceberg-1-1-1> > https://github.com/pharo-vcs/iceberg/releases/tag/v1.1.1 <https://github.com/pharo-vcs/iceberg/releases/tag/v1.1.1> > #864 <https://github.com/pharo-project/pharo/pull/864> Repairing Missing repositories lead to wrong source directory > #861 <https://github.com/pharo-project/pharo/pull/861> update tonel to v1.0.9 > #836 <https://github.com/pharo-project/pharo/pull/836> DefaultBackendType class variable is unused > #862 <https://github.com/pharo-project/pharo/pull/862> Iceberg tests are not running in Pharo 7 > #852 <https://github.com/pharo-project/pharo/pull/852> Make error dialogs copy-pastable > #858 <https://github.com/pharo-project/pharo/pull/858> IceTipReadOnlyTextMorph does not allow select and copy anymore > #850 <https://github.com/pharo-project/pharo/pull/850> Change Detached head status from error to warning if we are on a tag > #853 <https://github.com/pharo-project/pharo/pull/853> Clone dialog "username" is confusing > #860 <https://github.com/pharo-project/pharo/pull/860> CredentialStore API > #854 <https://github.com/pharo-project/pharo/pull/854> Error in History window > > > > -- > > 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

June 18, 2018

[Ann] Iceberg v1.1.1

by Guillermo Polito

Hi everybody, This week we have a small patch release of Iceberg, version v1.1.1. This version will be available in the next Pharo build. In summary, this release fixes two issues with the new credentials manager, and introduces a couple of other enhancements/bugfixes. Below you will find the detailed changes log. Enjoy, Guille Integrate Iceberg 1.1.1 https://pharo.fogbugz.com/f/cases/22168/Integrate-Iceberg-1-1-1 https://github.com/pharo-vcs/iceberg/releases/tag/v1.1.1 #864 <https://github.com/pharo-project/pharo/pull/864> Repairing Missing repositories lead to wrong source directory #861 <https://github.com/pharo-project/pharo/pull/861> update tonel to v1.0.9 #836 <https://github.com/pharo-project/pharo/pull/836> DefaultBackendType class variable is unused #862 <https://github.com/pharo-project/pharo/pull/862> Iceberg tests are not running in Pharo 7 #852 <https://github.com/pharo-project/pharo/pull/852> Make error dialogs copy-pastable #858 <https://github.com/pharo-project/pharo/pull/858> IceTipReadOnlyTextMorph does not allow select and copy anymore #850 <https://github.com/pharo-project/pharo/pull/850> Change Detached head status from error to warning if we are on a tag #853 <https://github.com/pharo-project/pharo/pull/853> Clone dialog "username" is confusing #860 <https://github.com/pharo-project/pharo/pull/860> CredentialStore API #854 <https://github.com/pharo-project/pharo/pull/854> Error in History window -- 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

June 18, 2018

Re: [Pharo-users] How to contribute to Pharo Launcher?

by Cyril Ferlicot D.

On 18/06/2018 17:27, Tim Mackinnon wrote: > Hi Cyril - I have to confess that I donât recall what the steps are to safely commit in Monticello. I have smallish changes to 2 packages Core and Spec, and I can see that smalltalkhub repo in the MC browser and can browse my changes against it - but how do I commit both packages in there? I vaguely recall something about slices - but wasnât that a Pharo core thing? > > I get the impression that I donât just press save on each package against sthub do I? > > Sorry to be so dumb - Iâve just swapped out Monticello usage for Git usage these days. Just need a few hints to get back on track > You need to save the two packages individually. While git is project oriented, StHub is package oriented. Slices are only for Pharo development. (One could adapt them to make Monticello more project oriented but it is currently not the case). So in conclusion, yes you need to press save on each package. :) > Tim > > > -- Cyril Ferlicot https://ferlicot.fr

June 18, 2018

Re: [Pharo-users] How to contribute to Pharo Launcher?

by Tim Mackinnon

Hi Cyril - I have to confess that I donât recall what the steps are to safely commit in Monticello. I have smallish changes to 2 packages Core and Spec, and I can see that smalltalkhub repo in the MC browser and can browse my changes against it - but how do I commit both packages in there? I vaguely recall something about slices - but wasnât that a Pharo core thing? I get the impression that I donât just press save on each package against sthub do I? Sorry to be so dumb - Iâve just swapped out Monticello usage for Git usage these days. Just need a few hints to get back on track Tim > On 18 Jun 2018, at 16:20, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > On 18/06/2018 17:15, Tim Mackinnon wrote: >> Given Pharo Launcher is a bit in the limelight, Iâm a bit nervous contributing blindly. Can someone point me/advice me towards how to safely push changes to StHub? >> >> As I mentioned, Iâve added a last-modified column as well as fixing the broken status bar in PL (it looks like spec is a bit pernickety about nested tables). >> > > Hi, > > Since there is stable version released, you can safely commit in the > StHub repository as long as you do not do a destructive actions such has > deleting a .mcz from StHub. > > If the worst case, you will break the bleeding edge launcher, it will be > detected by a review or a bleeding edge user and the commit will be > either corrected or reverted. > > I think stable versions are created from the versions defined in > ConfigurationOfPharoLauncher. > >> Tim >> >> >> > > > -- > Cyril Ferlicot > https://ferlicot.fr >

June 18, 2018

Re: [Pharo-users] How to contribute to Pharo Launcher?

by Cyril Ferlicot D.

On 18/06/2018 17:15, Tim Mackinnon wrote: > Given Pharo Launcher is a bit in the limelight, Iâm a bit nervous contributing blindly. Can someone point me/advice me towards how to safely push changes to StHub? > > As I mentioned, Iâve added a last-modified column as well as fixing the broken status bar in PL (it looks like spec is a bit pernickety about nested tables). > Hi, Since there is stable version released, you can safely commit in the StHub repository as long as you do not do a destructive actions such has deleting a .mcz from StHub. If the worst case, you will break the bleeding edge launcher, it will be detected by a review or a bleeding edge user and the commit will be either corrected or reverted. I think stable versions are created from the versions defined in ConfigurationOfPharoLauncher. > Tim > > > -- Cyril Ferlicot https://ferlicot.fr

June 18, 2018

Re: [Pharo-users] How to contribute to Pharo Launcher?

by Tim Mackinnon

Given Pharo Launcher is a bit in the limelight, Iâm a bit nervous contributing blindly. Can someone point me/advice me towards how to safely push changes to StHub? As I mentioned, Iâve added a last-modified column as well as fixing the broken status bar in PL (it looks like spec is a bit pernickety about nested tables). Tim > On 15 Jun 2018, at 22:25, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi Christophe - you are right, I did contribute many years ago (I found the Mcz field on my disk when I just checked now) - but Iâll be darned If I can remember how it works (I have to confess, I never really got on with Metacello and slices). > > Do I simply take my latest .mcz file in my local directory and somehow apply it to the sthub repo (sorry if this is obvious to you - but Iâve plain forgotten how its done). > > It would be good to get it into GitHub - it certainly seems to work pretty well now for most things, and it makes contributing so much easier. > > Tim > >> On 15 Jun 2018, at 08:14, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: >> >> Hi Tim, >> >>> Le 14 juin 2018 Ã 18:48, Tim Mackinnon <tim(a)testit.works> a Ã©crit : >>> >>> Is PharoLauncher using git - there is a note saying the StHub repo is about to be moved? >>> >>> I ask as I wanted to contribute a simple change that shows the modified date of the images and lets you sort by that (I sometimes forget which was the latest image I was using and have a few old ones kicking around). >> >> >> Until now, I preferred to stay on StHub mainly because Iceberg was not ready to work smoothly with. I did not wanted to get extra-difficulties to work on Pharo Launcher (merge problems, etc). >> That said, Iceberg has now moved a lot in the right direction and I think we could start to use git for Pharo Launcher development. >> I will release a ne version of PharoLauncher soon and then, I think I will move PharoLauncher on github and use Cargo to manage it. >> >> For your contribution, it is welcomed (in fact, it was planned to be added but you were faster). Feel free to commit it directly to the SH repository, I will then take a look at it. It looks like you already can commit: http://smalltalkhub.com/#!/~Pharo/PharoLauncher/contributors. >> >> Thanks Tim. >> >> Regards, >> Christophe > >

June 18, 2018

Re: [Pharo-users] Windows installation broken?

by Ben Coman

On 18 June 2018 at 21:39, Herbert VojÄÃk <herby(a)mailbox.sk> wrote: > > > horrido wrote on 18. 6. 2018 0:04: > >> This is what concerns me. I don't care that there are workarounds >> (undocumented or hard to find). >> >> I care that Windows is a most popular development platform. I care that >> newcomers to Pharo easily find what they need to get started. I care about >> Pharo's reputation. >> >> The last thing Pharo needs is a black eye. >> > > Do you have enough balls to call out Steph for his obviously wrong > decision to push Launcher down the users' throats and make him revert to > working installers / zips? Cause AFAICT there's the bottleneck atm. > > Herby I've been using PharoLauncher for years jumping between Linux & Windows, and it has worked great. Its not PharoLauncher itself, but limitations of the NSIS installer that was used and how that interacted poorly with some environments e.g. admin versus non-admin accounts. The meta-problem is that PharoLauncher worked great for its few users who had compatible environments, but problems remained submerged because it lacked exposure to broad enough environments to unearth such problems. A chicken/egg scenario was limiting broader use of PharoLauncher, and it would continue to languish with biting the bullet to get more users - and more reports. The challenge is providing enough resource priority to deal with issues quickly so not to annoy users too much. I'm very glad PharoLauncher is being promoted as it is, however it may be worth considering that it is for "managing multiple images" and very-new users probably aren't immediately concerned with that. Very-new users are concerned with getting something up as quick and easy as possible, and PharoLauncher does add a few extra steps. Maybe the top of the downloads page could have the zip downloads tagged something like "Taste Test Install" and also include a copy of PBE in those zips. cheers -ben > > > Travis Ayres wrote >> >>> I wonder how many people tried Pharo, thought "Oh this is totally broken" >>> and are never going to give it a second (or third) chance. >>> >>> On Sun, Jun 17, 2018 at 11:26 AM, >>> >> >> phil@ >>> >> >> < >>> >> >> phil@ >>> >> >> > >>> wrote: >>> >>> The current website shows the wrong link, the installer for the bleeding >>>> edge is the wrong one in files. >>>> The situation on the Windows front is very very bad and not really >>>> improving. >>>> >>>> That being said, the installer on the CI is the right one and works. >>>> >>>> so, steal the installer from here: https://ci.inria.fr/pharo-ci- >>>> jenkins2/job/PharoLauncher >>>> >>>> This is the one you want: >>>> >>>> https://ci.inria.fr/pharo-ci-jenkins2/job/PharoLauncher/ >>>> >>>> For having the latest lastet everything, go to the launcher settings, >>>> get >>>> into the devmode and open monticello and load the latest packages. >>>> >>>> Phil >>>> >>> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >

June 18, 2018

Re: [Pharo-users] Windows installation broken?

by Herbert VojÄÃk

Esteban Lorenzano wrote on 18. 6. 2018 16:04: > > >> On 18 Jun 2018, at 15:39, Herbert VojÄÃk <herby(a)mailbox.sk> wrote: >> >> >> >> horrido wrote on 18. 6. 2018 0:04: >>> This is what concerns me. I don't care that there are workarounds >>> (undocumented or hard to find). >>> I care that Windows is a most popular development platform. I care that >>> newcomers to Pharo easily find what they need to get started. I care about >>> Pharo's reputation. >>> The last thing Pharo needs is a black eye. >> >> Do you have enough balls to call out Steph for his obviously wrong decision to push Launcher down the users' throats and make him revert to working installers / zips? Cause AFAICT there's the bottleneck atm. > > First, it was MY decision. My apologies to blaming Steph. > Iâm pushing launcher as the default download for Pharo since year now. > Do I am happy with it not working on windows right now? Of course not. But pushing it also in windows has already forced us to fix some bugs there and a new version of the launcher (and a better Pharo on windows) and at the result will be good. > I was going to suspend the launcher as the default download until a better version arrived, but Iâve been told that will happen this week, so I will wait. > > Second, we have a lot of bottlenecks, but is true this is important. > > Third, please restrain your self to talk like that in the future. Is rude and unnecessary. I won't. Sometimes it seems this kind of talk is needed. Windows launcher was not working for so long but it is still pushed as the default download option, because "higher goals" I presume. If this kind of talk helps to get rid of it until working (or make it finally actually work), it is anything but unnecessary. Herby > Esteban > >> >> Herby >> >>> Travis Ayres wrote >>>> I wonder how many people tried Pharo, thought "Oh this is totally broken" >>>> and are never going to give it a second (or third) chance. >>>> >>>> On Sun, Jun 17, 2018 at 11:26 AM, >>>> phil@ >>>> < >>>> phil@ >>>> > >>>> wrote: >>>> >>>>> The current website shows the wrong link, the installer for the bleeding >>>>> edge is the wrong one in files. >>>>> The situation on the Windows front is very very bad and not really >>>>> improving. >>>>> >>>>> That being said, the installer on the CI is the right one and works. >>>>> >>>>> so, steal the installer from here: https://ci.inria.fr/pharo-ci- >>>>> jenkins2/job/PharoLauncher >>>>> >>>>> This is the one you want: >>>>> >>>>> https://ci.inria.fr/pharo-ci-jenkins2/job/PharoLauncher/ >>>>> >>>>> For having the latest lastet everything, go to the launcher settings, get >>>>> into the devmode and open monticello and load the latest packages. >>>>> >>>>> Phil >>> -- >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> > >

June 18, 2018

Re: [Pharo-users] Windows installation broken?

by Sven Van Caekenberghe

Most are using macOS (which can be considered more or less homogeneous since most mac users do update to recent versions at no cost). Many people are using Linux too, both with UI and for servers. But since there are lots of Linux distributions, supporting a large portion of them is lots of work. I would say it is fair to say Ubuntu is the leading platform here. It feels as if there are less Windows users in our community, and the Windows world is more fragmented over different versions. People really underestimate how hard it is to support all these platforms with all their quirks. And of course, every individual user complains loudly when it is not working for them. > On 18 Jun 2018, at 16:16, horrido <horrido.hobbies(a)gmail.com> wrote: > > Lack of enough Windows users? What platform are most Pharoers using? > > I'm using macOS, but this platform has only about 12% market share. Linux > has about 2%. > > > Sven Van Caekenberghe-2 wrote >>> On 18 Jun 2018, at 15:39, Herbert VojÄÃk < > >> herby@ > >> > wrote: >>> >>> >>> >>> horrido wrote on 18. 6. 2018 0:04: >>>> This is what concerns me. I don't care that there are workarounds >>>> (undocumented or hard to find). >>>> I care that Windows is a most popular development platform. I care that >>>> newcomers to Pharo easily find what they need to get started. I care >>>> about >>>> Pharo's reputation. >>>> The last thing Pharo needs is a black eye. >>> >>> Do you have enough balls to call out Steph for his obviously wrong >>> decision to push Launcher down the users' throats and make him revert to >>> working installers / zips? Cause AFAICT there's the bottleneck atm. >> >> The problem is the lack of enough Windows users and especially developers >> who can fix Windows problems. > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

June 18, 2018