June 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Help contributing a fix to pharo - docs seem out of date again?

by Guillermo Polito

Ah! Yes, in the Pharo plugin you have just that option. What we were saying with Esteban is that if you go to the *Repair* and then *Create new Branch* you should have it. But in the main menu you don't have a "Checkout branch" option? That's then maybe a bug, I'll check. On Tue, Jun 19, 2018 at 5:45 PM Tim Mackinnon <tim(a)testit.works> wrote: > Hi guys - I got build 1072 using Pharo Launcher (I like to know what build > Iâm using - but maybe I should pick stable and just date stamp my image?) > > Anyway just tried the latest 1077 and followed the steps I described > (although using my caught up branch) - when I right click on the detached > pharo - there is the Pharo menu item and inside that there is only the > option to create a new branch for an issue? > > Am I missing something (or is this something recently broken?) > > Tim > > On 19 Jun 2018, at 14:35, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > Strange... I'm with Esteban there, I'd need more information to reproduce > it. > I've just done > > $ wget -O - get.pharo.org/70+vm | bash > $ ./pharo-ui Pharo.image > > - Open iceberg > - Repair Pharo by cloning my (really out of date) fork (guillep/pharo) > - Fetch > - Repair -> Create branch > > And I have the "New branch" option. > > On Tue, Jun 19, 2018 at 3:28 PM Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> >> >> On 19 Jun 2018, at 15:18, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Hi Guillermo - it sounds like Iâm on the right track - the only thing >> that caught me out was in the latest V7 there is no ânew branchâ - I have >> to have an issue number? The picture in your doc shows both possibilities? >> >> >> how did you arrive there? >> seems to me that there should always be the opportunity of just branch. >> If not, may be there is an error. >> >> Esteban >> >> >> For now, I found a bug and created an issue, and so can experiment with >> that - but I think it is handy to create a generic branch so that you can >> experiment (while easily tracking your changes)? >> >> Tim >> >> On 19 Jun 2018, at 14:01, Guillermo Polito <guillermopolito(a)gmail.com> >> wrote: >> >> Hi, >> >> On Tue, Jun 19, 2018 at 2:26 PM Tim Mackinnon <tim(a)testit.works> wrote: >> >>> Hi - a few weeks ago, I contributed a tiny fix to Pharo 7 -and the >>> instructions seemed to work really well. >>> >>> Iâve since come back to try and do some more over lunch (I was thinking >>> Iâd like to dig out the changes I worked out for using the AST and cursor >>> to make senders/implements work properly and not just use the selected >>> text). >>> >>> My first problem was that my fork of Pharo from many months ago was out >>> of date - I think the instructions on >>> https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo should >>> probably mention this subtlety. >>> >> >>> It took me ages to figure out what to do - this was the clue ( >>> https://help.github.com/articles/syncing-a-fork/) - and of particular >>> note the the tiny bit at the bottom to ensure you Push your changes back to >>> your GitHub fork (I slightly complicated myself by using IntelliJ to do >>> this - doable but you need to be aware of whats going on). I did this in a >>> separate non-pharo directory (I think thats what you would recommend right? >>> Then you can keep updating it from time to time?) >>> >> >> Usually, you don't care. You don't need to update your fork :) >> You only need to: >> - clone/locate your repository in disk >> - fetch (this will find your commit in the pharo repository) >> - create a new branch X >> - push branch X to your fork >> - make a pull request >> >> The contribution process never goes through master nor development, so it >> does not really matter if they are updated. >> And that's what I was showing in my videos because there is nothing else >> to it :) >> >> >>> >>> Having got my GitHub fork caught up with pharo/development - I then have >>> the Local Repo Missing error (expected) - and now when I go to repair it I >>> can either clone again (which is the instructions online) - or âLocate this >>> repository in your file systemâ. As Iâve had to already check everything >>> out to catch up to pharo/dev I chose to locate. >>> >>> I then get a Fetch require msg (expected) >>> >>> I then choose to use Fetch (Iâm not sure what the Repair repository >>> picture is now about?) - the text does mention I will become detached, so >>> Iâve stuck to that >>> >>> Iâm not sure why the âsolving a detached working copyâ is further down >>> the page - but Iâve jumped to that >>> >>> It says I need to synchronise both (image and repo) - but then says its >>> easier to do a branch - and then says a nice alternative is to create a >>> temp branch like temp/synch - however I canât see how to do that as there >>> is only Crete new Branch from Issue now (the picture shows that plus New >>> Branch). >>> >> >> I don't see what's the problem, maybe the UI can be enhanced to be more >> explicit. >> But you can just select "New branch" and create a branch with any name. >> >> I'll go a bit deeper here: >> - you just downloaded a new image that was built from commit 100 >> - In the meantime, while you downloaded your image, a new PR would have >> been integrated in pharo, so now the development branch may not be anymore >> on commit 100 but on commit 101. >> - Even worse! There is no branch at all pointing to 100, your image's >> commit >> - So the safest way to work (because updating the image may be dangerous >> not because of Iceberg :)) is to create a new branch on your commit. >> >> However, while this is the recommended way to work on Pharo, on other >> projects you can do a more normal workflow: checkout, pull. >> >> Does this answer it? Maybe I've missed something? >> >> >> >>> >>> Am I on the right track here? If I want try something out - do I just >>> create myself a new issue (or is there a temp issue anyway?) >>> >>> Tim >>> >> >> >> -- >> >> 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 >> >> >> >> > > -- > > 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 > > > -- 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

June 19, 2018

Re: [Pharo-users] Help contributing a fix to pharo - docs seem out of date again?

by Tim Mackinnon

Hi guys - I got build 1072 using Pharo Launcher (I like to know what build Iâm using - but maybe I should pick stable and just date stamp my image?) Anyway just tried the latest 1077 and followed the steps I described (although using my caught up branch) - when I right click on the detached pharo - there is the Pharo menu item and inside that there is only the option to create a new branch for an issue? Am I missing something (or is this something recently broken?) Tim > On 19 Jun 2018, at 14:35, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Strange... I'm with Esteban there, I'd need more information to reproduce it. > I've just done > > $ wget -O - get.pharo.org/70+vm <http://get.pharo.org/70+vm> | bash > $ ./pharo-ui Pharo.image > > - Open iceberg > - Repair Pharo by cloning my (really out of date) fork (guillep/pharo) > - Fetch > - Repair -> Create branch > > And I have the "New branch" option. > > On Tue, Jun 19, 2018 at 3:28 PM Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > > >> On 19 Jun 2018, at 15:18, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >> >> Hi Guillermo - it sounds like Iâm on the right track - the only thing that caught me out was in the latest V7 there is no ânew branchâ - I have to have an issue number? The picture in your doc shows both possibilities? > > how did you arrive there? > seems to me that there should always be the opportunity of just branch. If not, may be there is an error. > > Esteban > >> >> For now, I found a bug and created an issue, and so can experiment with that - but I think it is handy to create a generic branch so that you can experiment (while easily tracking your changes)? >> >> Tim >> >>> On 19 Jun 2018, at 14:01, Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> wrote: >>> >>> Hi, >>> >>> On Tue, Jun 19, 2018 at 2:26 PM Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >>> Hi - a few weeks ago, I contributed a tiny fix to Pharo 7 -and the instructions seemed to work really well. >>> >>> Iâve since come back to try and do some more over lunch (I was thinking Iâd like to dig out the changes I worked out for using the AST and cursor to make senders/implements work properly and not just use the selected text). >>> >>> My first problem was that my fork of Pharo from many months ago was out of date - I think the instructions on https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo <https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo> should probably mention this subtlety. >>> >>> It took me ages to figure out what to do - this was the clue (https://help.github.com/articles/syncing-a-fork/ <https://help.github.com/articles/syncing-a-fork/>) - and of particular note the the tiny bit at the bottom to ensure you Push your changes back to your GitHub fork (I slightly complicated myself by using IntelliJ to do this - doable but you need to be aware of whats going on). I did this in a separate non-pharo directory (I think thats what you would recommend right? Then you can keep updating it from time to time?) >>> >>> Usually, you don't care. You don't need to update your fork :) >>> You only need to: >>> - clone/locate your repository in disk >>> - fetch (this will find your commit in the pharo repository) >>> - create a new branch X >>> - push branch X to your fork >>> - make a pull request >>> >>> The contribution process never goes through master nor development, so it does not really matter if they are updated. >>> And that's what I was showing in my videos because there is nothing else to it :) >>> >>> >>> Having got my GitHub fork caught up with pharo/development - I then have the Local Repo Missing error (expected) - and now when I go to repair it I can either clone again (which is the instructions online) - or âLocate this repository in your file systemâ. As Iâve had to already check everything out to catch up to pharo/dev I chose to locate. >>> >>> I then get a Fetch require msg (expected) >>> >>> I then choose to use Fetch (Iâm not sure what the Repair repository picture is now about?) - the text does mention I will become detached, so Iâve stuck to that >>> >>> Iâm not sure why the âsolving a detached working copyâ is further down the page - but Iâve jumped to that >>> >>> It says I need to synchronise both (image and repo) - but then says its easier to do a branch - and then says a nice alternative is to create a temp branch like temp/synch - however I canât see how to do that as there is only Crete new Branch from Issue now (the picture shows that plus New Branch). >>> >>> I don't see what's the problem, maybe the UI can be enhanced to be more explicit. >>> But you can just select "New branch" and create a branch with any name. >>> >>> I'll go a bit deeper here: >>> - you just downloaded a new image that was built from commit 100 >>> - In the meantime, while you downloaded your image, a new PR would have been integrated in pharo, so now the development branch may not be anymore on commit 100 but on commit 101. >>> - Even worse! There is no branch at all pointing to 100, your image's commit >>> - So the safest way to work (because updating the image may be dangerous not because of Iceberg :)) is to create a new branch on your commit. >>> >>> However, while this is the recommended way to work on Pharo, on other projects you can do a more normal workflow: checkout, pull. >>> >>> Does this answer it? Maybe I've missed something? >>> >>> >>> >>> Am I on the right track here? If I want try something out - do I just create myself a new issue (or is there a temp issue anyway?) >>> >>> Tim >>> >>> >>> -- >>> >>> 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 >> > > > > -- > > 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

June 19, 2018

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo Launcher v1.2 release

by Sven Van Caekenberghe

> On 19 Jun 2018, at 16:01, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Great work! Indeed. Thank you. > Doru > > >> On Jun 19, 2018, at 3:55 PM, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: >> >> Hi all, >> >> I just released PharoLauncher 1.2. It includes a new windows installer that you can use without administrator privileges as well as binary signing for OS X and Windows. Also, Pharo Launcher is not anymore identified as âPharoâ application and comes with its own icon. >> >> Here is the changelog (details on https://github.com/pharo-project/pharo-launcher/issues) >> New features: >> #21 Bless the DMG >> #46 sign pharo launcher app for windows >> #103 No way to rename a local template >> #107 Unable to add a description for the image using the Launcher UI >> #121 You can't see/sort images by last modified date >> Improvements: >> #69 Import command should also import pharo-local directory >> #70 Import command should delete origin folder if empty >> #73 Managers of Download of VMs and images should be in their own packages >> #76 Use https instead of http to requests the pharo file server >> #82 Official Distributions loads 32bit versions on 64bit System (i.e. provide better information on templates architecture) >> #86 Sort Existing Images Case-Insensitive >> #98 Copy and subfolders problem (contents no copied) >> #101 Templates from a local image are listed in "downloaded". "local" would be a better name >> #102 Template Cleared at Startup setting is enabled, making it weird when trying to use the template feature >> #106 Import could work if we select the parent folder of an image >> #109 Use latest pre-Spur VM to determine the image version >> #122 The Run without settings icon looks like a funny grey/which blob (missing alpha correction) >> Bux fixes: >> #41 #selectedMorphList was sent to nil >> #67 bash is not a command usable under windows >> #68 Does not launch images on Windows >> #85 Double click on an existing image open a file selector >> #88 Pharo Launcher on Windows > Failing >> #104 GUI bug makes Launcher unusable >> #110 Image launch not reliable on Windows >> #119 MessageNotUnderstood exception on launch >> #123 The status bar of the Launcher is broken, so can't easily show image descriptions >> >> >> Big thanks to all contributors: code, issues report, comments, advices. >> >> You can get platform bundles from pharo download page or files.pharo.org: http://files.pharo.org/pharo-launcher/1.2/ >> >> Regards, >> Christophe. > > -- > www.tudorgirba.com > www.feenk.com > > "The coherence of a trip is given by the clearness of the goal." > > > > > >

June 19, 2018

Re: [Pharo-users] [ANN] Pharo Launcher v1.2 release

by Serge Stinckwich

Thank you Christophe for your work ! I really appreciate it. I dl the 64 bits VM for macOS. Everytime I run a 32 bits image, I have a warning that using a 32 bits images, require a 32 bits VM. And then when I select yes, everything works. Why having this warning everytime ? A+ On Tue, Jun 19, 2018 at 2:57 PM Christophe Demarey < christophe.demarey(a)inria.fr> wrote: > Hi all, > > I just released *PharoLauncher 1.2*. It includes a new windows installer > that you can use without administrator privileges as well as binary signing > for OS X and Windows. Also, Pharo Launcher is not anymore identified as > âPharoâ application and comes with its own icon. > > Here is the changelog (details on > https://github.com/pharo-project/pharo-launcher/issues) > New features: > #21 Bless the DMG > #46 sign pharo launcher app for windows > #103 No way to rename a local template > #107 Unable to add a description for the image using the Launcher UI > #121 You can't see/sort images by last modified date > Improvements: > #69 Import command should also import pharo-local directory > #70 Import command should delete origin folder if empty > #73 Managers of Download of VMs and images should be in their own packages > #76 Use https instead of http to requests the pharo file server > #82 Official Distributions loads 32bit versions on 64bit System (i.e. > provide better information on templates architecture) > #86 Sort Existing Images Case-Insensitive > #98 Copy and subfolders problem (contents no copied) > #101 Templates from a local image are listed in "downloaded". "local" > would be a better name > #102 Template Cleared at Startup setting is enabled, making it weird when > trying to use the template feature > #106 Import could work if we select the parent folder of an image > #109 Use latest pre-Spur VM to determine the image version > #122 The Run without settings icon looks like a funny grey/which blob > (missing alpha correction) > Bux fixes: > #41 #selectedMorphList was sent to nil > #67 bash is not a command usable under windows > #68 Does not launch images on Windows > #85 Double click on an existing image open a file selector > #88 Pharo Launcher on Windows > Failing > #104 GUI bug makes Launcher unusable > #110 Image launch not reliable on Windows > #119 MessageNotUnderstood exception on launch > #123 The status bar of the Launcher is broken, so can't easily show image > descriptions > > > *Big thanks to all contributors*: code, issues report, comments, advices. > You can get platform bundles from pharo download page or files.pharo.org: > http://files.pharo.org/pharo-launcher/1.2/ > > Regards, > Christophe. > -- Serge Stinckwich UMI UMMISCO 209 (SU/IRD/UY1) "Programs must be written for people to read, and only incidentally for machines to execute."http://www.doesnotunderstand.org/

June 19, 2018

[ANN] TechTalk Dates second half 2018

by Marcus Denker

Here are the next dates for the Pharo Techtalks. 12 Jul 2018: Pharo TechTalk: Machine Learning with TensorFlow and Pharo https://association.pharo.org/event-2973748 For the others we have no topic yet, but dates are pre-fixed to: 23 Aug 2018: Pharo TechTalk https://association.pharo.org/event-2973753 11 Oct 2018: Pharo TechTalk https://association.pharo.org/event-2973754 15 Nov 2018: Pharo TechTalk https://association.pharo.org/event-2973755 13 Dec 2018: Pharo TechTalk https://association.pharo.org/event-2973756 We are looking for topics! â¢ If you have ideas for topics, please tell us! â¢ With no topic, we will use this slot for a general free discussion. â¢ If you want to do a TechTalk about a topic but no date is good, we can change the date! For recording of the past ones, see: http://pharo.org/TechTalk

June 19, 2018

Re: [Pharo-users] [Pharo-dev] [Ann] Iceberg v1.1.1

by Norbert Hartl

> Am 19.06.2018 um 15:22 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: > > > On Tue, Jun 19, 2018 at 2:07 PM Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: > Hi, > > let me wear the project manager hat for a moment. > > let me too, because the fact that I'm younger does not mean I don't know, right? :) > It has more to do with experience then with age. Well, the one thing enables sometimes the other but there is no strict causality, right. > >> Am 19.06.2018 um 10:59 schrieb Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>>: >> >> Hi, >> >> About why 1.1.1 and not 1.2.0. Itâs not about cheap or not, but about semantics :) > > for me âcaring about semanticsâ is just one of the top ten justifications developers use for the changes they did. > > Maybe, and putting the hat of project manager is usually a justification for somebody that is not good at technical stuff. > But I know that's not like it, so please let's not enter into this, I've felt a little insulted by this comment... > That is pretty clear by what you wrote. It wasnât meant to be personal so please donât take it like that. So do I. > >> We can agree that there is no hard rule on versionning, do we? But I try to follow the following guidelines (delta my own interpretation that adds some subjectivity :P) >> - Major Version will change when we break backwards compatibility >> - Minor Version will change when new features are added >> - Otherwise, patch version will change. >> > There is only one hard rule for me and that is knowing about the risk to take. > > That's a matter of conventions. We agree that version 1.1.x is compatible with 1.1.y. > > So if we take the patch version it should only include important bug fixes and nothing else. I would argue that only #864, #862, #858 and #854 qualify for such a patch if at all. > > So they are to my view. They should not introduce any compatibility issue. > And if they do, that's an error, but we are too few helping here, doing our best... > My mail was meant to be a plea for exactly this. If you donât think the hot-fix (I like that much more than patch) solves a show stopper for a lot of users of this version you donât put it in a patch version. If it is in the slightest sense an improvement donât put into a patch version but a minor on. Because I donât want to have my stuff broken but I choose to update in order to get the improvement hence a deliberate action. If all of these commits are hot-fixes then take my big excuse for bringing this up. > Not sure about #860 because the title is not specific enough. > > Please, I'll let you judge it for yourself > > https://github.com/pharo-vcs/iceberg/pull/860/files <https://github.com/pharo-vcs/iceberg/pull/860/files> > > But to me that change applies to patch. It actually fixes a compatibility issue that was introduced in 1.1.0. > > The point for me is that I want my project to rely on something like 1.1.x because I donât want anything to change that breaks my software. And I can tell you that most developers underestimate the side-effects of changes. > > I'm well aware of this. But do you have a concrete issue? > For what? > >> So I donât assign a new version number regarding the number of changes but about what they mean... > > To mean they mean it is a risk to use that version and you define how big that is. > > We are trying to do weekly releases, we could do better but again. I can count with my hand fingers people contributing with actual commits and issues in the issue tracker. > This time it is not about having more but less in a version. > >> Now, I considered myself this release as a patch because mostly little bugs here and there were fixed. >> Moreover, one of the changes done in the credentials manager was to *recover* some backwards compatibility for people setting up credentials in settings files. >> Of course, to this we add to this that my own interpretation saying that the changes do not break compatibility nor add features :) >> > You see you said âmostly bugsâ and that is the error already. > > I'm sorry for not being perfect... > > I mean we come from an amateurish behaviour that we change released artefacts. > > I assure you I do my best on it, and I'm one of the first that cries aloud when there are versionning and dependencies problems. > What I do not understand if this mail was meant as a lesson for the community or should I take it personally... > I know you do your best. And I know that you are a really good developer that does great stuff all the time. It is neither meant as a lesson nor something you should take personally. I do not often raise my wishes because I always need to assurance it is something really important and not something I want out of my current mood. But this is something I have no doubt about so I bring it up. And I do all of this for quite some time and that does count, too. > That is not discussable just a no-go. > > I know and I'm against it. So we agree, right? > Yes. > The reason was it would have wasted a huge amount of time to do a new version. So ok it was a loose-loose situation. Now we can do it better and I want something far less amateurish. So you can discuss your semantics about what major and minor versions in pharo mean but patch needs to be the definition of the combination: least risk - highest value. > > Would you help us measuring the risk? > Sure. > >> Now, this is the kind of subjective topic that starts a flamewar, but Iâd prefer to use my time on somewhat else ^^. > > You may not like to talk about these things but I do. And you should listen. > > I mostly do [enjoy such discussions] but what I learn from this discussion is: > - you think I'm stupid, or young, or both, so I don't know > - we are all amateurs > No, it is more like - you took it as a personal insult. That was not my intention and I apologize - well, we includes me. There are things that I have a pretty solid opinion about and that is what I want to raise. And I want to bring that into the community. It is also important work > I have no use for an environment where people only care about coding new cool stuff. > > I'm fu*** trying to make Iceberg as stable as possible, If I was just wanting to do new cool stuff I would not be doing this. > I know. Norbert

June 19, 2018

Re: [Pharo-users] [Pharo-dev] [Ann] Iceberg v1.1.1

by Tudor Girba

Hi, Indeed. Something went amiss in this email exchange. But, I really do not think that you are in disagreement. Cheers, Doru > On Jun 19, 2018, at 4:09 PM, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > > Hi Norbert, > >> Le 19 juin 2018 Ã 14:06, Norbert Hartl <norbert(a)hartl.name> a Ã©crit : >> >> I have no use for an environment where people only care about coding new cool stuff. If it would be like this I would quit all my pharo businesses, move to mainstream and would use pharo only for hobbyist projects because that would be the level that can be met. > > I do not think Guille has this state of mind. He spends time to write lot of tests for code other people wrote (not the funniest part), to clean code in the image (old code, bad dependencies, better API), to improve existing stuff, answering questions on the ML, and so on. > He is one of the few people that really tries to push semantic versioning. He could have made some errors (like everyone) but I find your sentence not fair for him. > > Regards, > Christophe -- www.tudorgirba.com www.feenk.com "We are all great at making mistakes."

June 19, 2018

Re: [Pharo-users] [Pharo-dev] [Ann] Iceberg v1.1.1

by Christophe Demarey

Hi Norbert, > Le 19 juin 2018 Ã 14:06, Norbert Hartl <norbert(a)hartl.name> a Ã©crit : > > I have no use for an environment where people only care about coding new cool stuff. If it would be like this I would quit all my pharo businesses, move to mainstream and would use pharo only for hobbyist projects because that would be the level that can be met. I do not think Guille has this state of mind. He spends time to write lot of tests for code other people wrote (not the funniest part), to clean code in the image (old code, bad dependencies, better API), to improve existing stuff, answering questions on the ML, and so on. He is one of the few people that really tries to push semantic versioning. He could have made some errors (like everyone) but I find your sentence not fair for him. Regards, Christophe

June 19, 2018

Re: [Pharo-users] [ANN] Pharo Launcher v1.2 release

by Tudor Girba

Great work! Doru > On Jun 19, 2018, at 3:55 PM, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > > Hi all, > > I just released PharoLauncher 1.2. It includes a new windows installer that you can use without administrator privileges as well as binary signing for OS X and Windows. Also, Pharo Launcher is not anymore identified as âPharoâ application and comes with its own icon. > > Here is the changelog (details on https://github.com/pharo-project/pharo-launcher/issues) > New features: > #21 Bless the DMG > #46 sign pharo launcher app for windows > #103 No way to rename a local template > #107 Unable to add a description for the image using the Launcher UI > #121 You can't see/sort images by last modified date > Improvements: > #69 Import command should also import pharo-local directory > #70 Import command should delete origin folder if empty > #73 Managers of Download of VMs and images should be in their own packages > #76 Use https instead of http to requests the pharo file server > #82 Official Distributions loads 32bit versions on 64bit System (i.e. provide better information on templates architecture) > #86 Sort Existing Images Case-Insensitive > #98 Copy and subfolders problem (contents no copied) > #101 Templates from a local image are listed in "downloaded". "local" would be a better name > #102 Template Cleared at Startup setting is enabled, making it weird when trying to use the template feature > #106 Import could work if we select the parent folder of an image > #109 Use latest pre-Spur VM to determine the image version > #122 The Run without settings icon looks like a funny grey/which blob (missing alpha correction) > Bux fixes: > #41 #selectedMorphList was sent to nil > #67 bash is not a command usable under windows > #68 Does not launch images on Windows > #85 Double click on an existing image open a file selector > #88 Pharo Launcher on Windows > Failing > #104 GUI bug makes Launcher unusable > #110 Image launch not reliable on Windows > #119 MessageNotUnderstood exception on launch > #123 The status bar of the Launcher is broken, so can't easily show image descriptions > > > Big thanks to all contributors: code, issues report, comments, advices. > > You can get platform bundles from pharo download page or files.pharo.org: http://files.pharo.org/pharo-launcher/1.2/ > > Regards, > Christophe. -- www.tudorgirba.com www.feenk.com "The coherence of a trip is given by the clearness of the goal."

June 19, 2018

Re: [Pharo-users] Project dependency management with Iceberg

by Guillermo Polito

Hi, On Tue, Jun 19, 2018 at 3:16 PM Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > Hello, > > How do I do project dependency management with Iceberg? > This is still Metacello. > I tried sometime ago but I was unable to understand how it work together > with Metacello, is there some tutorial available? > Well, there is a chapter in the Deep Into Pharo book http://files.pharo.org/books-pdfs/deep-into-pharo/2013-DeepIntoPharo-EN.pdf But that covers ConfigurationOf only. The technical part on how you define a dependency does not change too much between Configurations and Baselines. The main difference is that - a ConfigurationOf will store inside it several baselines (in baseline methods) and several versions (in version methods) - a BaselineOf defines a single baseline in a baseline method. And versions are declared in the VCS using whatever you like the most, most commonly being tags. Then, inside a BaselineOf, if you want to define a dependency to a project in github for example, you can specify it like this: spec baseline: 'Tonel' with: [ spec repository: 'github://pharo-vcs/tonel:v1.0.9/src' ] Where Tonel is the name of the project and the strangish url is then used to construct a github url. So it's something like [provider]://[owner-name]/[project-name][:version][/subdirectory] - provider can be (so far) any of github, bitbucket, gitorious - If version is ommited then it will just download the main branch (usually master) - Otherwise you can specify any commitish (commit hash, tag name, branch name) - If your source code is stored in a subdirectory of the repository, you can specify it after the version. Then, to load project you can either - use the Metacello plugin from Iceberg (right click -> Metacello -> Install baseline) - evaluate a Metacello expression in the playground Metacello new baseline: 'Tonel'; repository: 'github://pharo-vcs/tonel:v1.0.9/src' ; load Of course you can then just look for senders of #baseline:with: to see other examples in the image. Cheers, Guille

June 19, 2018