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

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

by Martin Dias

Max, Esteban, Denis: Thanks! it worked: https://github.com/pharo- project/pharo/pull/690 I didn't have to add or remove packages as in step 5, but I did have to 'Synchronize full repository' as in step 6. Luke, this is offtopic, but here is a brief guide to use epicea after you lost changes: 1. reopen the image and select "Code Changes" from the world menu > tools. 2. click on left side items: they are change log files. 3. look at the logged changes on right side: the most recent ones are on top. 4. you can select a single or multiple changes, right click and "apply". Also there is a button "Filters" with options that can help you to remove from the view changes you don't want to see. BTW, the "apply" of multiple changes will work better after the PR is merged. MartÃn On Wed, Jan 17, 2018 at 8:20 AM, Luke Gorrie <luke(a)snabb.co> wrote: > Just one data point... > > I am completely overwhelmed by all of the different ways to manage source > code in the Pharo universe. I would love to contribute to upstream but this > seems way out of reach: I'm not even managing to keep track of the code in > my own home directory properly yet. > > Just now I am looking at upstream code that should be fixed: CairoLibrary > unix32ModuleName and unix64ModuleName are giving higher priority to guessed > hard-coded paths than to LD_LIBRARY_PATH and this is backwards i.e. the > carefully selected paths a user supplies with LD_LIBRARY_PATH should come > first (imho.) > > On the one hand it would be fine to dive into the upstream contribution > process to work out how to do this. On the other hand I am still trying to > master tools like Epica to recover useful code that I have written and lost > track of when images crash and get rebuilt etc. I really need to get this > under control before spending time learning Iceberg, FogBugz, etc. > > > > > On 14 December 2017 at 13:19, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> Hi! >> >> Iâm working on simplifying the contribution process, after collecting >> opinions/experiences last couple of months. >> As you know, Pharo contribution process is still WIP and we aim to have >> it as smooth as possible for Pharo 7.0 release. Now, after observe the idea >> of the âsystem repositoriesâ was a bad idea because it introduced extra and >> non standard âpathâ to contribution, I managed to remove that to >> reestablish âthe regular wayâ: you will now need to add pharo repository >> just as any other repository you add, by cloning or adding local repository. >> >> I took Guilleâs doc and moved it to pharo project (it does not has sense >> to have it living in a contributorâs repository when is so important). You >> can find it here: >> >> https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo >> >> This document is also updated to reveal this new process, please read it. >> >> How to update your startup scripts? >> Some people has added startup scripts to easy the first part of >> contribution. Instead enabling system repositories, etc. you now need to >> replace that with this: >> >> (IceRepositoryCreator new >> location: '/path/to/pharo-project/pharo' asFileReference; >> subdirectory: 'src'; >> createRepository) >> register >> >> PLEASE, PLEASE, PLEASEâ¦ take a moment to read and try the document. Is >> very important that document reflects new process and works reliable in >> different scenarios (I validated it on macOS and Windows, and assumed it >> worked fine on linux but you knowâ¦ bad assumptions is the base of failure >> ;) ) >> >> Iâm eager to hear your feedback and continue enhancing the process. >> >> (yes, Stef, I know UI is still cumbersomeâ¦ Iâm working on that :) ) >> >> cheers! >> Esteban >> > >

Jan. 18, 2018

Re: [Pharo-dev] [ANN] Dates Pharo Sprints 2018 till June

by Peter UhnÃ¡k

No worries, it's a "nice to have". :) Peter On Wed, Jan 17, 2018 at 5:44 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > I will seeâ¦ the problem is that this is then yet another thing to maintain. > > On 13 Jan 2018, at 10:32, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Hi, > > is it possible to add the events as a google calendar so it updates > automatically? > > Thanks, > Peter > > On Fri, Jan 12, 2018 at 2:37 PM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > >> Hi, >> >> For Pharo sprints for the next months, we suggest these dates: >> >> Jan 26 >> Feb 23 >> Mar 30 >> Apr 20 >> Mai 25 >> Jun 29 >> >> >> I have added the first one already to the events page: >> https://association.pharo.org/events >> >> the others will be added later. >> Marcus >> > > >

Jan. 17, 2018

Re: [Pharo-dev] [ANN] Dates Pharo Sprints 2018 till June

by Marcus Denker

I will seeâ¦ the problem is that this is then yet another thing to maintain. > On 13 Jan 2018, at 10:32, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Hi, > > is it possible to add the events as a google calendar so it updates automatically? > > Thanks, > Peter > > On Fri, Jan 12, 2018 at 2:37 PM, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: > Hi, > > For Pharo sprints for the next months, we suggest these dates: > > Jan 26 > Feb 23 > Mar 30 > Apr 20 > Mai 25 > Jun 29 > > > I have added the first one already to the events page: > > https://association.pharo.org/events <https://association.pharo.org/events> > > the others will be added later. > > Marcus >

Jan. 17, 2018

[ANN] Updating Consultants Listing

by Marcus Denker

Hi, We have http://consultants.pharo.org <http://consultants.pharo.org/> I want to change it to - not be a forward to files.pharo.org <http://files.pharo.org/> - be auto-generated from the https://association.pharo.org <https://association.pharo.org/> But we should update it already before that is finished. So: If you want to be listed, please send your infos in the form: PharoConsultant { #name : Your name', #email : your(a)email.com', #website : 'http://your-website.com', #id : 'yourname (currently not used for anything)', #location : 'City, Country of your business', #languages : 'what languages do you speak', #industryExperienceSince : 1994, #pharoExperienceSince : 2008, #areasOfExpertise : 'what are your areas of expertise. E.g. business apllications, user interface, legacy, ...', #smalltalkExperienceSince : 2002 } (or open a pull request at: https://github.com/pharo-project/pharo-project-consultants/ <https://github.com/pharo-project/pharo-project-consultants/>) Marcus

Jan. 17, 2018

[Pharo 7.0-dev] Build #435: 20972-ShiftClassInstaller-do-not-announce-ClassModificationApplied-event

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

There is a new Pharo build available! The status of the build #435 was: SUCCESS. The Pull Request #684 was integrated: "20972-ShiftClassInstaller-do-not-announce-ClassModificationApplied-event" Pull request url: https://github.com/pharo-project/pharo/pull/684 Issue Url: https://pharo.fogbugz.com/f/cases/20972 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 17, 2018

Re: [Pharo-dev] [ANN] OpenSmalltalk VM Meeting

by Fabio Niephaus

Hi all, Just a quick reminder that the meeting starts in about 15mins. The agenda and a link to a public hangout is in the Google doc at [1]. See you in a few minutes! Fabio [1] https://docs.google.com/document/d/1nu3JLDvxJqKbDv1DsQoREtXPJNnqB-adB5zC-Uh… -- On Tue, Jan 16, 2018 at 1:01 AM Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi Fabio, > > On Mon, Jan 15, 2018 at 1:27 PM, Fabio Niephaus <lists(a)fniephaus.com> > wrote: > >> Dear all, >> >> The OpenSmalltalk VM Meeting will be held *this Wednesday, 17th January, >> 5pm - 6pm CET*. Click [1] for a quick timezone conversion. >> Please find the link to a public Google Hangout in the Google Doc at [2]. >> The document also includes a preliminary agenda, feel free to leave any >> comments. >> > > Since voting for this slot (amongst others) I've been given a post-op > checkup appointment by my eye surgeon. I'll try and change it tomorrow but > if I'm unable to then I won't be able to attend for more than about 40 > minutes. I do apologise. > > >> See you on Wednesday! >> >> Fabio >> >> [1] >> http://www.thetimezoneconverter.com/?t=5pm&tz=CET%20(Central%20European%20T… >> ) >> [2] >> https://docs.google.com/document/d/1nu3JLDvxJqKbDv1DsQoREtXPJNnqB-adB5zC-Uh… >> > > > > -- > _,,,^..^,,,_ > best, Eliot >

Jan. 17, 2018

[Pharo 7.0-dev] Build #434: 20979-Introducing-DoubleWord-and-DoubleByte-arrays

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

There is a new Pharo build available! The status of the build #434 was: SUCCESS. The Pull Request #689 was integrated: "20979-Introducing-DoubleWord-and-DoubleByte-arrays" Pull request url: https://github.com/pharo-project/pharo/pull/689 Issue Url: https://pharo.fogbugz.com/f/cases/20979 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 17, 2018

[Pharo 7.0-dev] Build #433: 20978-PharoIssueTest-should-be-long-time-test

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

There is a new Pharo build available! The status of the build #433 was: SUCCESS. The Pull Request #687 was integrated: "20978-PharoIssueTest-should-be-long-time-test" Pull request url: https://github.com/pharo-project/pharo/pull/687 Issue Url: https://pharo.fogbugz.com/f/cases/20978 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 17, 2018

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

by Luke Gorrie

Just one data point... I am completely overwhelmed by all of the different ways to manage source code in the Pharo universe. I would love to contribute to upstream but this seems way out of reach: I'm not even managing to keep track of the code in my own home directory properly yet. Just now I am looking at upstream code that should be fixed: CairoLibrary unix32ModuleName and unix64ModuleName are giving higher priority to guessed hard-coded paths than to LD_LIBRARY_PATH and this is backwards i.e. the carefully selected paths a user supplies with LD_LIBRARY_PATH should come first (imho.) On the one hand it would be fine to dive into the upstream contribution process to work out how to do this. On the other hand I am still trying to master tools like Epica to recover useful code that I have written and lost track of when images crash and get rebuilt etc. I really need to get this under control before spending time learning Iceberg, FogBugz, etc. On 14 December 2017 at 13:19, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi! > > Iâm working on simplifying the contribution process, after collecting > opinions/experiences last couple of months. > As you know, Pharo contribution process is still WIP and we aim to have it > as smooth as possible for Pharo 7.0 release. Now, after observe the idea of > the âsystem repositoriesâ was a bad idea because it introduced extra and > non standard âpathâ to contribution, I managed to remove that to > reestablish âthe regular wayâ: you will now need to add pharo repository > just as any other repository you add, by cloning or adding local repository. > > I took Guilleâs doc and moved it to pharo project (it does not has sense > to have it living in a contributorâs repository when is so important). You > can find it here: > > https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo > > This document is also updated to reveal this new process, please read it. > > How to update your startup scripts? > Some people has added startup scripts to easy the first part of > contribution. Instead enabling system repositories, etc. you now need to > replace that with this: > > (IceRepositoryCreator new > location: '/path/to/pharo-project/pharo' asFileReference; > subdirectory: 'src'; > createRepository) > register > > PLEASE, PLEASE, PLEASEâ¦ take a moment to read and try the document. Is > very important that document reflects new process and works reliable in > different scenarios (I validated it on macOS and Windows, and assumed it > worked fine on linux but you knowâ¦ bad assumptions is the base of failure > ;) ) > > Iâm eager to hear your feedback and continue enhancing the process. > > (yes, Stef, I know UI is still cumbersomeâ¦ Iâm working on that :) ) > > cheers! > Esteban >

Jan. 17, 2018

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

by Esteban Lorenzano

Hi, > On 17 Jan 2018, at 11:45, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi > > 2018-01-17 7:15 GMT+01:00 Max Leske <maxleske(a)gmail.com <mailto:maxleske@gmail.com>>: > Hi Martin, > > What I do is > 1. update local pharo repository on branch 'development' > 2. add repository to Iceberg > 3. create branch for phogbugz issue > 4. make changes (e.g. load stuff from your project) > 5. Note that you will have to handle addition and removal of packages separately: > 5.1 addition: click 'add package' > 5.2 removal: click 'remove package'. You will have to commit the removal from the command line, as Iceberg does not currently recognize removals as staged changes. > I usually just make a second commit with the removal before I push everything. > 6. Now the changes may not show up. But you can right click on the repository in Iceberg and select 'Synchronize full repository' > 7. Select the changes you want to commit > > I think the 4-th step is the question. > Epicea in image is managed by Iceberg and hosted in github. How to load new version from external monticello repo? Also there is no ConfigurationOfEpicea in the image. Epicea is also integrated on Pharo, and as Fuel or GT, they are managed outside. So, what you do is: - load new version of Epicea (that will be apply the changes) using a regular baseline or configuration of package by package, from Martinâs repository. - you add and remove new/removed packages AND you modify BaselineOfIDE (or the one where Epicea is declared) than you are ok to use âSync full changesâ as Max said. cheers, Esteban > > > The rest you know, I guess ;) > > Cheers, > Max > > > > On 16 January 2018 at 20:16:22, Martin Dias (tinchodias(a)gmail.com <mailto:tinchodias@gmail.com>) wrote: > >> Hi, I followed the guide and everything is good. What I don't know is how to upgrade an external project already integrated in Pharo 7 (Epicea). I have new version 8.2.6. >> >> Cheers, MartÃn. >> >> On Tue, Jan 9, 2018 at 11:01 AM, Sean P. DeNigris <sean(a)clipperadams.com <mailto:sean@clipperadams.com>> wrote: >> EstebanLM wrote >> >> Mmm. I think this is because your local clone is outdated. >> >> It should be fixed with a fetchâ¦ from pharo-project, I mean :) >> >> That worked. Thanks. Next problem: Iceberg is showing a massive number of >> changes when syncing with pharo fork on the dev branch at the same commit as >> the image. There doesn't seem to be a way to collapse the whole tree making >> it impossible to find the real changes. I assume it's that known bug where >> the first commit will sync the list, but not very user friendly! >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html> >> >> >

Jan. 17, 2018