- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #1128: 22277-nextNameForextension-is-bogus
by ci-pharo-ci-jenkins2＠inria.fr July 24, 2018

July 24, 2018

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

1 0

Esteban's ChangeLog week of 16 July 2018
by estebanlm＠gmail.com July 23, 2018

July 23, 2018

Hello! This is my weekly ChangeLog, from 16 July 2018 to 22 July 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=16/7/2018&to=22/7/2018 ChangeLog ========= 19 July 2018: ------------- * Back from holidays :) I'm slowly resuming work... right now I'm still dealing with the Win64 VM (no news right now). cheers! Esteban

2 1

Problem with zinc 2.9.2
by Norbert Hartl July 22, 2018

July 22, 2018

I tried to see how hard it would be to load my current project in pharo7. Cyril helped me to see that I load an old version of zinc and it does not work that way. Upgrading to zinc 2.9.2 made it work in pharo 7 but my jenkins build do not work anymore. I donât fully understand what is happening. I see in the log Loading baseline of BaselineOfMobilityMap... ...RETRY->BaselineOfParasol ...RETRY->BaselineOfParasol[31mMessageNotUnderstood: ZnFileSystemUtils class>>newBinaryFileNamed:do: [0mZnFileSystemUtils class(Object)>>doesNotUnderstand: #newBinaryFileNamed:do: ZnClient>>downloadEntityTo: ZnClient>>downloadTo: IceMetacelloPharoPlatform(MetacelloPharoPlatform)>>downloadZipArchive:to: The strange thing about it is that when I download that image where the error occurred I cannot find a sender of #newBinaryFileNamed:do: and the #downloadEntityTo: does not seem to use it. Downgrading to zinc 2.8.10 makes it work again. I feel a little bit stupid because the image does not load any new package on startup and still there is this error message which does not make sense to me at all. Any ideas? Norbert

6 47

[PROPOSAL] Put the WorldMenu in a Menu bar
by Cyril Ferlicot D. July 22, 2018

July 22, 2018

Hi everyone, With Guille we are trying to improve the usability of the WorldMenu. The world menu is by large un-intuitive: - Users are not used to click on a background to open a menu - For those that "get it" they try to do it with right click (Of course, it looks like a context menu!) and that does not work Since some decades now the default way to display a menu in applications is to have a bar at the top of the windows. We should change that world menu by a menu bar like any application. That will lower the entrance barrier to new users, at the cost of having to move the cursor to the top to look for the menu... You can find here a PR that add the WorldMenu as a top bar to Pharo and reorganize it: https://github.com/pharo-project/pharo/pull/1470 See screen in the PR. It still have room for improvements but we think it's stable enough for integration in Pharo. Missing features: - What do we do when Pharo is not wide enough? - What to do when a window is dragged behind? - Make it parametrizable to allow users to build a bar with their own menu builder - Add shortcuts to open the menu windows like (maybe) - Update it when we change the font size (this is a general Pharo problem) Feedback is welcome. Related issue: https://pharo.fogbugz.com/f/cases/22038/Replace-World-Menu-by-Menu-bar Guille & Cyril -- Cyril Ferlicot https://ferlicot.fr

12 26

Re: [Pharo-dev] RHEL/CentOS vs. libgit2 vs. libcurl-gnutls.so.4 vs. 64bit default VM from pharo.org and repos - report
by Sean P. DeNigris July 19, 2018

July 19, 2018

Thanks for the report! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

1 0

RHEL/CentOS vs. libgit2 vs. libcurl-gnutls.so.4 vs. 64bit default VM from pharo.org and repos - report
by Petr Fischer July 19, 2018

July 19, 2018

Hello, Pharo situation on the CentOS/RHEL - major server side Linux distribution: 1) VM installation via this (CentOS7 section via pharo centos repo): https://pharo.org/gnu-linux-installation-64 Broken. There is no libgit2.so in /usr/lib64/pharo6-vm/ So no git/iceberg, game over (can't load today library dependencies hosted on github). There is probably obsolete VM build in pharo CentOS repository. 2) manual download VM standalone "Pharo 6.1 for GNU/Linux (64bit)" from: http://pharo.org/download OK, in this zip package, there is libgit2.so, which has these deps: ... linux-vdso.so.1 => (0x00007ffdb0bfe000) libcurl-gnutls.so.4 => /lib64/libcurl-gnutls.so.4 (0x00007fc67dae8000) libz.so.1 => /lib64/libz.so.1 (0x00007fc67d8d2000) ... But there is no curl-gnutls.so.4 on CentOS7, only libcurl.so.4 (in package libcurl). Result is: no git/iceberg -> game over. Workaround is: cd /usr/lib64 ln -s libcurl.so.4 libcurl-gnutls.so.4 ---------- Solutions: 1) pharo CentOS VM repository needs to be updated (and make the libcurl link in the rpm post installation step) 2) PLEASE - add information about linking libcurl-gnutls.so.4 to the CentOS7 sections (and maybe CentOS6) here: https://pharo.org/gnu-linux-installation-64 End of report, pf

1 0

Re: [Pharo-dev] IndexedSlots in combination with StatefulTraits
by Damien Pollet July 18, 2018

July 18, 2018

I understand what slots are, but haven't heard of frames in this contextâ¦ can you elaborate ? On Wed, 18 Jul 2018 at 13:44, Reg Krock via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > The Slot class implementation is fundamentally sound but the larger > constructs surrounding Frames and Slots still requires extensive thought. > > I suspect that you will find that many more changes will be discovered as > work is done with it. > > Slots provide the capacity to implement most of AOP concepts in a simple > manner. It also results in a Frame model. > > I also would suggest careful examination of when to use composition versus > traits with slots. > > Regards > > Reg Krock > > > > On 17 Jul2018, at 1:44 PM, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: > > > > tesonep(a)gmail.com wrote > >> the one that is disturbing, it is kept for > >> compatibility with the old behavior > > > > Are there enough users to justify backward compatibility if it costs a > nice > > API? > > > > > > > > ----- > > Cheers, > > Sean > > -- > > Sent from: > http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > > > > > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

3 2

[ANN] Pharo Git Thermite Release
by Ronie Salgado July 17, 2018

July 17, 2018

Hello, I am finally releasing an initial public version of Pharo Git Thermite, a tool that I am developing as part of my master thesis for visualizing Monticello and Git commits, for Pharo and Python: GitHub Page with sources/documentation/issue tracker: https://github.com/ronsaldo/pharo-git-thermite Short video examples: - Monticello Visualization; https://youtu.be/02CUHBmm-K8 - GitHub pull request: https://youtu.be/f196btLfYxM - Local git commit: https://youtu.be/LCHTiJ4nx3g Feedback form: https://docs.google.com/forms/d/e/1FAIpQLSeir6VlE3bR78oRsNAp9eHLkUn2Q016wEl… Best regards, Ronie

2 1

[Pharo 7.0-dev] Build #1127: 22067-Duplicated-packages-in-Pharo-baselines-SUnit-and-BasicTools
by ci-pharo-ci-jenkins2＠inria.fr July 17, 2018

July 17, 2018

There is a new Pharo build available! The status of the build #1127 was: FAILURE. The Pull Request #1487 was integrated: "22067-Duplicated-packages-in-Pharo-baselines-SUnit-and-BasicTools" Pull request url: https://github.com/pharo-project/pharo/pull/1487 Issue Url: https://pharo.fogbugz.com/f/cases/22067 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

ZnUnicodeComposingReadStream?
by Alistair Grant July 17, 2018

July 17, 2018

Hi Sven & Everyone, I need to convert an UTF8 encoded decomposed stream (Mac OS file names) in to a composed string, e.g.: string: 'test-Ã¤Ã¶Ã¼-aÌoÌuÌ' code points: #(116 101 115 116 45 228 246 252 45 97 776 111 776 117 776) utf8 encoding: #[116 101 115 116 45 195 164 195 182 195 188 45 97 204 136 111 204 136 117 204 136] In the above string, the first group of 3 accented characters are the same as the second group of 3, but are encoded differently - code points (228 246 252) vs (97 776 111 776 117 776). Reading the utf8 encoded stream should result in: string: 'test-Ã¤Ã¶Ã¼-Ã¤Ã¶Ã¼' code points: #(116 101 115 116 45 228 246 252 45 228 246 252) utf8 encoding: #[116 101 115 116 45 195 164 195 182 195 188 45 195 164 195 182 195 188] My current thought is to write a ZnUnicodeComposingReadStream which would wrap a ZnCharacterReadStream and return the composed characters. What do you think? Thanks! Alistair

3 6