November 2017 - Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #313: 20384-Converted-rules-to-Renraku-architecture-2

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

There is a new Pharo build available! The status of the build #313 was: SUCCESS. The Pull Request #445 was integrated: "20384-Converted-rules-to-Renraku-architecture-2" Pull request url: https://github.com/pharo-project/pharo/pull/445 Issue Url: https://pharo.fogbugz.com/f/cases/20384 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 21, 2017

balloonHelp for menus

by Nicolas Cellier

Hi again, I see no balloon help in menus in Pharo 7.0. Some menu labels are intention revealing and a balloon paraphrasing the label is useless. But that's not the general case, some complex actions like found in Iceberg interface would deserve a bit more explanations for noobs like me. A link from the menu to some Help topic would also be more than welcome (maybe thru an anchor, a tag or some other machinery...)

Nov. 20, 2017

Find in HelpBrowser

by Nicolas Cellier

Hi, I see currently no find menu in HelpBrowser. Wouldn't it be usefull? Yes, there is one in Spotter but: - it does open a window on subtopic, then no way to navigate into the HelpBrowser (it should better open a HelpBrowser with appropriate selection) - it only ever scan help chapter titles from what I understand... I think that a help word-index would be also usefull.

Nov. 20, 2017

method usage example: annotation or comment?

by Nicolas Cellier

Hi, I encountered some annotations in the form: < expr: (foo) result: bar > and some meta comments of the form: " foo >>> bar " I think both are aimed at providing examples of method usage for documentation, non regression testing, etc... I note that the former is requiring a literal result, which is quite limiting (1/3) is not a literal for example, 0@0 neither... IMO it should be extended for handling any valid expression. But that still makes two different ways of expressing the same intent. So what's the canonical one?

Nov. 20, 2017

[Pharo 7.0-dev] Build #312: 20727-WeakAnnouncerTesttestWeakDoubleAnnouncer-should-be-long

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

There is a new Pharo build available! The status of the build #312 was: SUCCESS. The Pull Request #509 was integrated: "20727-WeakAnnouncerTesttestWeakDoubleAnnouncer-should-be-long" Pull request url: https://github.com/pharo-project/pharo/pull/509 Issue Url: https://pharo.fogbugz.com/f/cases/20727 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 20, 2017

Re: [Pharo-dev] [ci-announces] CI capacity problems, help wanted !

by Bruno Carrez

Thanks Stephane. The pressure on the service is slightly lower since Friday, there is no emergency. My call was for those who have obvious oversized or unused slaves; I donât think Pharo is in this caseâ¦ ;-) Thank you anyway. - Bruno > Le 17 nov. 2017 Ã 22:30, Stephane Ducasse <stepharo.self(a)gmail.com> a Ã©crit : > > Hi Bruno > > We will have a look. Now the failures/erasure of the configurations > this summer did not really help > us. We still not fully recovered. > Once Pharo will be managed on git. I think that many of our community > jobs will be > migrated to travis and other services. > > Stef > > On Thu, Nov 16, 2017 at 1:02 PM, Bruno Carrez <bruno.carrez(a)inria.fr> wrote: >> Dear CI users, >> >> As some of you may have noticed, the CI service is in capacity troubles. >> Most VM deployment fail due to a lack of resources. >> >> A lot of VMs use a high-end hardware configuration (XL or XXL), but you must >> be aware that cloudstack is a mutalised service; so, it is important to use >> the right configuration for your real needs. >> It is not acceptable to have unused or oversized slaves on one side, and >> stucked users on the other side that cannot use the service. >> >> A lot of users are affected by this issue and are unable use the platform at >> all ! >> >> So I highly recommend to check if you can reduce your footprint on the >> service: >> >> - by downgrading your oversized slaves, >> - or deleting your unused slaves >> >> If you donât know how to decrease the slave configuration, issue a support >> ticket and we will be glad to help you. >> >> Thanks in advance, in the name of all the ci users. >> >> - The CI team >>

Nov. 20, 2017

Re: [Pharo-dev] nil suspend

by Guillermo Polito

Yes, it doesn't sound right. I vote for removal :) On Sat, Nov 18, 2017 at 11:04 PM, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > It sounds like a left over... > no time stamp in Squeak, so it must be old. > Display reverse; reverse means we wanted to catch when such oddity was > necessary. > (I would do it differently with an Exception and a MessageTally like I > already exhibited several times) > The fact that reverse; reverse was commented is more difficult to > interpret... Is it really necessary? > I removed the method in a Squeak image, and so fare nothing wrong > happened, but it does not prove anything. > The best is to ask in Squeak lists, maybe someone can remember... > Or carefully analyze all senders of suspend... > > 2017-11-18 22:36 GMT+01:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: > >> Hi, >> >> I was looking at nil (already funny) and found a very interesting method: >> >> suspend >> "Kills off processes that didn't terminate properly" >> "Display reverse; reverse." "<-- So we can catch the suspend bug" >> Processor terminateActive >> >> It means that the following code is probably the shortest way to kill >> your image (save first!) >> >> nil suspend >> >> It terminates a UI process if evaluated from anywhere using CMD+d :D >> >> Cheers, >> Alex >> > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Nov. 20, 2017

[Pharo 7.0-dev] Build #311: Avoid costly & useless LargeInteger arithmetics when raisedToFraction will be inexact

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

There is a new Pharo build available! The status of the build #311 was: SUCCESS. The Pull Request #506 was integrated: "Avoid costly & useless LargeInteger arithmetics when raisedToFraction will be inexact" Pull request url: https://github.com/pharo-project/pharo/pull/506 Issue Url: https://pharo.fogbugz.com/f/cases/20432 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 20, 2017

Re: [Pharo-dev] Deploying using the latest minimal image of Pharo (6.1)

by Pavel Krivanek

2017-11-19 19:05 GMT+01:00 despotadesdibujau <despotadesdibujau(a)gmail.com>: > Sven Van Caekenberghe-2 wrote > > Great work, Gabriel, thanks for sharing. I have yet to look at what you > > did in detail, but what is your pending issue exactly, because I don't > > understand "the staless image". Could you elaborate ? > > > > Sven > > Thanks!!! > Ja!, I wanted to say "stateless":eliminate the possibility of modify the > state of the image once it is in production. > That I did was downloaded the minimal image of Pharo, I faced with some > issues to load my application using filetree or github. > I found the solution just loading through Monticello the missing > dependecies > that Metacello needed to use filetree and github repositories. > I delivered an application to a final user just using the minimal image and > it is working. > My idea is to prepare a minimal image with every tool for load > code:Monticello,Metacello suporting all types of repositories > (filetree,github,gitbucket, gitlab,...etc),...etc. > In Pharo 7 most of them are already part of the the minimal (Metacello) image. -- Pavel > Then, when my application is loaded, unload those tools and disable the > command line handlers (if is posible), and eliminate all unnecessary files > like changes and sources ( thank you > <http://forum.world.st/How-to-deploy-headless-app-without- > changes-and-source-files-td4949556.html> > ). > > > Gabriel > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > >

Nov. 20, 2017

[Pharo 7.0-dev] Build #310: 20723 Unused temps in AthensDemoMorph, Alien, AthensBalloonEngine, AthensBezier3Scene, AthensCairoPathBuilder

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

There is a new Pharo build available! The status of the build #310 was: SUCCESS. The Pull Request #503 was integrated: "20723 Unused temps in AthensDemoMorph, Alien, AthensBalloonEngine, AthensBezier3Scene, AthensCairoPathBuilder" Pull request url: https://github.com/pharo-project/pharo/pull/503 Issue Url: https://pharo.fogbugz.com/f/cases/20723 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 20, 2017