[Pharo-dev] [Pharo 8.0] Build #398: 3670 package announcements tests core should be announcements core tests

There is a new Pharo build available! The status of the build #398 was: FAILURE. The Pull Request #3671 was integrated: "3670 package announcements tests core should be announcements core tests" Pull request url: https://github.com/pharo-project/pharo/pull/3671 Issue Url:

[Pharo-dev] [Pharo 8.0] Build #397: 3672 athens tests cairo should be athens cairo tests

There is a new Pharo build available! The status of the build #397 was: FAILURE. The Pull Request #3673 was integrated: "3672 athens tests cairo should be athens cairo tests" Pull request url: https://github.com/pharo-project/pharo/pull/3673 Issue Url:

[Pharo-dev] [Pharo 8.0] Build #396: Small cleanups in BlueInk-Tests package

There is a new Pharo build available! The status of the build #396 was: FAILURE. The Pull Request #3678 was integrated: "Small cleanups in BlueInk-Tests package" Pull request url: https://github.com/pharo-project/pharo/pull/3678 Issue Url: https://github.com/pharo-project/pharo/issues/3676

Re: [Pharo-dev] Regression in P7 with drag and drop

thanks for the report. Hilaire could you open a bug entry and we will issue a fix for P7 and P8 S. > On 28 Jun 2019, at 07:16, Hilaire wrote: > > And there is an issue with the Default drop handler. > > Try to drop a text file in P7 or likely P8 image. > > Message #name is expected to be

Re: [Pharo-dev] Regression in P7 with drag and drop

And there is an issue with the Default drop handler. Try to drop a text file in P7 or likely P8 image. Message #name is expected to be understandble by Stream, but it is not any more the case. Hilaire -- Dr. Geo http://drgeo.eu -- Dr. Geo http://drgeo.eu

Re: [Pharo-dev] Regression in P7 with drag and drop

It was changed like that as early as in P7. It does not work. How could the dragged and dropped file opened as a write stream? Replacing binaryWriteStreamDo: wtih readStreamDo: make it work for DrGeo. I don't know about other scenario usage. Hilaire -- Dr. Geo http://drgeo.eu

Re: [Pharo-dev] Regression in P7 with drag and drop

That method was fixed as follows in Pharo 8 PasteUpMorph>>#dropFiles: anEvent "Handle a number of dropped files from the OS. TODO: - use a more general mechanism for figuring out what to do with the file (perhaps even offering a choice from a menu)

[Pharo-dev] Regression in P7 with drag and drop

Hi, PasteUpMorph>>dropFiles: looks wrong in P7. A Write stream is created while a Read stream is expected. Result: drag and drop of a sketch file does not work anymore in DrGeo. Should it be a binary read stream or just a read stream? With a read stream it works fine for DrGeo, not sure

[Pharo-dev] [Pharo 8.0] Build #395: 3650-unify-hasSlotNamed-in-AbractLayout-and-ClassDescription

There is a new Pharo build available! The status of the build #395 was: FAILURE. The Pull Request #3651 was integrated: "3650-unify-hasSlotNamed-in-AbractLayout-and-ClassDescription" Pull request url: https://github.com/pharo-project/pharo/pull/3651 Issue Url:

[Pharo-dev] [Pharo 8.0] Build #394: 3657-add-allClassVariables

There is a new Pharo build available! The status of the build #394 was: FAILURE. The Pull Request #3658 was integrated: "3657-add-allClassVariables" Pull request url: https://github.com/pharo-project/pharo/pull/3658 Issue Url: https://github.com/pharo-project/pharo/issues/3657 Build Url:

[Pharo-dev] [Pharo 8.0] Build #393: 3646-simplify-allSelectorsInProtocol

There is a new Pharo build available! The status of the build #393 was: FAILURE. The Pull Request #3647 was integrated: "3646-simplify-allSelectorsInProtocol" Pull request url: https://github.com/pharo-project/pharo/pull/3647 Issue Url: https://github.com/pharo-project/pharo/issues/3646 Build

Re: [Pharo-dev] Pharo VM still crashing on Windows due to SSL

wrote: > Since my last post, Pharo is still crashing during installation of > Seaside 3 in Windows 10 platforms. It happens because git uses SSL and > there’s some bug that causes libssl to crash, killing VM. With the latest vm? Stephan

[Pharo-dev] [Pharo 8.0] Build #392: 3668-hasLinks---hasMetaLinks

There is a new Pharo build available! The status of the build #392 was: FAILURE. The Pull Request #3669 was integrated: "3668-hasLinks---hasMetaLinks" Pull request url: https://github.com/pharo-project/pharo/pull/3669 Issue Url: https://github.com/pharo-project/pharo/issues/3668 Build Url:

[Pharo-dev] [Pharo 8.0] Build #391: 3664-add-minimal-code-to-have-the-new-code-completion

There is a new Pharo build available! The status of the build #391 was: FAILURE. The Pull Request #3665 was integrated: "3664-add-minimal-code-to-have-the-new-code-completion" Pull request url: https://github.com/pharo-project/pharo/pull/3665 Issue Url:

Re: [Pharo-dev] Loading project with Pharo

On Thu, 27 Jun 2019 at 16:31, Ben Coman wrote: > > > On Thu, 27 Jun 2019 at 21:41, Jannik Laval wrote: > >> Dear pharoers, >> >> I use Pharo in Windows 10 and MacOS. >> I find a big difference of loading time between the 2 systems. >> >> For loading Moose for example, In MacOS, it takes few

Re: [Pharo-dev] Loading project with Pharo

On Thu, 27 Jun 2019 at 21:41, Jannik Laval wrote: > Dear pharoers, > > I use Pharo in Windows 10 and MacOS. > I find a big difference of loading time between the 2 systems. > > For loading Moose for example, In MacOS, it takes few minutes, but in > Windows 10 it takes more than 15 minutes. >

[Pharo-dev] Loading project with Pharo

Dear pharoers, I use Pharo in Windows 10 and MacOS. I find a big difference of loading time between the 2 systems. For loading Moose for example, In MacOS, it takes few minutes, but in Windows 10 it takes more than 15 minutes. Also when I load Voyage, in MacOS, all loads correctly, but on

[Pharo-dev] [Pharo 8.0] Build #390: 3654-SystemNavigation-browseAllStoresIntofrom-and-cleanup

There is a new Pharo build available! The status of the build #390 was: SUCCESS. The Pull Request #3655 was integrated: "3654-SystemNavigation-browseAllStoresIntofrom-and-cleanup" Pull request url: https://github.com/pharo-project/pharo/pull/3655 Issue Url:

Re: [Pharo-dev] A small game: do one trivial improvement every day

> On 26 Jun 2019, at 08:16, Marcus Denker wrote: > > Hi, > > I have started again to do one absolutely trivial improvement every week-day. > Trivial improvement of the day: simplify #allSelectorsInProtocol: https://github.com/pharo-project/pharo/pull/3647 review needed. This is