- Pharo-dev - lists.pharo.org

Zinc Websockets

by Shaping

Hi all. What is the easiest way to port Zinc Websockets to VW? Has this been done? Shaping

Nov. 6, 2018

Re: [Pharo-dev] Now this is fun ...

by Todd Blanchard

Based on his activity level - it is abandoned. Ask him nicely and I'd bet he would relinquish it. He can move his stuff to jpharo (which is great until we port the VM to Java like JRuby) or something. > On Nov 5, 2018, at 9:07 AM, phil(a)highoctane.be wrote: > > PR bomb... fork all his repos and issue gazillons of PRs. > > Or maybe ask Github for turning ownership to us. > > Phil > > On Mon, Nov 5, 2018, 17:19 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com <mailto:hernan.morales@gmail.com> wrote: > :) > > I think nobody expects Pharo to be : https://github.com/pharo-project <https://github.com/pharo-project> > > but like these: > > https://github.com/perl <https://github.com/perl> -> The Perl Programming Language > https://github.com/ruby <https://github.com/ruby> -> The Ruby Programming Language > https://github.com/python <https://github.com/python> -> The Python Programming Language > > More fun: > > https://github.com/smalltalk <https://github.com/smalltalk> -> Mareike Hybsier > https://github.com/lisp <https://github.com/lisp> -> James Anderson > https://github.com/rust <https://github.com/rust> -> Shinichiro OGAWA > https://github.com/cpp <https://github.com/cpp> -> Stefan Herr > https://github.com/java <https://github.com/java> -> A product manager > > > > El lun., 5 nov. 2018 a las 12:44, Sven Van Caekenberghe > (<sven(a)stfx.eu <mailto:sven@stfx.eu>>) escribiÃ³: > > > > https://github.com/pharo <https://github.com/pharo> > > > > ;-) > > > > >

Nov. 5, 2018

Re: [Pharo-dev] Now this is fun ...

by phil＠highoctane.be

On Mon, Nov 5, 2018, 18:55 James Foster <Smalltalk(a)jgfoster.net wrote: > > > On Nov 5, 2018, at 9:07 AM, phil(a)highoctane.be wrote: > > > > PR bomb... fork all his repos and issue gazillons of PRs. > > I hope this was in jest. > Sure. We already are mixing #pharo with Marseille and a video game... Phil > > > Or maybe ask Github for turning ownership to us. > > If he has been there for a while and that is his name, then we have no > grounds for taking it away. The transfer of ownership case is for a company > that holds a trademark and the other use is causing confusion. I donât > think anyone going to his site will be confused. > > > > > Phil > > James >

Nov. 5, 2018

[Pharo 7.0-dev] Build #1363: 22627-Integrate-Iceberg-131

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

There is a new Pharo build available! The status of the build #1363 was: SUCCESS. The Pull Request #1951 was integrated: "22627-Integrate-Iceberg-131" Pull request url: https://github.com/pharo-project/pharo/pull/1951 Issue Url: https://pharo.fogbugz.com/f/cases/22627 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 5, 2018

Re: [Pharo-dev] Now this is fun ...

by James Foster

> On Nov 5, 2018, at 9:07 AM, phil(a)highoctane.be wrote: > > PR bomb... fork all his repos and issue gazillons of PRs. I hope this was in jest. > Or maybe ask Github for turning ownership to us. If he has been there for a while and that is his name, then we have no grounds for taking it away. The transfer of ownership case is for a company that holds a trademark and the other use is causing confusion. I donât think anyone going to his site will be confused. > > Phil James

Nov. 5, 2018

Re: [Pharo-dev] [ANN] 22477 DelayScheduler cleanup and refactoring [was: Where do we go now ?]

by Ben Coman

On Mon, 5 Nov 2018 at 22:17, Ben Coman <btc(a)openinworld.com> wrote: > On Mon, 5 Nov 2018 at 20:02, Stephan Eggermont <stephan(a)stack.nl> wrote: > >> Ben Coman <btc(a)openinworld.com> wrote: >> > On Fri, 13 Apr 2018 at 13:56, Benoit St-Jean via Pharo-users < >> > pharo-users(a)lists.pharo.org> wrote: >> > >> >> What is the current status of this? DelaySpinScheduler is default in my >> recent Pharo 7 images and makes my images unusable on Ubuntu 18.04LTS. >> > > The refactoring was enabled a month ago. DelaySemaphoreScheduler in the > refactored hierarchy was made default so that DelaySpinScheduler could > remain in place in the old hierarchy . > > https://github.com/pharo-project/pharo/blame/development/src/Kernel/Delay.c… > Working through this on Discord with Stefan, discovered that earlier <Store Settings> had recorded DelaySpinScheduler when it was active was asserting itself in every freshly created image. I guess a lot of people will be susceptible to this, particularly if like me they don't remember where those files are without googling for it. In this case could fix it by changing System > System Settings > System > Delay Scheduler = DelaySemaphoreScheduler and then in Settings clicking <Store Settings>. But maybe something else needs to be done to head off this trap for everyone else. cheers -ben

Nov. 5, 2018

Re: [Pharo-dev] Now this is fun ...

by phil＠highoctane.be

PR bomb... fork all his repos and issue gazillons of PRs. Or maybe ask Github for turning ownership to us. Phil On Mon, Nov 5, 2018, 17:19 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com wrote: > :) > > I think nobody expects Pharo to be : https://github.com/pharo-project > > but like these: > > https://github.com/perl -> The Perl Programming Language > https://github.com/ruby -> The Ruby Programming Language > https://github.com/python -> The Python Programming Language > > More fun: > > https://github.com/smalltalk -> Mareike Hybsier > https://github.com/lisp -> James Anderson > https://github.com/rust -> Shinichiro OGAWA > https://github.com/cpp -> Stefan Herr > https://github.com/java -> A product manager > > > > El lun., 5 nov. 2018 a las 12:44, Sven Van Caekenberghe > (<sven(a)stfx.eu>) escribiÃ³: > > > > https://github.com/pharo > > > > ;-) > > > > > >

Nov. 5, 2018

Re: [Pharo-dev] Now this is fun ...

by Ben Coman

On Mon, 5 Nov 2018 at 23:43, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > https://github.com/pharo > > ;-) > Beat us to it in 2011. But with only 4 repositories, I wonder did anyone politely reach out to describe out community and ask if we might allowed to adopt that url? You can't know anyone's situation and philosophy until you ask them. I could do it. But better we don't all rush to do it and overwhelm him. cheers -ben

Nov. 5, 2018

Re: [Pharo-dev] Now this is fun ...

by HernÃ¡n Morales Durand

:) I think nobody expects Pharo to be : https://github.com/pharo-project but like these: https://github.com/perl -> The Perl Programming Language https://github.com/ruby -> The Ruby Programming Language https://github.com/python -> The Python Programming Language More fun: https://github.com/smalltalk -> Mareike Hybsier https://github.com/lisp -> James Anderson https://github.com/rust -> Shinichiro OGAWA https://github.com/cpp -> Stefan Herr https://github.com/java -> A product manager El lun., 5 nov. 2018 a las 12:44, Sven Van Caekenberghe (<sven(a)stfx.eu>) escribiÃ³: > > https://github.com/pharo > > ;-) > >

Nov. 5, 2018

Re: [Pharo-dev] [ANN] Iceberg v1.3.1

by HernÃ¡n Morales Durand

Hi Cyril, Does the update apply to Pharo 6.1? Cheers, HernÃ¡n El lun., 5 nov. 2018 a las 10:16, Cyril Ferlicot (<cyril.ferlicot(a)gmail.com>) escribiÃ³: > > Hello! > > This week we are releasing the version v1.3 of Iceberg. > (https://github.com/pharo-vcs/iceberg/releases/tag/v1.3.0 > +https://github.com/pharo-vcs/iceberg/releases/tag/v1.3.1) > > This version will be available after we merge this PR: > > https://github.com/pharo-project/pharo/pull/1951 > > This release contains some new features such as the support of self > hosted gitlab, integration with github, etc. > It also contains multiple bug fixes, cleanups and enhancements. > > On the CI part, Guille made the Appveyor build green! This will > increase the stability of the windows support. > > Thanks to all contributors. > > Enjoy! > > Full changelog: > > Features > > #1021 Self hosted gitlab support > #1027 Improved new tag dialog to generate semantic versionning tags > #1044 Show a button "View on Github" when creating a PR > #1008 Add "create branch from GitHub issue" option > #1048 Add commands to open remotes on Github > #1010 Add menu entry in extras to force calculate diff > > Bug corrections > > #975 Metacello asks too many times what to install when there are > conflicting versions > #980 Iceberg should Identify better the packages and the normal files > #982 The Edit Project should have a Warning if it will affect the packages > #986 Iceberg does not realize changes in extended classes > #999 Pulling and pushing to a gitolite server asks password > #984 Conversion to Tonel generates corrupted .properties > #1041 Filter in repository view don't work with capital letters > #1019 Metacello Integration leaves Monticello leftover repositories > #859 Creating a branch and pushing does not sets the upstream > #1043 Packages starting with lowercase not recognized > #991 Error on right click in the project editon wizard > #775 Reviewing a PR is broken > #1036 Debugger if we try to merge without selecting a branch > #1064 Fix failing tests regarding clean code in Pharo > > Enhancements > > #988 Iceberg should load the packages in a single MCLoader (This will > make the loads of packages atomic) > #1001 Use "instance creation" instead of "instance-creation" for > method protocol name > #1004 Use displayScaleFactor in UI > #977 Add ToolTip help to the Commands > #1030 Better support for binary files > #1034 SSH passphrase is now hidden > > Cleanups > > #1018 Iceberg UI relies on deprecated classes from Spec and Commander > #1051 Clean useless huge hierarchy in Github plugin UI > > Infrastructure Enhancements > > #1023 Fix CI for windows > > -- > Cyril Ferlicot > https://ferlicot.fr >

Nov. 5, 2018