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

[Issue tracker] reviewing help needed

by Marcus Denker

Hi, We continue to need more people that help reviewing and testing new submissions of both fixes and new featuresâ¦ https://pharo.fogbugz.com/f/filters/45/Review <https://pharo.fogbugz.com/f/filters/45/Review> - check if the fix fixed the bug - look a the code: does it look ok? - for new features: does it make sense? Marcus

July 9, 2015

Re: [Pharo-dev] GToolkit loading problem

by Andrei Chis

https://pharo.fogbugz.com/f/cases/15933/Wrong-metacelloPlatformAttributes-f… On Wed, Jul 8, 2015 at 11:54 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > you need to create one :P > > On 08 Jul 2015, at 11:47, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > Is there bug report for this or should I create one? > > cheers, > Andrei > > On Fri, Jul 3, 2015 at 4:58 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> >> On 03 Jul 2015, at 16:42, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: >> >> >> >> On Fri, Jul 3, 2015 at 3:37 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> >> wrote: >> >>> Hi, >>> >>> thank you, Andrei. >>> >>> SmalltalkImage>>#metacelloPlatformAttributes are defined currently as >>> (#squeakCommon #pharo #'pharo4.x' #'pharo4.0.x' #'pharo5.x' #'pharo5.0.x') >>> for Pharo 5 (from most to least general) so it will prefer 'pharo4.x' over >>> 'common'. >>> >> >> Ahaaa. >> Then I kind of misunderstood how platform attributes work. >> I need now to update some configurations from GTools. >> >> >> but this is an error. >> #metacelloPlatformAttributes for Pharo 5 should be: #(#squeakCommon >> #pharo #'pharo5.x' #'pharo5.0.xâ) >> >> then your configuration should be taking #common and not #pharo4.x >> >> cheers, >> Esteban >> >> >> >> Cheers, >> Andrei >> >> >>> >>> Cheers, >>> -- Pavel >>> >>> 2015-07-03 14:37 GMT+02:00 Andrei Chis <chisvasileandrei(a)gmail.com>: >>> >>>> Hi Pavel, >>>> >>>> I fixed the issue in the glamour repo and updated the configurations. >>>> >>>> Still I get the same error when trying to load ConfigurationOfGToolkit >>>> #stable into PharoIDE, as monticello >>>> seems to not resolve versions correctly. >>>> >>>> To reproduce first update all configurations: >>>> { { 'ConfigurationOfRubric'. 'Pharo'. 'Rubric' }. >>>> { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. >>>> { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. >>>> { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. >>>> { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. >>>> { 'ConfigurationOfGToolkitCore'. 'Moose'. 'GToolkit' }. >>>> } do: [ :spec | >>>> Gofer new >>>> smalltalkhubUser: spec second project: spec third; >>>> package: spec first; >>>> load ]. >>>> >>>> Then print: >>>> (ConfigurationOfGToolkitCore project version: #stable) record >>>> loadDirective >>>> >>>> ConfigurationOfGToolkitCore is resolved to version 3.0.2 even though it >>>> should be 3.0.4 >>>> Now ConfigurationOfGToolkitCore>>#stable is defined as >>>> >>>> ConfigurationOfGToolkitCore >>stable: spec >>>> <symbolicVersion: #'stable'> >>>> spec for: #'common' version: '3.0.4'. >>>> spec for: #'pharo4.x' version: '3.0.2'. >>>> >>>> If I add an entry for pharo5.x then it works. >>>> Through I think it should also work without one. >>>> >>>> Cheers, >>>> Andrei >>>> >>>> >>>> On Fri, Jul 3, 2015 at 1:09 PM, Pavel Krivanek < >>>> pavel.krivanek(a)gmail.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> I try to load GT tools to minimal Pharo image (with Morphic) and I >>>>> have problems to do that because it has a dependency cycle it these methods: >>>>> >>>>> GLMBrickDarkThemer>>#actionThemer >>>>> GLMBrickThemer>>#actionThemer >>>>> >>>>> These methods try to extend classes in Glamour-Morphic-Brick package >>>>> but they belong to Glamour-Core package that is prerequisite of the first >>>>> package. >>>>> >>>>> The image without GT tools for testing is hrere: >>>>> https://ci.inria.fr/pharo/view/5.0-SysConf/job/Pharo-5.0-ConfigurationOfIDE/ >>>>> >>>>> Cheers, >>>>> -- Pavel >>>>> >>>>> >>>> >>> >> >> > >

July 9, 2015

Re: [Pharo-dev] merging in a filetree repository

by Thierry Goubier

Alexandre, if you had the time, could you give me the output of readlink --help on your computer? Thanks, Thierry 2015-07-09 9:44 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > Ok, thanks! > > Alexandre > > > On Jul 8, 2015, at 11:39 PM, Thierry Goubier <thierry.goubier(a)gmail.com> > wrote: > > > > Le 08/07/2015 23:25, Alexandre Bergel a Ã©crit : > >> Thanks Thierry. Seems to work. But I get this error: > >> > >> ~/HackathonSattose2015> git merge master > >> readlink: illegal option -- e > >> usage: readlink [-n] [file ...] > >> readlink: illegal option -- e > >> usage: readlink [-n] [file ...] > >> readlink: illegal option -- e > >> usage: readlink [-n] [file â¦] > > > > Can you edit the merge file > (~/Dropbox/Workspace/GitFileTree-MergeDriver/merge) and change that line: > > > > DIR=`readlink -e "$0"` || DIR="$0"; > > > > to: > > > > DIR=`readlink "$0"` || DIR="$0"; > > > > (I would have expected this to work as well on a mac... but it isn't the > case :(:( The -e option is there to try to see through symlinks. I'll > correct that.) > > > > Thierry > > > >> > >> Any idea? > >> > >> Alexandre > >> > >> > >>> On Jul 8, 2015, at 3:31 PM, Thierry Goubier <thierry.goubier(a)gmail.com> > wrote: > >>> > >>> > >>> > >>> 2015-07-08 15:24 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > >>> Thierry, > >>> > >>>>> $ git config --get merge.mcVersion.driver > >>>> > >>>> ~/HackathonSattose2015> git config --get merge.mcVersion.driver > >>>> pathToGitFileTree-MergeDriver/merge --version %O %A %B > >>> > >>> Any idea how I can merge then? > >>> Is this value what you expected? > >>> > >>> No. > >>> > >>> If you have your path for the merge command (something like > >>> /User/Alexandre/GitFileTree-MergeDriver/merge ), then it should be: > >>> > >>> ~/HackathonSattose2015> git config --get merge.mcVersion.driver > >>> /User/Alexandre/GitFileTree-MergeDriver/merge --version %O %A %B > >>> > >>> To correct it, what you can do by hand is: > >>> > >>> git config --global merge.mcVersion.driver > "/User/Alexandre/GitFileTree-MergeDriver/merge --version %O %A %B" > >>> git config --global merge.mcMethodProperties.driver > "/User/Alexandre/GitFileTree-MergeDriver/merge --methodProperties %O %A %B" > >>> git config --global merge.mcProperties.driver > "/User/Alexandre/GitFileTree-MergeDriver/merge --properties %O %A %B" > >>> > >>> Don't forget to update the path ! > >>> > >>> Thierry > >>> > >>> > >>> Cheers, > >>> Alexandre > >>> -- > >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > >>> Alexandre Bergel http://www.bergel.eu > >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > >>> > >>> > >>> > >>> > >>> > >> > > > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

July 9, 2015

Re: [Pharo-dev] Debugging Spotter previews in Pharo 4

by Andrei Chis

https://pharo.fogbugz.com/f/cases/15932/Backport-15772-to-Pharo-4-spotter-i… On Thu, Jul 9, 2015 at 10:32 AM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > There is a better fix that also catches and logs Errors. > https://pharo.fogbugz.com/f/cases/15772/spotter-is-undebuggable > > I'll make an issue to back port it to pharo 4 > > Cheers, > Andrei > > On Thu, Jul 9, 2015 at 10:16 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > >> Just wanted to share in case someone has the same problem: >> >> In Pharo4.0 Latest update: #40617 when one puts a #halt into a >> <spotterPreview:> tagged method nothing happens. No debugger - nothing. >> Also no output on the Transcript. >> >> One can fix this easily in GTSpotterPreviewBrick>>updatePreviewWith: by >> replacing Exception with Error. >> >> Would be nice if this could be integrated as a backport in >> Pharo 4.0 somehow. >> >> Thx >> T. >> >> >

July 9, 2015

Re: [Pharo-dev] Debugging Spotter previews in Pharo 4

by Andrei Chis

There is a better fix that also catches and logs Errors. https://pharo.fogbugz.com/f/cases/15772/spotter-is-undebuggable I'll make an issue to back port it to pharo 4 Cheers, Andrei On Thu, Jul 9, 2015 at 10:16 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > Just wanted to share in case someone has the same problem: > > In Pharo4.0 Latest update: #40617 when one puts a #halt into a > <spotterPreview:> tagged method nothing happens. No debugger - nothing. > Also no output on the Transcript. > > One can fix this easily in GTSpotterPreviewBrick>>updatePreviewWith: by > replacing Exception with Error. > > Would be nice if this could be integrated as a backport in > Pharo 4.0 somehow. > > Thx > T. > >

July 9, 2015

Debugging Spotter previews in Pharo 4

by Torsten Bergmann

Just wanted to share in case someone has the same problem: In Pharo4.0 Latest update: #40617 when one puts a #halt into a <spotterPreview:> tagged method nothing happens. No debugger - nothing. Also no output on the Transcript. One can fix this easily in GTSpotterPreviewBrick>>updatePreviewWith: by replacing Exception with Error. Would be nice if this could be integrated as a backport in Pharo 4.0 somehow. Thx T.

July 9, 2015

[pharo-project/pharo-core]

by GitHub

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

July 9, 2015

[pharo-project/pharo-core] 20b048: 50162

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 20b048a48f156733c427506d50aa4cc20df2e57b https://github.com/pharo-project/pharo-core/commit/20b048a48f156733c427506d… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-07-09 (Thu, 09 Jul 2015) Changed paths: A Monticello.package/MCRepository.class/instance/error handling/error_.st M Nautilus.package/AbstractNautilusUI.class/instance/menus behavior/addClass.st M RPackage-Core.package/RPackageOrganizer.class/instance/accessing/packageNamed_ifAbsent_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50161.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50162.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50161.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50162.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Slot.package/BaseSlot.class/instance/comparing/=.st A Slot.package/BaseSlot.class/instance/comparing/hash.st A Slot.package/BaseSlot.class/instance/initalize/default.st A Slot.package/ExampleSlotWithDefaultValue.class/instance/accessing/default.st A Slot.package/ExampleSlotWithDefaultValue.class/instance/comparing/=.st A Slot.package/ExampleSlotWithDefaultValue.class/instance/comparing/hash.st Log Message: ----------- 50162 15912 Classes are not rebuilt when changing only slot parameters https://pharo.fogbugz.com/f/cases/15912 14310 Renaming a package just by changing upper/lowercase removes the package https://pharo.fogbugz.com/f/cases/14310 15926 Monticello should raise MCRepositoryError and not Error https://pharo.fogbugz.com/f/cases/15926 12190 Nautilus right click menus do not work on empty panes https://pharo.fogbugz.com/f/cases/12190 http://files.pharo.org/image/50/50162.zip

July 9, 2015

Re: [Pharo-dev] merging in a filetree repository

by Alexandre Bergel

Ok, thanks! Alexandre > On Jul 8, 2015, at 11:39 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Le 08/07/2015 23:25, Alexandre Bergel a Ã©crit : >> Thanks Thierry. Seems to work. But I get this error: >> >> ~/HackathonSattose2015> git merge master >> readlink: illegal option -- e >> usage: readlink [-n] [file ...] >> readlink: illegal option -- e >> usage: readlink [-n] [file ...] >> readlink: illegal option -- e >> usage: readlink [-n] [file â¦] > > Can you edit the merge file (~/Dropbox/Workspace/GitFileTree-MergeDriver/merge) and change that line: > > DIR=`readlink -e "$0"` || DIR="$0"; > > to: > > DIR=`readlink "$0"` || DIR="$0"; > > (I would have expected this to work as well on a mac... but it isn't the case :(:( The -e option is there to try to see through symlinks. I'll correct that.) > > Thierry > >> >> Any idea? >> >> Alexandre >> >> >>> On Jul 8, 2015, at 3:31 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: >>> >>> >>> >>> 2015-07-08 15:24 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>: >>> Thierry, >>> >>>>> $ git config --get merge.mcVersion.driver >>>> >>>> ~/HackathonSattose2015> git config --get merge.mcVersion.driver >>>> pathToGitFileTree-MergeDriver/merge --version %O %A %B >>> >>> Any idea how I can merge then? >>> Is this value what you expected? >>> >>> No. >>> >>> If you have your path for the merge command (something like >>> /User/Alexandre/GitFileTree-MergeDriver/merge ), then it should be: >>> >>> ~/HackathonSattose2015> git config --get merge.mcVersion.driver >>> /User/Alexandre/GitFileTree-MergeDriver/merge --version %O %A %B >>> >>> To correct it, what you can do by hand is: >>> >>> git config --global merge.mcVersion.driver "/User/Alexandre/GitFileTree-MergeDriver/merge --version %O %A %B" >>> git config --global merge.mcMethodProperties.driver "/User/Alexandre/GitFileTree-MergeDriver/merge --methodProperties %O %A %B" >>> git config --global merge.mcProperties.driver "/User/Alexandre/GitFileTree-MergeDriver/merge --properties %O %A %B" >>> >>> Don't forget to update the path ! >>> >>> Thierry >>> >>> >>> Cheers, >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 9, 2015

Re: [Pharo-dev] Rubic is getting more and more lowlevel

by stepharo

We will replace the PluggableTexMorph uses by Spec Normally this should be transparent to the user. PluggableTextMorph should get out. Stef Le 9/7/15 09:02, HernÃ¡n Morales Durand a Ã©crit : > Hi Stef, > > 2015-07-07 16:15 GMT-03:00 stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > Hi Pavel > > Rubric will replace the PluggableTextMorph and friends. So it is > at the same level. > > > This will impact Spec? > > HernÃ¡n >

July 9, 2015