- Pharo-dev - lists.pharo.org

[ANN] Pharo Consortium New Platinum Member: IngenieurbÃ¼ro fÃ¼r Bauwesen Schmidt GmbH

by Marcus Denker

The Pharo Consortium is very happy to announce that IngenieurbÃ¼ro fÃ¼r Bauwesen Schmidt GmbH has joined the Consortium as a Platinum Member. About - IngenieurbÃ¼ro fÃ¼r Bauwesen Schmidt GmbH: http://bauing-schmidt.de - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: - http://association.pharo.org

Oct. 24, 2017

[ANN] sha256 checksum for Pharo6 downloads

by Marcus Denker

Hi, A tiny first step: I added sha256 chechsums for all downloads created by the Pharo6 build process https://ci.inria.fr/pharo/ <https://ci.inria.fr/pharo/> This step: https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-5-Publish/ <https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-5-Publish/> now creates .sha256.txt files, e.g for the mac: https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-5-Publish/lastSuccessfu… <https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-5-Publish/lastSuccessfu…> This allows to check that downloads from the file server are indeed the same files that the build server created. http://files.pharo.org/platform/ <http://files.pharo.org/platform/> http://files.pharo.org/image/60/ <http://files.pharo.org/image/60/> As I said, just a very first step. TODO: - pgp signatures - insert into website - SSL for files.pharo.org <http://files.pharo.org/> - do it Pharo7 - â¦. So: more to come! Marcus

Oct. 24, 2017

[Pharo 7.0-dev] Build #223: 20580-ValueChanged-should-be-moved-to-System-Model

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

There is a new Pharo build available! The status of the build #223 was: SUCCESS. The Pull Request #390 was integrated: "20580-ValueChanged-should-be-moved-to-System-Model" Pull request url: https://github.com/pharo-project/pharo/pull/390 Issue Url: https://pharo.fogbugz.com/f/cases/20580 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 24, 2017

Re: [Pharo-dev] Bloc status

by Tudor Girba

What Pharo are you using and how did you load the code? Doru > On Oct 24, 2017, at 3:49 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Tudor Girba-2 wrote >> In the meantime, the file is in: >> ./pharo-local/iceberg/feenkcom/gtoolkit-visualizer/doc/mondrian/index.pillar > > I don't seem to even have ./pharo-local/iceberg! > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > -- www.tudorgirba.com www.feenk.com "Don't give to get. Just give."

Oct. 24, 2017

Re: [Pharo-dev] Probably stupid... question about string printString.

by Alistair Grant

Hi Torsten, On Sun, Oct 22, 2017 at 10:40:41AM +0200, Torsten Bergmann wrote: > Alistair Grant wrote: > > I can't comment on the original thinking behind this > > The original thinking is simple and as the name says: you want to print the > object (even when it is a string) to be print in a string. > > So it always is a "printObjectInString" instead of a "printObjectAsString" > behavior. Also the resulting string often is a string to easily reconstruct the object. > > So it is not a conversion method. There is #asString for that. Hmm, I knew about #asString, but this was a while ago, so I can't remember why I didn't use it. But thanks for the reminder. > > If we're displaying values such as numbers and strings in a UI, e.g. > > table, we normally don't want the strings always enclosed in quotes. > > There is #displayString for this task (which may return the printString or is overwritten) > and this is common in nearly all Smalltalks I know. Right, so what would be nice is for UI elements / GT toolkit to move to using #displayString by default, and to add String>>displayString that answers the receiver (currently in Pharo String uses the default #printString, which returns the string with quotes). >From memory this has been discussed before, but I couldn't find it, and don't remember the outcome. Thanks, Alistair

Oct. 24, 2017

Re: [Pharo-dev] Bloc status

by Sean P. DeNigris

Tudor Girba-2 wrote > In the meantime, the file is in: > ./pharo-local/iceberg/feenkcom/gtoolkit-visualizer/doc/mondrian/index.pillar I don't seem to even have ./pharo-local/iceberg! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 24, 2017

Re: [Pharo-dev] Iceberg - viewing uncommitted changes

by Alistair Grant

Hi Ben, On Tue, Oct 03, 2017 at 09:36:59PM +0800, Ben Coman wrote: > When the Iceberg [Packages] tab shows "Uncommitted changes", > how do you view what those changes are? > > For example... > $ curl get.pharo.org/70+vm | bash > $ ./pharo-ui > * Open System > Settings > Include system repositories by default = enabled > * Open Tools > Iceberg > "pharo" > * Click <Clone> button > enter "git@github.com:pharo-project/pharo.git" > * Close and reopen Iceberg so the four tabs show > * Select [Packages] tab and sort by "Name" so dirty packages are at top > (btw, GT-Spotter and Reflectivity packages are dirty, but ignore that for now) > * Open System Browser, randomly select AST-Core > NumberParser > allowPlusSign > * Change the comment, save, enter author details. > * Not sure how to refresh [Packages] tab, so close and reopen Iceberg and > select [Packages] tab, sorted by "Name" > ==> "AST_Core" shows "Uncomitted changes" > So from here, how can I view what the uncommitted changes of that package are? > I partly expect it in the context menu of AST_Core package. > > cheers -ben I'm way behind on my list reading, so you've probably already figured this out, but just in case, or maybe someone has a better answer... If you right click on the repository and select "Synchronize repository.." (Ctrl-S) you'll get a dialog displaying all the changes displayed as a tree, with the package at the top level. Cheers, Alistair > P.S. Currently, when I open Iceberg I'm habitually first selecting the > [Packages] and [Branches] tabs. If I first select [Remotes] & "origin" > followed by... > * [Packages] ==> Instance of IceScpRemote did not understand #entity > * [Branches] ==> Instance of IceScpRemote did not understand #isBranchModel

Oct. 24, 2017

[Pharo 7.0-dev] Build #222: 20575-TextMorph-cannot-work-without-code-completion-temporary-solution

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

There is a new Pharo build available! The status of the build #222 was: SUCCESS. The Pull Request #387 was integrated: "20575-TextMorph-cannot-work-without-code-completion-temporary-solution" Pull request url: https://github.com/pharo-project/pharo/pull/387 Issue Url: https://pharo.fogbugz.com/f/cases/20575 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 24, 2017

Re: [Pharo-dev] System Update Failure from #60510 -> #60513

by Marcus Denker

Hi, I have copied it over! Thanks, Marcus > On 22 Oct 2017, at 03:55, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Marcus Denker-4 wrote >> yes, can you send it to me? I will add it. > > It's in the Pharo60Inbox. Of course I can still send it to you if that would > helpâ¦ > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Oct. 24, 2017

[Pharo 7.0-dev] Build #221: 20573-BaselineOfMorphic-should-include-System-Identification

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

There is a new Pharo build available! The status of the build #221 was: SUCCESS. The Pull Request #384 was integrated: "20573-BaselineOfMorphic-should-include-System-Identification" Pull request url: https://github.com/pharo-project/pharo/pull/384 Issue Url: https://pharo.fogbugz.com/f/cases/20573 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 24, 2017