July 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] Iceberg 0.5.1 with Pull Request review tool

by Pavel Krivanek

There seems to be an issue in the baseline with circular dependencies. Load it, skip all warnings and then try to reload all packages in the Iceberg repository (from the Iceberg window). -- Pavel 2017-07-06 16:53 GMT+02:00 Norbert Hartl <norbert(a)hartl.name>: > Am I the only one or are there some classes missing? > > Norbert > > Am 06.07.2017 um 15:35 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > Hi, > > I just released Iceberg version 0.5.1 with a Pull Request tool Guille and > I worked on since yesterday. > It allows you to list open Pull Requests (by right click on a repo, > GitHub/Review pull requestsâ¦ option): > > <Screen Shot 2017-07-06 at 14.59.32.png> > > And then if you doubleclick on one (or select it with right button), you > will see this: > > > <Screen Shot 2017-07-06 at 15.00.56.png> > it allows you to see changes and > > - merge changes into your image (in case you want to see more in details > the code, run tests, etc.) > - accept a pull request > - reject a pull request > > no, it does not shows (at least *yet*) comments, and it does not allows > you to add comments, reviews, etc. > this could be done, but not time to implement it now, so for now this has > to be enough. > > Again, this can be loaded in a 6.0 image by executing this script: > > #('Iceberg-UI' 'Iceberg-Plugin' 'Iceberg-Metacello-Integration' > 'Iceberg-Libgit' 'Iceberg' 'BaselineOfIceberg' 'LibGit-Core' > 'BaselineOfLibGit') do: [ :each | each asPackage removeFromSystem ]. > > Metacello new > baseline: 'Iceberg'; > repository: 'github://pharo-vcs/iceberg:v0.5.1'; > load. > > (and you still need to have the vm that is meant for Pharo7) > > This tools are open for you to use on your projectsâ¦ and to improve them, > I accept pull requests on pharo-vcs/iceberg. > > cheers! > Esteban > > > >

July 6, 2017

Re: [Pharo-dev] [ANN] Iceberg 0.5.1 with Pull Request review tool

by Norbert Hartl

Am I the only one or are there some classes missing? Norbert > Am 06.07.2017 um 15:35 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > Hi, > > I just released Iceberg version 0.5.1 with a Pull Request tool Guille and I worked on since yesterday. > It allows you to list open Pull Requests (by right click on a repo, GitHub/Review pull requestsâ¦ option): > > <Screen Shot 2017-07-06 at 14.59.32.png> > > And then if you doubleclick on one (or select it with right button), you will see this: > > > <Screen Shot 2017-07-06 at 15.00.56.png> > it allows you to see changes and > > - merge changes into your image (in case you want to see more in details the code, run tests, etc.) > - accept a pull request > - reject a pull request > > no, it does not shows (at least *yet*) comments, and it does not allows you to add comments, reviews, etc. > this could be done, but not time to implement it now, so for now this has to be enough. > > Again, this can be loaded in a 6.0 image by executing this script: > > #('Iceberg-UI' 'Iceberg-Plugin' 'Iceberg-Metacello-Integration' 'Iceberg-Libgit' 'Iceberg' 'BaselineOfIceberg' 'LibGit-Core' 'BaselineOfLibGit') do: [ :each | each asPackage removeFromSystem ]. > > Metacello new > baseline: 'Iceberg'; > repository: 'github://pharo-vcs/iceberg:v0.5.1 <github://pharo-vcs/iceberg:v0.5.1>'; > load. > > (and you still need to have the vm that is meant for Pharo7) > > This tools are open for you to use on your projectsâ¦ and to improve them, I accept pull requests on pharo-vcs/iceberg. > > cheers! > Esteban > >

July 6, 2017

Re: [Pharo-dev] [ANN] Iceberg 0.5.1 with Pull Request review tool

by Stephane Ducasse

this is quite cool :) On Thu, Jul 6, 2017 at 3:35 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > I just released Iceberg version 0.5.1 with a Pull Request tool Guille and > I worked on since yesterday. > It allows you to list open Pull Requests (by right click on a repo, > GitHub/Review pull requestsâ¦ option): > > > And then if you doubleclick on one (or select it with right button), you > will see this: > > > it allows you to see changes and > > - merge changes into your image (in case you want to see more in details > the code, run tests, etc.) > - accept a pull request > - reject a pull request > > no, it does not shows (at least *yet*) comments, and it does not allows > you to add comments, reviews, etc. > this could be done, but not time to implement it now, so for now this has > to be enough. > > Again, this can be loaded in a 6.0 image by executing this script: > > #('Iceberg-UI' 'Iceberg-Plugin' 'Iceberg-Metacello-Integration' > 'Iceberg-Libgit' 'Iceberg' 'BaselineOfIceberg' 'LibGit-Core' > 'BaselineOfLibGit') do: [ :each | each asPackage removeFromSystem ]. > > Metacello new > baseline: 'Iceberg'; > repository: 'github://pharo-vcs/iceberg:v0.5.1'; > load. > > (and you still need to have the vm that is meant for Pharo7) > > This tools are open for you to use on your projectsâ¦ and to improve them, > I accept pull requests on pharo-vcs/iceberg. > > cheers! > Esteban > > >

July 6, 2017

[ANN] Iceberg 0.5.1 with Pull Request review tool

by Esteban Lorenzano

Hi, I just released Iceberg version 0.5.1 with a Pull Request tool Guille and I worked on since yesterday. It allows you to list open Pull Requests (by right click on a repo, GitHub/Review pull requestsâ¦ option): And then if you doubleclick on one (or select it with right button), you will see this: it allows you to see changes and - merge changes into your image (in case you want to see more in details the code, run tests, etc.) - accept a pull request - reject a pull request no, it does not shows (at least *yet*) comments, and it does not allows you to add comments, reviews, etc. this could be done, but not time to implement it now, so for now this has to be enough. Again, this can be loaded in a 6.0 image by executing this script: #('Iceberg-UI' 'Iceberg-Plugin' 'Iceberg-Metacello-Integration' 'Iceberg-Libgit' 'Iceberg' 'BaselineOfIceberg' 'LibGit-Core' 'BaselineOfLibGit') do: [ :each | each asPackage removeFromSystem ]. Metacello new baseline: 'Iceberg'; repository: 'github://pharo-vcs/iceberg:v0.5.1'; load. (and you still need to have the vm that is meant for Pharo7) This tools are open for you to use on your projectsâ¦ and to improve them, I accept pull requests on pharo-vcs/iceberg. cheers! Esteban

July 6, 2017

Re: [Pharo-dev] Epicea feedback

by Martin Dias

Thanks I still didn't invest time to fix them but I registered both in fogbugz as: https://pharo.fogbugz.com/f/cases/20223/Epicea-check-usability-bug-to-apply… https://pharo.fogbugz.com/f/cases/20225/Epicea-would-be-nice-is-to-have-som… cheers, Martin On Sat, Jul 1, 2017 at 5:24 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Thanks martin for your excellent support. > What would be nice is to have some menus on the sessions items > because often I try to click on them so see what I can do with them. > > Stef > > On Tue, Jun 27, 2017 at 4:17 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > > Hello Jan, thanks for your feedback. I will have a look asap. Feel free > to > > report it in fogbugz. > > > > MartÃn > > > > On Tue, Jun 27, 2017 at 8:26 AM, Jan BlizniÄenko <bliznjan(a)fit.cvut.cz> > > wrote: > >> > >> Hello > >> > >> I'd like to thank you for creating the Epicea. It is way more > >> user-friendly > >> and dependable than previous change-handling tool. Browsing, applying > and > >> reverting changes is way easier. > >> > >> Just one note: > >> It is not exactly clear from first look how to properly reapply changes > >> after an image has been closed without saving. If I select all changes I > >> want to apply without using any filter, those changes are reapplied in > >> wrong > >> order (if I changed a method two times, first the new version is applied > >> and > >> then the old one). As far as I understood, I have to use filter to show > >> only > >> latest changes, but I think it could be clearer in the UI that I need to > >> do > >> so (or something completely different?) for applying changes. > >> > >> Thank you > >> Jan > >> > >> > >> > >> -- > >> View this message in context: > >> http://forum.world.st/Epicea-feedback-tp4952661.html > >> Sent from the Pharo Smalltalk Developers mailing list archive at > >> Nabble.com. > >> > > > >

July 6, 2017

Re: [Pharo-dev] Epicea and #name in #behaviorAffectedName

by Martin Dias

Hi Torsten, just copied your report into here: https://pharo.fogbugz.com/f/cases/20222/Epicea-deprecation-warning-dialog-p… I'll see it ASAP. Thanks and sorry for my delay. MartÃn El 19/5/2017 17:45, "Torsten Bergmann" <astares(a)gmx.de> escribiÃ³: > Hi, > > in latest Pharo 6 image 60494 I run into some trouble today where the > deprecation warning dialog popped up and repeated itself unstoppable > due to Epicea. > > It is hard to reproduce but what I found out was that I had a class > modification (represented by EpClassModification) which run into a state > where "newClass" was nil and therefore in EpClassModification>>#behavior > AffectedName > the message #name was sent to nil. > > So #name was found in Object and as we all know we deprecated it now > which lead to the deprecation dialog, leading to the deprecation dialog, > leading to the deprecation dialog, ... > > Nearly all implementors of Epiceas #behaviorAffectedName send #name > which is ok if there is a valid object it is sent to. > > I do not know if we should protect them somehow in case something > goes wrong (like having nil in newClass) or if we should keep this > untouched. > > At least I wanted to inform because I do not know if this later > gets others into trouble too and losing their changes because Epicea > does not record. > > Thanks > T. > >

July 6, 2017

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60507 Home: https://github.com/pharo-project/pharo-core

July 6, 2017

[pharo-project/pharo-core] 9b87bb: 60507

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 9b87bb71fd929f5f2af417887b3598f79784ae60 https://github.com/pharo-project/pharo-core/commit/9b87bb71fd929f5f2af41788… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-07-06 (Thu, 06 Jul 2017) Changed paths: M Jobs.package/Job.class/class/examples/exampleCurrentValue.st M Kernel.package/Context.class/class/simulation/runSimulated_.st M Monticello.package/MCMcdReader.class/instance/loading/loadPatch.st M Monticello.package/MCMczReader.class/instance/loading/loadDefinitions.st M Monticello.package/MCPatch.class/instance/intializing/initializeWithBase_target_.st M Monticello.package/MCVersion.class/instance/enumerating/withAllDependenciesDo_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60506.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60507.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60506.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60507.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Text-Core.package/Text.class/class/initialization/initialize.st M Traits.package/TBehaviorCategorization.class/instance/organization/category.st M UnifiedFFI.package/FFISizeT.class/class/converting/asExternalTypeOn_.st Log Message: ----------- 60507 20218 Master branch (Pharo 6) needs to be safely merged into development branch (Pharo 7). https://pharo.fogbugz.com/f/cases/20218 http://files.pharo.org/image/60/60507.zip

July 6, 2017

Re: [Pharo-dev] OSPlatform currentVersion

by Norbert Hartl

Ok, it works in the 7.0 vm. I opened the ticket again in order that we do not forget the fix for 6.1 https://pharo.fogbugz.com/f/cases/20156/OSPlatform-current-returns-a-MacOSP… <https://pharo.fogbugz.com/f/cases/20156/OSPlatform-current-returns-a-MacOSP…> Norbert > Am 06.07.2017 um 14:29 schrieb Norbert Hartl <norbert(a)hartl.name>: > > Ok, then it is a regression because I downloaded vm and image freshly before trying > > thanks, > > Norbert > >> Am 06.07.2017 um 14:15 schrieb Alistair Grant <akgrant0710(a)gmail.com>: >> >> Hi Norbet, >> >> Take a look at: >> >> http://forum.world.st/Working-OSProcess-configuration-for-Pharo-6-release-p… >> >> HTH, >> Alistair >> >> >> On 6 July 2017 at 14:06, Norbert Hartl <norbert(a)hartl.name> wrote: >>> Does anyone know when the output for >>> >>> OSPlatform currentVersion >>> >>> changed? In Pharo 4 I get >>> >>> '1095' >>> >>> and in pharo6 I get >>> >>> '10.12.5'. >>> >>> The determination if it is a OSX system or older is done by >>> >>> currentVersion asNumber >= 1000 >>> >>> which changes behaviour because the currentVersion string has been changed. >>> Is the output the one supposed to be? >>> >>> Norbert >>> >>>

July 6, 2017

Re: [Pharo-dev] OSPlatform currentVersion

by Norbert Hartl

Ok, then it is a regression because I downloaded vm and image freshly before trying thanks, Norbert > Am 06.07.2017 um 14:15 schrieb Alistair Grant <akgrant0710(a)gmail.com>: > > Hi Norbet, > > Take a look at: > > http://forum.world.st/Working-OSProcess-configuration-for-Pharo-6-release-p… > > HTH, > Alistair > > > On 6 July 2017 at 14:06, Norbert Hartl <norbert(a)hartl.name> wrote: >> Does anyone know when the output for >> >> OSPlatform currentVersion >> >> changed? In Pharo 4 I get >> >> '1095' >> >> and in pharo6 I get >> >> '10.12.5'. >> >> The determination if it is a OSX system or older is done by >> >> currentVersion asNumber >= 1000 >> >> which changes behaviour because the currentVersion string has been changed. >> Is the output the one supposed to be? >> >> Norbert >> >>

July 6, 2017