- Pharo-dev - lists.pharo.org

Vote for the Pharo mooc :)

by ducasse

Hi there is a competition for the mooc loved by its users: you can vote for the Pharo mooc at https://docs.google.com/forms/d/e/1FAIpQLSfPtKTnyRqJDlJ53A7Ml-nVoKRrz9ijz9L… Stef

Jan. 7, 2019

Bad naming of libfreetype in latest Pharo vm windows 64bits

by Guillermo Polito

Hi all, I'm trying the latest windows pharo VM 64bits (pharo-win-x86_64-201901051900-7a3c6b6.zip from http://files.pharo.org/vm/pharo-spur64/win/) to see how reproducible are the problems with freetype, athens and the bitblt. While in that I've found that libcairo does not load due to a bad naming of libfreetype. I had libfreetype.dll, and renaming it to libfreetype-6.dll made it loadable again. The 32bit windows VM that corresponds to the same commit, the freetype library file is also named libfreetype.dll but there it works. I've found that the specs for freetype for win64 in that commit are right: https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/7a3c6b642312bc2778fd… but maybe the default ones are used? https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/7a3c6b642312bc2778fd… Does somebody know what else could be causing this? Tx, Guille

Jan. 7, 2019

[Pharo 7.0] Build #103: 22865-Metacello-Baselines-using-the-copy-functionality-over-a-p

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

There is a new Pharo build available! The status of the build #103 was: SUCCESS. The Pull Request #2173 was integrated: "22865-Metacello-Baselines-using-the-copy-functionality-over-a-p" Pull request url: https://github.com/pharo-project/pharo/pull/2173 Issue Url: https://pharo.fogbugz.com/f/cases/22865 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 6, 2019

[Pharo 7.0] Build #102: 22493-Classes-after-Removing-traits-should-not-have-methods-from-TraitedClass

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

There is a new Pharo build available! The status of the build #102 was: SUCCESS. The Pull Request #1847 was integrated: "22493-Classes-after-Removing-traits-should-not-have-methods-from-TraitedClass" Pull request url: https://github.com/pharo-project/pharo/pull/1847 Issue Url: https://pharo.fogbugz.com/f/cases/22493 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 6, 2019

Re: [Pharo-dev] [Pharo-users] New book: Pharo with Style

by Esteban Maringolo

I've read the whole booklet and I'm happy to follow most, if not all, the guidelines. Kent Beck's book was influential on this. I have a few remarks, though... Guideline 2.2 Typed variables should mention only existing or loadable types in the system. E.g selectFrom: aDate to: anotherDate and not selectFrom: aBeginningDate to: anEndDate (where Beginning and EndDate are not classes in the system) This affects guideline 2.3 because it says aBinaryBlock and there is no BinaryBlock class. I would also add another guideline here for the use of the 'as' preffix, e.g. asDate, asString, etc. where "as" means a different representation of receiver. E.g. asString is okay, while asShortString is not, because there is no ShortString class. Guideline 2.6 Should be "Number of" or "Count"? E.g. numberOfSomething or somethingCount? I don't like using "of" "with" or similar prepositions to name variables and classes. Guideline 3.2 #beSuprised would be better than #lookSurprised and follows a used convention of using #beSomething, e.g. #beBinary, #beReadOnly, etc. In the Guideline 5.6 the examples are the same. Regards! Esteban A. Maringolo El miÃ©., 2 ene. 2019 a las 2:33, Sean P. DeNigris via Pharo-dev (< pharo-dev(a)lists.pharo.org>) escribiÃ³: > Pharo Smalltalk Developers mailing list wrote > > Including what the method does, even when the code is fairly simple > > (OK, not getter / setter methods), is still useful. > > Yes, but... there is no free lunch. While there may be a benefit when the > code and comment are freshly written and in sync, they are duplication > which > smells whether code or comment and it is all too easy for the code to be > patched without updating the comment. Now that minor speedup turns into a > more significant slowdown when a user blindly follows the now-wrong > comment. > This possibility is made more likely be the fact that a stale comment will > not be picked up by the testing framework. > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > >

Jan. 6, 2019

[Pharo 7.0] Build #101: 22843-Cannot-select-all-in-windows

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

There is a new Pharo build available! The status of the build #101 was: SUCCESS. The Pull Request #2157 was integrated: "22843-Cannot-select-all-in-windows" Pull request url: https://github.com/pharo-project/pharo/pull/2157 Issue Url: https://pharo.fogbugz.com/f/cases/22843 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 5, 2019

Re: [Pharo-dev] I am abandoning SqueakSource3, any takers?

by Eliot Miranda

Hi Tobi, On Sat, Jan 5, 2019 at 1:28 PM Tobias Pape <Das.Linux(a)gmx.de> wrote: > Hi all, > > since there's not a lot interest anymore in SqueakSource3, I'm giving up > maintenanceship. > > Here's the project: > http://squeaksource.com/squeaksource3.html > Here's the current bug tracker: > https://github.com/krono/squeaksource3/issues > > It runs on Squeak, GemStone, and Pharo. > > There are a few instances out there, running without any problems. > What are the instances? If I depend on any I may have to take upon maintainership ;-) Any Takers? > -t _,,,^..^,,,_ best, Eliot

Jan. 5, 2019

I am abandoning SqueakSource3, any takers?

by Tobias Pape

Hi all, since there's not a lot interest anymore in SqueakSource3, I'm giving up maintenanceship. Here's the project: http://squeaksource.com/squeaksource3.html Here's the current bug tracker: https://github.com/krono/squeaksource3/issues It runs on Squeak, GemStone, and Pharo. There are a few instances out there, running without any problems. Any Takers? -t

Jan. 5, 2019

[Pharo 7.0] Build #100: 22864-SessionErrorHandlingTest-should-run-using-the-NonInteractiveUIManager

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

There is a new Pharo build available! The status of the build #100 was: SUCCESS. The Pull Request #2169 was integrated: "22864-SessionErrorHandlingTest-should-run-using-the-NonInteractiveUIManager" Pull request url: https://github.com/pharo-project/pharo/pull/2169 Issue Url: https://pharo.fogbugz.com/f/cases/22864 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 4, 2019

[Pharo 7.0] Build #99: 22863-Improve-Stability-of-Glamour-Tests

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

There is a new Pharo build available! The status of the build #99 was: FAILURE. The Pull Request #2168 was integrated: "22863-Improve-Stability-of-Glamour-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/2168 Issue Url: https://pharo.fogbugz.com/f/cases/22863 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 4, 2019