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

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

by Sven Van Caekenberghe

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) - remember the resource location or (when in browser) even the actual file handle" | numFiles | numFiles := anEvent contents. 1 to: numFiles do: [:i | | aFileReference handler | aFileReference := FileReference requestDropReference: i. handler := ExternalDropHandler lookupExternalDropHandler: aFileReference. handler ifNotNil: [ aFileReference binaryWriteStreamDo: [ :stream | handler handle: stream in: self dropEvent: anEvent ] ]]. > On 27 Jun 2019, at 22:41, Hilaire <hilaire(a)drgeo.eu> wrote: > > 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 about other. > > Enclosed .st of the edited method. > > Please, some one with know fill a bug ticket with the proposed fix. > > Thanks > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > <PasteUpMorph-dropFiles.st>

June 27, 2019

Regression in P7 with drag and drop

by Hilaire

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 about other. Enclosed .st of the edited method. Please, some one with know fill a bug ticket with the proposed fix. Thanks Hilaire -- Dr. Geo http://drgeo.eu

June 27, 2019

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

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

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: https://github.com/pharo-project/pharo/issues/3650 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 27, 2019

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

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

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: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 27, 2019

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

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

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 Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 27, 2019

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

by Stephan Eggermont

<casimiro.barreto(a)gmail.com> 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

June 27, 2019

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

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

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: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 27, 2019

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

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

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: https://github.com/pharo-project/pharo/issues/3664 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 27, 2019

Re: [Pharo-dev] Loading project with Pharo

by Christopher Fuhrman

On Thu, 27 Jun 2019 at 16:31, Ben Coman <btc(a)openinworld.com> wrote: > > > On Thu, 27 Jun 2019 at 21:41, Jannik Laval <jannik.laval(a)gmail.com> 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. >> Also when I load Voyage, in MacOS, all loads correctly, but on Windows >> the path length is too long and generate an error. >> > > I expect the repo is in FIleTree format which has two problems on Windows: > * "file per method" produces a massive number of small files which the > system struggles with > * long pathnames exceed Windows 256 character limit. > > Tonel "file per class" format was designed to resolve both these problems > on Windows (IIUC). > > There is also the Windows Defender (virus) scanner that wants to look at all the new files coming down (you'll see it chewing more than 30% of the CPU when you pull down Moose). You can luckily create Exclusions for your Pharo image directory, or the Pharo.exe process. That helps a lot I found. Cheers, Cris

June 27, 2019

Re: [Pharo-dev] Loading project with Pharo

by Ben Coman

On Thu, 27 Jun 2019 at 21:41, Jannik Laval <jannik.laval(a)gmail.com> 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. > Also when I load Voyage, in MacOS, all loads correctly, but on Windows the > path length is too long and generate an error. > I expect the repo is in FIleTree format which has two problems on Windows: * "file per method" produces a massive number of small files which the system struggles with * long pathnames exceed Windows 256 character limit. Tonel "file per class" format was designed to resolve both these problems on Windows (IIUC). cheers -ben

June 27, 2019