- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #331: 20763 ExternalAddress>>finalize should be in finalization protocol
by ci-pharo-ci-jenkins2＠inria.fr Nov. 26, 2017

Nov. 26, 2017

There is a new Pharo build available! The status of the build #331 was: SUCCESS. The Pull Request #547 was integrated: "20763 ExternalAddress>>finalize should be in finalization protocol" Pull request url: https://github.com/pharo-project/pharo/pull/547 Issue Url: https://pharo.fogbugz.com/f/cases/20763 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Is SmalltalkCI working for Pharo projects?
by Gabriel Cotelli Nov. 26, 2017

Nov. 26, 2017

All the latest builds I've tried are failing in Travis with "out of memory" errors aparently after running the tests. It's always the same error and for different Pharo versions (4.0 5.0 6.1 7.0 , etc) See for example https://travis-ci.org/ba-st/Willow/jobs/307025742 Anyone noticed something similar? Regards, Gabriel

2 2

Bloc Animations
by Sean P. DeNigris Nov. 26, 2017

Nov. 26, 2017

I saw this on the Squeak ML [1] and wondered how/if this applies to Blocâ¦ marcel.taeumel wrote > You can do a lot of stuff with plain morphs and stepping, too. In the > Animations framework, the focus was on a more convenient programming > interface that decouples system load and animation time. So, even if your > Squeak image has plenty of things to do, the animation X will finish > after, for example, 250 ms. Yet, you might only see the first and the last > update then. :D In some way, the Animations framework is kind of Morphic > stepping but it offers each participant a synchronized progression of > time, which can then be used to update or interpolate the animation > progress. Such things are difficult with Morphic stepping because the > "call me again in 20 ms" via #stepTime treats time different for each > morph. 1. http://forum.world.st/Fun-with-Animations-tp5029046p5030234.html ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

3 2

Re: [Pharo-dev] Pharo 32bit on debian 9 stretch 64bit
by Juan Nov. 26, 2017

Nov. 26, 2017

Hi May be making link, ln -s .... Cheers Jmdc El 25 nov. 2017 21:36, "Cyril Ferlicot" <cyril.ferlicot(a)gmail.com> escribiÃ³: On Sun, Nov 26, 2017 at 1:22 AM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > Hi, > > I would like to use Pharo on a Debian 9, 64bits. > > On Pharo website there is an explanation of the requirements for Debian 7 and 8. > > For Debian it is: > > sudo dpkg --add-architecture i386 > sudo apt-get update > sudo apt-get install libx11-6:i386 > sudo apt-get install libgl1-mesa-glx:i386 > sudo apt-get install libfontconfig1:i386 > sudo apt-get install libssl1.0.0:i386 > > The problem is that > > sudo apt-get install libssl1.0.0:i386 > > throw me this error: > > Reading package lists... Done > Building dependency tree > Reading state information... Done > Package libssl1.0.0:i386 is not available, but is referred to by > another package. > This may mean that the package is missing, has been obsoleted, or > is only available from another source > > E: Package 'libssl1.0.0:i386' has no installation candidate > > Pharo cannot be use with this libssl. I think that Pharo's webstie > should also cover Debian 9. > > Does someone know what should I do to get the right dependencies? > Should I manually download the .deb of debian 8 and install it? > For some more info: Apparently Debian 9 only support libssl1.0.2 and libssl1.1. I tried to install the 1.0.2 but the VM really ask for the 1.0.0 version. -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

2 1

Layout in bloc
by Alexandre Bergel Nov. 25, 2017

Nov. 25, 2017

Hi! I am working on a popup support in Bloc and I am facing a problem. Consider the following code: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= space := BlSpace new. space root layout: BlLinearLayout horizontal. 10 timesRepeat: [ | e | e := (BlRectangle new extent: 20 @ 20) asElement. e background: Color random. space root addChild: e ]. space root children withIndexDo: [ :e :index | e translateBy: (index * 30) @ 10 ]. space root children do: [ :e | e addEventHandler: (BlEventHandler on: BlMouseEnterEvent do: [ :evt | | txt | txt := BlText new position: evt position; fill: Color red; text: 'Hello World'. e parent addChild: txt ]). ]. space show -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= If you uncomment the second line (âspace root layout:â¦â), then the string hello world is added text to the element in which the mouse enter. With the layout, the string is added at the end of the line. I like very much the idea of having the layout applied when elements are added (even I suspect we may have scalability issues very soon), but in that situation, this is not wished. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 4

Iceberg Clone Location
by Sean P. DeNigris Nov. 25, 2017

Nov. 25, 2017

I have a problem I'm not sure how to solve. In many of my baselines for personal private projects, I have dependencies with filetree URL repositories. IIUC, that was the best practice when I asked on the MetaC mailing list. The file URLS are all of the form {sharedRepoFolder}/{projectName}. Now Iceberg seems to expect clones to be in {sharedRepoFolder}/{gitHubUser}/{projectName}. It doesn't find them there, and then clones everything anew. I have a few concerns about this, not the least of which is the thought of having to redo all my baselines. That said, I realize that maybe this is inevitable, so I wanted to put this out there to see if I'm missing something and the best way to proceed. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

3 3

Pharo 6.1 64 bits segmentation fault loading code on Linux
by Gabriel Cotelli Nov. 25, 2017

Nov. 25, 2017

I've created the following issue: https://pharo.fogbugz.com/f/cases/20737/Segmentation-fault-trying-to-load-c… I can reproduce it easily so if you need some more info let me know. Regards, Gabriel

4 8

Pharo Filter usability due to same background as List (Iceberg)
by Torsten Bergmann Nov. 25, 2017

Nov. 25, 2017

Hi, I do not know if this is only an issue of Iceberg or of the themes in general: Due to the topic of todays techtalk I added "DiscordSt" repository to Iceberg leading to the attached screenshot. I wondered why there are only 7 packages while I was pretty sure that there were more packages in the GitHub page of the repo. So it LOOKED LIKE THE LIST ENDED/ONLY HAS A FEW ITEMS because the filter is displayed right at the bottom of the list. You can call me stupid - but I initially thought of an Iceberg synch synch issue were some packages were not downloaded/cloned - but then after several seconds I realized that the list just ends because of the filter area and there are more items - one just has to scroll. This is OK but I interpreted the white area of the filter as there is no further list item instead of realizing the filter possibility itself. Maybe I'm the only one but: as the (package) list background is white and the filter background is white too this is hardly to distinguish. Also the placeholder "Filter" is centered instead of right aligned ... So depending on windows size it is displayed in a wider distance to the list item text and one does not notice that the white area is a filter. I guess a small thin line to separate the filter widget from the list part of the widget would solve the issue. Would that be possible? If so is this only an issue of Iceberg or the Pharo theme in general? Also I wonder: the "Filter ..." placeholder label is centered in the middle. If one clicks into the filter the "Filter..." placeholder surprisingly jumps to the left. I guess we have to catch up more with the usability of our tools. Thanks T.

3 2

[Pharo 7.0-dev] Build #330: 20061-Explicit-isAbstract-is-needed-instead-of-using-hasAbstractMethods-in-tools2
by ci-pharo-ci-jenkins2＠inria.fr Nov. 25, 2017

Nov. 25, 2017

There is a new Pharo build available! The status of the build #330 was: SUCCESS. The Pull Request #541 was integrated: "20061-Explicit-isAbstract-is-needed-instead-of-using-hasAbstractMethods-in-tools2" Pull request url: https://github.com/pharo-project/pharo/pull/541 Issue Url: https://pharo.fogbugz.com/f/cases/20061 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #329: 20176-Error-in-ByteArraybooleanAt
by ci-pharo-ci-jenkins2＠inria.fr Nov. 25, 2017

Nov. 25, 2017

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

1 0