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

Re: [Pharo-dev] [Ann] TaskIt v1.0

by Norbert Hartl

Great, thanks! Does TaskIt include implementations for combining futures such as the ALL and the ANY futures which resolve either when all or one future resolves? From the documentation it looks that rather not. Norbert > Am 29.11.2018 um 15:29 schrieb Santiago Bragagnolo <santiagobragagnolo(a)gmail.com>: > > Hi everybody :). > > I am happy to announce TaskIt v1.0. > > In this version we add some new features, passed over the red tests and clean up some dead code. And did a pass in the documentation > > A bit from the DOC > Downloading > > Current stable version of taskit can be downloaded using metacello as follows: > > Metacello new > baseline: 'TaskIt'; > repository: 'github://sbragagnolo/taskit'; > load. > If you want a specific release such as v1.0, you can load the associated tag as follows > > Metacello new > baseline: 'TaskIt'; > repository: 'github://sbragagnolo/taskit:v1.0'; > load. > Otherwise, if you want the latest development version, take a look at the development branchs and load the latest: > > Metacello new > baseline: 'TaskIt'; > repository: 'github://sbragagnolo/taskit:dev-1.1'; > load. > <https://github.com/sbragagnolo/taskit/blob/master/README.md#major-features>Major Features > > Actors (ActIt) > Configuration Profiles > Service > > Check specially the configuration profiles. The default profile usage is #development, which sets up the environment for debugging exceptions in a process. > > I want to thank a lot to the contributors, Guillermo Polito Max Leske and Daniel Sasu. > I want as well to thanks the users, specially to those that bring me feedback (blames and ideas) in person (Esteban, Pablo) or through the different channels (Holger Freyther, Juraj Kubelka, Philippe Back). > > > I want also to apologise the delay of my responses on the issue board :) (Really, sorry). I am constantly using TaskIt in other projects, but much times I cannot do it my priority. > > > thanks a lot, > > Santiago Bragagnolo. > > > > > > > > >

Nov. 29, 2018

[Ann] TaskIt v1.0

by Santiago Bragagnolo

Hi everybody :). I am happy to announce TaskIt v1.0. In this version we add some new features, passed over the red tests and clean up some dead code. And did a pass in the documentation A bit from the DOC Downloading Current stable version of taskit can be downloaded using metacello as follows: Metacello new baseline: 'TaskIt'; repository: 'github://sbragagnolo/taskit'; load. If you want a specific release such as v1.0, you can load the associated tag as follows Metacello new baseline: 'TaskIt'; repository: 'github://sbragagnolo/taskit:v1.0'; load. Otherwise, if you want the latest development version, take a look at the development branchs and load the latest: Metacello new baseline: 'TaskIt'; repository: 'github://sbragagnolo/taskit:dev-1.1'; load. <https://github.com/sbragagnolo/taskit/blob/master/README.md#major-features>Major Features - Actors (ActIt) - Configuration Profiles - Service Check specially the configuration profiles. The default profile usage is #development, which sets up the environment for debugging exceptions in a process. I want to thank a lot to the contributors, Guillermo Polito Max Leske and Daniel Sasu. I want as well to thanks the users, specially to those that bring me feedback (blames and ideas) in person (Esteban, Pablo) or through the different channels (Holger Freyther, Juraj Kubelka, Philippe Back). I want also to apologise the delay of my responses on the issue board :) (Really, sorry). I am constantly using TaskIt in other projects, but much times I cannot do it my priority. thanks a lot, Santiago Bragagnolo.

Nov. 29, 2018

[Pharo 7.0-dev] Build #1424: 22711-Improve-Cursor-class-comment

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

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

Nov. 29, 2018

[Pharo 7.0-dev] Build #1423: 22568-ContextcompleteCallee-is-dead-code-new-pr

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

There is a new Pharo build available! The status of the build #1423 was: SUCCESS. The Pull Request #1926 was integrated: "22568-ContextcompleteCallee-is-dead-code-new-pr" Pull request url: https://github.com/pharo-project/pharo/pull/1926 Issue Url: https://pharo.fogbugz.com/f/cases/22568 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 29, 2018

[Pharo 7.0-dev] Build #1422: 22708 Tag ManifestRingChunkImporter and related classes

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

There is a new Pharo build available! The status of the build #1422 was: SUCCESS. The Pull Request #2019 was integrated: "22708 Tag ManifestRingChunkImporter and related classes" Pull request url: https://github.com/pharo-project/pharo/pull/2019 Issue Url: https://pharo.fogbugz.com/f/cases/22708 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 29, 2018

[Pharo 7.0-dev] Build #1421: 22709 Tag ManifestRingCoreContainers and related classes

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

There is a new Pharo build available! The status of the build #1421 was: SUCCESS. The Pull Request #2020 was integrated: "22709 Tag ManifestRingCoreContainers and related classes" Pull request url: https://github.com/pharo-project/pharo/pull/2020 Issue Url: https://pharo.fogbugz.com/f/cases/22709 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 29, 2018

Re: [Pharo-dev] Version control of Playground scripts

by Norbert Hartl

> Am 29.11.2018 um 11:15 schrieb Christopher Fuhrman <christopher.fuhrman(a)inria.fr>: > > > > On Wed, 28 Nov 2018 at 10:23, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: >> Am 28.11.2018 um 09:38 schrieb Christopher Fuhrman <christopher.fuhrman(a)inria.fr <mailto:christopher.fuhrman@inria.fr>>: >> >> Knowing Playground files are saved on local disk, I got to thinking... What would be the risk(s) of using git outside Pharo, on the Playground files' directory? Has anyone tried that before? >> > It is not a problem. I use this every day. Meaning all my repos have a scripts folder where I put my helper scripts. In the image I open this with > > âscriptsâ asFileReference inspect > > This is great. Thanks! > > so you get kind of a file browser of all the scripts. If you call the files with an extension of .st you get syntax highlighting. If you change a script with cmd-s the file gets modified and you can check into git. The problem here is that if you have modifications in the image you should commit that first because if you do on the scripts folder first the image working copy is detached and there is no easy way to commit your in-image changes. You would have to do a branch which is cumbersome. > > I'm a bit lost here: > > 1. Are you using Iceberg within Pharo (when you speak of "committing that first"), or are you using only git outside of Pharo? Also, I think it's possible to use a git repo with monticello? > 2. I'm not an advanced git user, so how do I set up my Pharo image directory to work with the 'scripts' folder (again, with Iceberg if possible, as it seems to be the most user-friendly)? > > Thanks for your patience with my beginner questions. > You are welcome. We like to share with people that want to know ;) The problem in understanding is a hard one. Using git means there are two repositories, one online in the git server and the working copy you checked out locally. When using pharo there is a third one and that is the working copy within your image. Having these two there is a number of conflicts possible. As pharo does not manage external resources like these scripts you can have trouble here. When you go to the command line and commit the script and you go back to pharo it tells you that you are in detached state. It means that the git index is not the same as it was when you loaded stuff via pharo. That is why I was saying that a good flow would first commit the pharo changes and then the ones on the command line. Hope this helps, Norbert > Cheers, > > Christopher > > With the scripts in place I have developed a workflow of creating new images. I have a script that downloads a new image and renames it for the project. And if it finds a script > > scripts/prepare-image.st <http://prepare-image.st/> > > it gets executed. This contains metacello commands to load the project code and settings I need in a new image. This way it is super easy to create a new image for your work. And as all the scripts you use are on the filesystem there is usually no state in the image that needs to be transferred to a new image. > > Norbert > >

Nov. 29, 2018

Re: [Pharo-dev] Version control of Playground scripts

by Christopher Fuhrman

On Wed, 28 Nov 2018 at 10:23, Norbert Hartl <norbert(a)hartl.name> wrote: > Am 28.11.2018 um 09:38 schrieb Christopher Fuhrman < > christopher.fuhrman(a)inria.fr>: > > Knowing Playground files are saved on local disk, I got to thinking... > What would be the risk(s) of using git outside Pharo, on the Playground > files' directory? Has anyone tried that before? > > It is not a problem. I use this every day. Meaning all my repos have a > scripts folder where I put my helper scripts. In the image I open this with > > âscriptsâ asFileReference inspect > This is great. Thanks! > so you get kind of a file browser of all the scripts. If you call the > files with an extension of .st you get syntax highlighting. If you change a > script with cmd-s the file gets modified and you can check into git. The > problem here is that if you have modifications in the image you should > commit that first because if you do on the scripts folder first the image > working copy is detached and there is no easy way to commit your in-image > changes. You would have to do a branch which is cumbersome. > I'm a bit lost here: 1. Are you using Iceberg within Pharo (when you speak of "committing that first"), or are you using only git outside of Pharo? Also, I think it's possible to use a git repo with monticello? 2. I'm not an advanced git user, so how do I set up my Pharo image directory to work with the 'scripts' folder (again, with Iceberg if possible, as it seems to be the most user-friendly)? Thanks for your patience with my beginner questions. Cheers, Christopher > With the scripts in place I have developed a workflow of creating new > images. I have a script that downloads a new image and renames it for the > project. And if it finds a script > > scripts/prepare-image.st > > it gets executed. This contains metacello commands to load the project > code and settings I need in a new image. This way it is super easy to > create a new image for your work. And as all the scripts you use are on the > filesystem there is usually no state in the image that needs to be > transferred to a new image. > > Norbert > > >

Nov. 29, 2018

[Pharo 7.0-dev] Build #1420: 22710 Tag ManifestDeprecatedFileStream and related classes

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

There is a new Pharo build available! The status of the build #1420 was: SUCCESS. The Pull Request #2021 was integrated: "22710 Tag ManifestDeprecatedFileStream and related classes" Pull request url: https://github.com/pharo-project/pharo/pull/2021 Issue Url: https://pharo.fogbugz.com/f/cases/22710 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 29, 2018

Re: [Pharo-dev] Excel export with Tabular

by Ben Coman

On Tue, 13 Nov 2018 at 05:42, Hans-Martin Mosner <pharo-dev(a)fam-mosner.de> wrote: > I put it on ss3 because I'm not yet familiar with the way Pharo uses > github. Will look into it later. > > I'm unsure how git repositories are used in the Pharo context. Do you use > them just like you use git normally (i.e. I > use my git repository, you use yours and send me pull requests etc...). > Yes. Exactly like that. cheers -ben

Nov. 28, 2018