- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #417: 20945-Dependency-browser-should-not-depends-on-Nautilus
by ci-pharo-ci-jenkins2＠inria.fr Jan. 11, 2018

Jan. 11, 2018

There is a new Pharo build available! The status of the build #417 was: FAILURE. The Pull Request #661 was integrated: "20945-Dependency-browser-should-not-depends-on-Nautilus" Pull request url: https://github.com/pharo-project/pharo/pull/661 Issue Url: https://pharo.fogbugz.com/f/cases/20945 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

About values....
by Stephane Ducasse Jan. 10, 2018

Jan. 10, 2018

https://youtu.be/keCwRdbwNQY I would love to have $ to market Pharo but I like this talk Stef

3 5

[Pharo 7.0-dev] Build #416: 20936-64bit-primitiveFailure-for-1-0-largeIdentityHash
by ci-pharo-ci-jenkins2＠inria.fr Jan. 10, 2018

Jan. 10, 2018

There is a new Pharo build available! The status of the build #416 was: SUCCESS. The Pull Request #658 was integrated: "20936-64bit-primitiveFailure-for-1-0-largeIdentityHash" Pull request url: https://github.com/pharo-project/pharo/pull/658 Issue Url: https://pharo.fogbugz.com/f/cases/20936 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Google Summer of Code 2018 with Pharo Consortium
by Jigyasa Grover Jan. 10, 2018

Jan. 10, 2018

Hello Pharo-ers ! On behalf of the community, I would like to thank each one of you for their significant contribution in the previously concluded *Google Summer of Code 2017* with *Pharo Consortium*. We aspire to take-off on a long flight after this successful stint by applying to participate in the upcoming *Google Summer of Code 2018*. As many of you might know, Google Summer of Code is a global program focused on bringing more student developers into open source software development. Students work with an open source organization on a 3 month programming project during their break from school. Read more about the program here: https://summerofcode.withgoogle.com/ The deadline for organisations to apply is January 23, 2018 which is fast approaching. As an open source evangelist and a Pharo developer, I would like to invite all the experienced members to be a part of the "GSoC 2018 with Pharo Consortium" Team and mentor students. Propose fresh ideas for projects which shall help improve Pharo or volunteer to mentor any of the existing one (Listed here: http://gsoc.pharo.org/) To add your own project idea to the list, visit http://gsoc.pharo.org/#adding-a-proposal Looking forward to an appreciable representation from the Pharo community. Best regards Jigyasa Grover Pharo Consortium Org Admin, Google Summer of Code 2017 [hidden email] -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

1 0

Pavel's ChangeLog week of 2017-01-01
by Pavel Krivanek Jan. 9, 2018

Jan. 9, 2018

In memory sources file - I slightly improved the PR for integration of the sources file inside the object memory. Now it will be possible to extract them back to the disk from the menu so everything can work as before. I'm not sure if it will be integrated into Pharo 7 or we will wait for Pharo 8 but it seems to be prepared. File API and caching - because the in-memory sources file do not use deprecated MultiByteFileStream, I played with the new file API and discovered that ZnCharacterReadStream on File is about 10 times slower than the old MultiByteFileStream. That's because ZnCharacterReadStream does not use any cache. For better speed the ZnBufferedReadStream needs to be used like this: readStream := File openForReadFileNamed: 'file.txt'. zn := ZnCharacterReadStream on: readStream encoding: #UTF8. buffered := ZnBufferedReadStream on: zn. [ buffered atEnd ] whileFalse: [ buffered next: 20000 ]. However the ZnBufferedReadStream is by design only a linear stream and the position cannot be changed and thus it cannot be used for *.sources files etc. We will need to prepare a positionable alternative. Ring 2 integration - I was working on replacing of the old Ring with the new reimplementation. The old Ring is used on many sensitive places in the system. Mainly in tools however it is used by Monticello and Epicea too so to try to remove it is like to cut a branch below yourself on an undermined tree. The approach of the old and new Ring is in many senses very different and the full compatibility will not be supported. I partly provide compatibility API, partly adopt the code directly. - The real system and the model is mixed many times in the users of the old Ring. For example a model for a method is created but then when the package of the method is asked, it is already a real package, not its model. Such places need to be cleaned. - I already have an image that has no old Ring code at all but because of some memory leaks caused by the mixtures of the models and real system I was not able to bootstrap it successfully. More work is needed. - I discovered that the image has a serious memory leak caused by Iceberg/GT and Announcers but I still need to find more information about it. Smalltalk archeology - during the free days on the beginning of the year I looked at Smalltalk-78. I extracted the data from Lively Kernel so the original image can read from external files, not only the recent updated ones. - Then I looked at SqueakJS again and tried to reproduce Craig's experiments with Pharo on it. Generally it is about 100 times slower than native Pharo which makes it hard to use for real-life tasks. However it would be pity to do not provide at least basic attention to it because in some cases it may be really useful. Cheers, -- Pavel

5 9

[Doodle] OpenSmalltalk VM Meeting
by Fabio Niephaus Jan. 9, 2018

Jan. 9, 2018

Hi all, When ClÃ©ment and I recently talked about the next VM release, we thought it might be good to organize a meeting and invite everyone who would be interested. The agenda is yet to be finalized, but I think it would be great if ClÃ©ment and/or Eliot could give an update on their work on Sista. And I could give an overview of what still needs to be done for the release or how we plan to sign and update the release bundles. I'm sure there is a lot more we can talk about. If you would like to attend, please indicate your availability using this Doodle link by Sunday, 14th January: https://doodle.com/poll/cyei4ax4sd43m522. Looking forward to seeing you all soon. Best, Fabio

2 1

[Ann] Tiny Calypso update 0.8.7
by Denis Kudriashov Jan. 9, 2018

Jan. 9, 2018

Hi. I just want to share the progress of Calypso. This version adopts Calypso for new TelePharo version and removes the main Nautilus dependency. You can find details with screenshots in my blog http://dionisiydk.blogspot.fr/2018/01/calypso-in-progress-087.html. Best regards, Denis

2 1

[Ann] TelePharo is updated for new Calypso version
by Denis Kudriashov Jan. 9, 2018

Jan. 9, 2018

Hi. I finally tested and fixed TelePharo based on new Calypso version 0.8. So all new features of Calypso are available for remote images. It is new stable version v0.2.x. For slow remote servers it is good to disable "expensive" plugins. For example overriding method icons (up/down arrows) decrease browser performance on Raspberry. For such cases prepare remote images with extra script: ClySystemEnvironmentPlugin disableSlowPlugins. It disables most heavy features including critiques plugin and covered methods decoration (test icon over domain methods). You can also disable it from command line: ./pharo PharoServer.image remotePharo --startServerOnPort=40423 *--disableSlowPlugins* Best regards, Denis

1 1

[Pharo 7.0-dev] Build #415: 20934-Missing-implementation-for-supporting-read-only-onjects
by ci-pharo-ci-jenkins2＠inria.fr Jan. 9, 2018

Jan. 9, 2018

There is a new Pharo build available! The status of the build #415 was: SUCCESS. The Pull Request #656 was integrated: "20934-Missing-implementation-for-supporting-read-only-onjects" Pull request url: https://github.com/pharo-project/pharo/pull/656 Issue Url: https://pharo.fogbugz.com/f/cases/20934 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

identifying source of particular VM
by Ben Coman Jan. 9, 2018

Jan. 9, 2018

This filename of the VM download url... http://files.pharo.org/vm/pharo-spur64/linux/pharo-linux-x86_64threaded-201… includes a hash "276a5ff" that I presumed identified the opensmalltalk-vm commit from which this VM was built. i.e. so I could check that out if I wanted to compile a debug version of that VM. However... $ git checkout 276a5ff says... error: pathspec '276a5ff' did not match any file(s) known to git. so what exactly is that hash 276a5ff in the filename? cheers -ben

4 4