- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] roundTo: strange behavior

by Sven Van Caekenberghe

> On 25 Oct 2016, at 11:05, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > > +1. > > Unless you're dealing with fixed precision* entities, it's usually better to specify digits to display in printing methods themselves (#printShowingDecimalPlaces: & friends in base image). > As per previous discussions around this that arise every second year or so, rounding the number itself (as long as we're dealing with floats) will never work as you want reliably. > > Cheers, > Henry > > * And in that case, you'd use ScaledDecimals YES !! So true. >> On 23 Oct 2016, at 7:08 , phil(a)highoctane.be wrote: >> >> I use the Printf package for that. >> >> v := 65.456. >> 'With 2 decimal digits: %5.2f, or 3 like this: %6.3f' >> printf: {v. v}. >> >> With 2 decimal digits: 65.45, or 3 like this: 65.456 >> >> It is in http://www.smalltalkhub.com/#!/~philippeback/HOExtras >> >> Printf >> >> I am just used to C printf and well, I like the way it works. >> >> Phil

Oct. 25, 2016

Re: [Pharo-dev] roundTo: strange behavior

by Henrik Johansen

+1. Unless you're dealing with fixed precision* entities, it's usually better to specify digits to display in printing methods themselves (#printShowingDecimalPlaces: & friends in base image). As per previous discussions around this that arise every second year or so, rounding the number itself (as long as we're dealing with floats) will never work as you want reliably. Cheers, Henry * And in that case, you'd use ScaledDecimals > On 23 Oct 2016, at 7:08 , phil(a)highoctane.be wrote: > > I use the Printf package for that. > > v := 65.456. > 'With 2 decimal digits: %5.2f, or 3 like this: %6.3f' > printf: {v. v}. > > With 2 decimal digits: 65.45, or 3 like this: 65.456 > > It is in http://www.smalltalkhub.com/#!/~philippeback/HOExtras <http://www.smalltalkhub.com/#!/~philippeback/HOExtras> > > Printf > > I am just used to C printf and well, I like the way it works. > > Phil

Oct. 25, 2016

Re: [Pharo-dev] CI's down ?

by Marcus Denker

Hi, I have restarted the jenkins. Lets hope it works better. Marcus > On 24 Oct 2016, at 11:34, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > It seems that since a couple of days the CI's are down ? > > https://ci.inria.fr/pharo-contribution/ > > >

Oct. 25, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50762 Home: https://github.com/pharo-project/pharo-core

Oct. 25, 2016

[pharo-project/pharo-core] 9733d5: 50762

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 9733d5c59a3043f0425826f133fa7b71d24e3c2a https://github.com/pharo-project/pharo-core/commit/9733d5c59a3043f0425826f1… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-10-25 (Tue, 25 Oct 2016) Changed paths: M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/baselines/baseline33_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/baselines/baseline34_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/baselines/baseline40_.st M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/symbolic versions/development_.st M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version415_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version416_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version417_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version418_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version4191_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version419_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version420_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version421_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version422_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version423_.st M Glamour-Core.package/GLMAction.class/definition.st A Glamour-Core.package/GLMAction.class/instance/accessing/enabledCondition.st A Glamour-Core.package/GLMAction.class/instance/accessing/enabledCondition_.st A Glamour-Core.package/GLMAction.class/instance/testing/isEnabledOn_.st A Glamour-Core.package/GLMPresentation.class/instance/scripting actions/selectionAct_entitled_enabledWhen_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50761.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50762.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50761.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50762.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50762 19205 [Backport] Pharo 5: Enable / Disable options in context Menu in FastTable https://pharo.fogbugz.com/f/cases/19205 http://files.pharo.org/image/50/50762.zip

Oct. 25, 2016

[pharo-project/pharo-core] 4a07c2: 60268

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 4a07c2a919a25a29ecc26483fda83c7bf3ada95d https://github.com/pharo-project/pharo-core/commit/4a07c2a919a25a29ecc26483… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-10-25 (Tue, 25 Oct 2016) Changed paths: M Refactoring-Core.package/RBRefactoring.class/instance/preconditions/checkPreconditions.st M Refactoring-Core.package/RBRenameTemporaryRefactoring.class/instance/preconditions/preconditions.st M Refactoring-Core.package/RBRenameTemporaryRefactoring.class/instance/tranforming/renameNode_.st M Refactoring-Core.package/RBRenameTemporaryRefactoring.class/instance/tranforming/transform.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60267.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60268.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60267.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60268.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60268 19238 RBRenameTemporaryRefactoring do not set oldName if one of the optional precondition is not valid https://pharo.fogbugz.com/f/cases/19238 http://files.pharo.org/image/60/60268.zip

Oct. 25, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60268 Home: https://github.com/pharo-project/pharo-core

Oct. 25, 2016

Re: [Pharo-dev] [REMEMBER] TechTalk tomorrow 16UTC

by Blondeau Vincent

You can make links that never expires (unless you deactivate them) (else it is 30 minutes): https://discord.gg/jyVT2dp Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Esteban Lorenzano EnvoyÃ© : mardi 25 octobre 2016 09:27 Ã : Pharo Development List Objet : Re: [Pharo-dev] [REMEMBER] TechTalk tomorrow 16UTC instant invites expires very fast. I will be sending a new one before the meeting. Esteban On 25 Oct 2016, at 04:57, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com<mailto:hernan.morales@gmail.com>> wrote: 16:00 UTC is 13:00hs in Argentina but the link now (23:57hs) says "The instant invite is invalid or has expired" 2016-10-24 12:08 GMT-03:00 phil(a)highoctane.be<mailto:phil@highoctane.be> <phil(a)highoctane.be<mailto:phil@highoctane.be>>: https://discord.gg/EBDhD On Mon, Oct 24, 2016 at 4:44 PM, Blondeau Vincent <vincent.blondeau(a)worldline.com<mailto:vincent.blondeau@worldline.com>> wrote: I think that his tomorrow is Tuesday, because he sent the email Monday (CEST). But, I will be interested by a link to find the TechTalk on discord too. Thanks Vincent > -----Message d'origine----- > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org<mailto:pharo-dev-bounces@lists.pharo.org>] De la part de > Dale Henrichs > EnvoyÃ© : lundi 24 octobre 2016 16:35 > Ã : pharo-dev(a)lists.pharo.org<mailto:pharo-dev@lists.pharo.org> > Objet : Re: [Pharo-dev] [REMEMBER] TechTalk tomorrow 16UTC > > Hmmm... since Esteban sent the email at 1 am my time and this _is_ > tomorrow for me ... but perhaps Esteban means Tuesday? since I think this is > still _today_ in Europe? > > Dale > > > On 10/24/16 7:31 AM, Dale Henrichs wrote: > > Since time is short (for me) and I still have to get out ouf bed, > > shower eat and maybe get into the office before the meeting ... could > > someone drop me an email with the details I need to find and install > > (?) discord and find the techtalk ... I'll be out of pocket for about > > an hour getting ready --- as this is short notice (for me) --- > > > > Thanks, > > > > Dale > > > > On 10/24/16 12:58 AM, Esteban Lorenzano wrote: > >> Hello fellow pharoers, > >> > >> The time has come (1 month passes so fast!). And tomorrow we will be > >> handling another TechTalk. > >> This time we propose to talk about the new Bootstrap process. > >> > >> For this, Iâd ask Guille, Pavel and/or Christophe to be present. They > >> are the ones actually working on it, so weâll all learn from what > >> they have to say :) > >> > >> Meeting will be handled with discord, as last time. > >> > >> And as always, this will also be a place to ask anything about pharo > >> development (statuses, proposals, etc., etc., etc.) > >> > >> See you tomorrow ! > >> > >> Esteban > > > !!!************************************************************************************* "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!" !!!************************************************************************************* "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

Oct. 25, 2016

Re: [Pharo-dev] [REMEMBER] TechTalk tomorrow 16UTC

by Esteban Lorenzano

instant invites expires very fast. I will be sending a new one before the meeting. Esteban > On 25 Oct 2016, at 04:57, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > > 16:00 UTC is 13:00hs in Argentina but the link now (23:57hs) says "The instant invite is invalid or has expired" > > 2016-10-24 12:08 GMT-03:00 phil(a)highoctane.be <mailto:phil@highoctane.be> <phil(a)highoctane.be <mailto:phil@highoctane.be>>: > https://discord.gg/EBDhD <https://discord.gg/EBDhD> > > On Mon, Oct 24, 2016 at 4:44 PM, Blondeau Vincent <vincent.blondeau(a)worldline.com <mailto:vincent.blondeau@worldline.com>> wrote: > I think that his tomorrow is Tuesday, because he sent the email Monday (CEST). > But, I will be interested by a link to find the TechTalk on discord too. > > Thanks > > Vincent > > > -----Message d'origine----- > > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org <mailto:pharo-dev-bounces@lists.pharo.org>] De la part de > > Dale Henrichs > > EnvoyÃ© : lundi 24 octobre 2016 16:35 > > Ã : pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org> > > Objet : Re: [Pharo-dev] [REMEMBER] TechTalk tomorrow 16UTC > > > > Hmmm... since Esteban sent the email at 1 am my time and this _is_ > > tomorrow for me ... but perhaps Esteban means Tuesday? since I think this is > > still _today_ in Europe? > > > > Dale > > > > > > On 10/24/16 7:31 AM, Dale Henrichs wrote: > > > Since time is short (for me) and I still have to get out ouf bed, > > > shower eat and maybe get into the office before the meeting ... could > > > someone drop me an email with the details I need to find and install > > > (?) discord and find the techtalk ... I'll be out of pocket for about > > > an hour getting ready --- as this is short notice (for me) --- > > > > > > Thanks, > > > > > > Dale > > > > > > On 10/24/16 12:58 AM, Esteban Lorenzano wrote: > > >> Hello fellow pharoers, > > >> > > >> The time has come (1 month passes so fast!). And tomorrow we will be > > >> handling another TechTalk. > > >> This time we propose to talk about the new Bootstrap process. > > >> > > >> For this, Iâd ask Guille, Pavel and/or Christophe to be present. They > > >> are the ones actually working on it, so weâll all learn from what > > >> they have to say :) > > >> > > >> Meeting will be handled with discord, as last time. > > >> > > >> And as always, this will also be a place to ask anything about pharo > > >> development (statuses, proposals, etc., etc., etc.) > > >> > > >> See you tomorrow ! > > >> > > >> Esteban > > > > > > > > !!!************************************************************************************* > "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!" > >

Oct. 25, 2016

Re: [Pharo-dev] [ANN] Scale

by phil＠highoctane.be

Python has virtualenv, where one can install its own little world. There is no reason we couldn't have an equivalent where a base scale image is copied and updated with whatever we feel like. http://docs.python-guide.org/en/latest/dev/virtualenvs/ Phil On Tue, Oct 25, 2016 at 5:59 AM, Ben Coman <btc(a)openinworld.com> wrote: > On Mon, Oct 24, 2016 at 5:48 PM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > > Really nice project, Santiago. > > > > I have few questions: > > > > - what "system saveAfterRun" actually do? > > > > As I understand it saves image when script completes. Imaging during > script > > I loaded Seaside. Does this command makes Seaside accessible from any > scale > > scripts? > > Image persistence is one of Pharo's most useful features, but I think > its a liability for a system scripting environment. As a > philosophical point, Python/Ruby (somewhat) guarantee scripts start > with the same state each time they are run. I believe this is an > important attribute for system scripting. "saveAfterRun" seems > detrimental to that because you can break the environment for other > scripts, and you can't just reset state by deleting you script. Also > its harder to share scripts since dependencies are not recorded in the > script if the system state has changed. Python/Ruby handle this via a > module import/require facility. Perhaps Scale could provide a > facility to install a Configuration, then export it via Fuel as a > "module" that could be imported into Scale scripts. Loading via Fuel > should be fast enough (??) that Seaside could be accessible from any > Scale script without too much runtime overhead. (I'll add this as an > Issue if discussion indicates interest). > > cheers -ben > > > > > > - system execute: aString into: anImageBundle > > > > What is anImageBundle here? > > > > - What you think to make scripts working as workspace? All undeclared > > variables will be added to environment automatically. And in case of > > saveAfterRun they will became accessible from any scale scripts. > > > > > > 2016-10-23 20:34 GMT+02:00 Santiago Bragagnolo > > <santiagobragagnolo(a)gmail.com>: > >> > >> Hi everybody. > >> > >> We are officially releasing a first version of scale. > >> > >> Scale is a command line handler that is there for making easier the life > >> of the people that uses scripting in linux. As such, we only tested it > so > >> far in linux. It will be for sure easy to adapt it to mac because its a > >> *nix, but not for windoze. > >> > >> IMPORTANT REMARK: scale is not meant to develop applications, it is > meant > >> to develop scripts in Pharo, to be launched from the command line. This > >> means that scale does not provide a top level syntax to declare classes > or > >> methods: people should do that as any normal Pharo application. Scale > should > >> be used to invoke such applications. > >> > >> When would you use scale? > >> - For example, to replace some bash scripts used for common boring > tasks > >> (and you are using python or ruby there :P) > >> - Another example, would be when you want to replace bash scripts that > >> chain things like: > >> ./pharo eval --save "something" > >> ./pharo eval --save "other something" > >> ... > >> > >> Github: https://github.com/guillep/Scale > >> Oneliner to install: (note it needs sudo) > >> > >> wget -O- > >> https://raw.githubusercontent.com/guillep/Scale/master/setupScale.sh | > sudo > >> bash > >> > >> > >> In the repository there is some user level documentation based on > examples > >> and a list of available methods on the magical variable system. There > are > >> many examples as well on the repository. > >> > >> Last but not least, I'm using this project in others two projects, where > >> it proof it self quite powerful what keeps me on maintaining Scale. > >> > >> These projects are: > >> > >> Pharo Android VM building https://github.com/sbragagnolo/pharo-vm > >> > >> Here I use it for automating the creation of a > >> * new building image, > >> * the creation of new resource image (for deploying on the > android > >> apk), > >> * linking the android sources into the building directory > >> * generating the code from the console > >> > >> MakrosTool https://github.com/sbragagnolo/MakrosTool > >> > >> MakrosTool is an extension of scale that adds a second magical variable > >> for building up component reification in a ROS based environment. > >> > >> > >> Santiago & Guille > >> > >> > >> > >> > >> > > > >

Oct. 25, 2016