- Pharo-users - lists.pharo.org

double dispatch example

by stepharo

Hi If you happen to know a double dispatch situation in Pharo, I'm interested since I'm revisiting my lecture. Stef

Sept. 13, 2016

Re: [Pharo-users] Iceberg and git workflow

by Nicolas Passerini

Hi Holger, I think that both patterns are currently supported (in beta version), but maybe we do not use exactly the same tools. First, Iceberg does not use the concept of "stash". The git stash changes the file in your git working copy (on your file system), while your (modified) code is not there, is in the Pharo image. Going deeper into it, we understand git is very powerful but we do not believe that git is the ultimate perfect code versioning tool. We think that there are some git usage patterns that tend to be difficult to understand so we are trying to create a better abstraction on top of that. Also we would like to come up with an abstraction that works not only for git but for other repositories. So, we try to support the kind of requirements you are worried about, but maybe not in the same way that the command line tools you are used to. I also have been working with git in languages like Scala, Javascript, Xtend, etc and I was used to the command line tools... so now the task for me is to try to understand: which of all those things I was used to do were really necessary and which of them are just boilerplate I need to do because of my tools are too low level? Maybe your experience can help us answer that question. > a.) If current HEAD is same as origin/master > > $ git stash (stash away my not finished changes) > $ vi code.c fix.. > $ git commit -a -c "subject > > long explanation of fix > reference to bug" > $ git stash apply (and go back to working on my feature) > > So, why is this better than having a new image with a clean version of HEAD? > b.) E.g. if I finished n-commits but I am not fully done > For this I would propose a slightly different pattern: > > # store my work > $ git commit -a -m "Work In Progress hack.." > You can commit, ok... but also you could just save the image with your work in progress, no need to create a hacky commit. > $ git checkout -b new-feature-branch > > # go back to master > $ git checkout master > $ git reset --hard origin/master (to restore) > To avoid reset, I would propose to leave master like that and put the new work in a clean branch, starting on origin/master. In git-command-line language it would be: git checkout -b fix origin/master So you create a new branch for your fix out of origin/master, leaving the original branch untouched. > > # work on the fix > $ vi code.c fix.. > $ git commit -a -c "fix..." > > No problems here... just we do not use vi for editing code :) > # go back and continue on my fix > $ git checkout new-feature-branch > $ git rebase origin/master > $ git reset HEAD^1 > .. continue to work > > Several things here. First, I think that everything is simpler if you just leave your original branch untouched, so you could re-checkout that branch without the need for reset and removing hacky commits. But even more interesting if you agree to have two images one for each task, you just go back to your first image and everything is just like you left it, including open windows and whatever task you were doing. I think that is a beautiful value of Pharo I would not like to loose. The only thing left would be to incorporate the fix into this image, right now we do not support rebase, you would need to merge... but I understand why one would prefer rebase in this scenario, at some point we will support both options. So, to sum up. I am not trying to replicate in Pharo the way I used to work in Javascript... I think that would be silly. Instead, we are trying to take the good stuff of git into Pharo, but without loosing all the good stuff of Pharo.

Sept. 13, 2016

Re: [Pharo-users] Seaside not installing

by stepharo

thanks for the alarm and tx esteban for the fix. Le 13/9/16 Ã 08:58, Hersh Krishna via Pharo-users a Ã©crit :

Sept. 13, 2016

Re: [Pharo-users] Problem cleaning up image

by Marcus Denker

Hi, I think it is not really realistic to expect this to work *after* loading code of others. Why not -> do image clean -> *then* load the packages you need? Marcus > On 13 Sep 2016, at 03:19, Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > > Ok, I did some extra tests and I think I figured what is happening: the code I load on the image subject to clean has a startUp method that starts a Teapot server on port 8080. I tried various scenarios: > > 1- Load a fresh image from get.pharo.org <http://get.pharo.org/> and execute clean --> Ok > 2- Load a fresh image from get.pharo.org <http://get.pharo.org/> only with the dependencies from my project (ConfigurationOfTwitterChallenge), one at a time, and execute clean --> Ok > 3- Load a fresh image from get.pharo.org <http://get.pharo.org/>, apply ConfigurationOfTwitterChallenge and execute clean --> Fail > 4- Load a fresh image from get.pharo.org <http://get.pharo.org/>, apply ConfigurationOfTwitterChallenge and execute eval "TwitterChallengeMain stopDefaultExecution. ImageCleaner cleanUpForProduction. Smalltalk snapshot: true andQuit: true." --> Ok (Assuming ImageCleaner cleanUpForProduction. Smalltalk snapshot: true andQuit: true. does the same as clean --production) > > It appears I cannot clean an Image with the server started. Question: is that an error or I really should not try to clean an image with a server on? If the former I open an issue on FogBuz and I will try on a not-headless vm to see if some error happen. > > Regards, > Vitor > > > > On Mon, Sep 12, 2016 at 6:59 AM, stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote: > Ok may be this is just an endless loop :) > > > > Le 12/9/16 Ã 10:22, Marcus Denker a Ã©crit : >> Hello, >> >> Yes, this is a bug that we really need to fix. >> (sadly no information to add other thant that). >> >>> On 09 Sep 2016, at 15:16, Vitor Medina Cruz <vitormcruz(a)gmail.com <mailto:vitormcruz@gmail.com>> wrote: >>> >>> Hello, >>> >>> Isn't cleanup the headless image working right now? I know it has some problems, but I tried to: >>> >>> curl get.pharo.org <http://get.pharo.org/> | bash >>> ./pharo Pharo.image clean --production >>> >>> It runs for hours and don't complete. Last time I leave it for about 5 hours before I cancelled. >>> >>> Regards, >>> Vitor >> > >

Sept. 13, 2016

Re: [Pharo-users] Iceberg and git workflow

by Christophe Demarey

> Le 12 sept. 2016 Ã 22:20, Stephan Eggermont <stephan(a)stack.nl> a Ã©crit : > > On 12/09/16 21:51, Christophe Demarey wrote: >> I think your scenario is not covered by Iceberg. It could be a nice feature but not one of the most important. > > Why do you think so? In my mind, the top priorities are to have a UI allowing to easily: - clone a repository - sync with a remote - a good diff and merge support - an easy way to understand the project history (among all branches): log, visual graph of branches and versions - choose what you want to commit (even if we do not use git index) - easy switch to another tag, branch (- and use of libgit instead of gitfiletree: important for windows users) I see git stash usage less important than this one. But maybe it is a top-priority feature for some people heavily relying on it. Anyway, the best way is to play/use Iceberg and give feedback to Nicolas about what is good, what could be improved / added. We just need to take care that Nicolas has limited time and, at some point, we need to take decisions.

Sept. 13, 2016

Re: Seaside not installing

by Hersh Krishna

All right, that push seemed to fix it. Thanks for helping me out. I thought I was going insane since I always seem to get the wierdest errors. -- View this message in context: http://forum.world.st/Seaside-not-installing-tp4915283p4915290.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 13, 2016

Re: Seaside not installing

by Hersh Krishna

I'm on Pharo 5 currently. Its the latest image you get from the shell script on the download page. -- View this message in context: http://forum.world.st/Seaside-not-installing-tp4915283p4915288.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 13, 2016

Re: [Pharo-users] Seaside not installing

by Esteban A. Maringolo

I just uploaded a new Metacello config that, I hope, fixes a reference to Cryptography package that for some reason stopped working. After changing this I had 1010 (all) Seaside-Tests passing. Name: ConfigurationOfSeaside3-EstebanMaringolo.312 Author: EstebanMaringolo Time: 13 September 2016, 1:04:36.108636 am UUID: 57a8dff5-a6da-4e91-be29-7628e93171ae Ancestors: ConfigurationOfSeaside3-pmm.311 Fixes #baseline320security: that had a specific spec and package reference for Pharo that wasn't working. Now it uses the same #squeakCommon spec. Regards, Esteban A. Maringolo 2016-09-12 23:22 GMT-03:00 Ben Coman <btc(a)openinworld.com>: > On Tue, Sep 13, 2016 at 10:09 AM, Hersh Krishna via Pharo-users > <pharo-users(a)lists.pharo.org> wrote: >> >> ---------- Forwarded message ---------- >> From: Hersh Krishna <hershkrishna(a)protonmail.ch> >> To: pharo-users(a)lists.pharo.org >> Cc: >> Date: Mon, 12 Sep 2016 19:05:06 -0700 (PDT) >> Subject: Seaside not installing >> When I try to install seaside via the Catalog Browser I get an error >> "MetacelloNameNotDefinedError", which says that a crypto library is missing. >> Is this my fault or is the build just broken right now? > > Hi Hersh, > > Which version of Pharo are you on? > > cheers -ben >

Sept. 13, 2016

Re: [Pharo-users] Seaside not installing

by Ben Coman

On Tue, Sep 13, 2016 at 10:09 AM, Hersh Krishna via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > ---------- Forwarded message ---------- > From: Hersh Krishna <hershkrishna(a)protonmail.ch> > To: pharo-users(a)lists.pharo.org > Cc: > Date: Mon, 12 Sep 2016 19:05:06 -0700 (PDT) > Subject: Seaside not installing > When I try to install seaside via the Catalog Browser I get an error > "MetacelloNameNotDefinedError", which says that a crypto library is missing. > Is this my fault or is the build just broken right now? Hi Hersh, Which version of Pharo are you on? cheers -ben

Sept. 13, 2016

Seaside not installing

by Hersh Krishna

When I try to install seaside via the Catalog Browser I get an error "MetacelloNameNotDefinedError", which says that a crypto library is missing. Is this my fault or is the build just broken right now? -- View this message in context: http://forum.world.st/Seaside-not-installing-tp4915282.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 13, 2016