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

Re: [Pharo-dev] Fwd: [Pharo-users] "Oops! Invalid username or password" when saving Settings on smalltalkhub

by Merwan Ouddane

I already experienced the same issue but it only happened once, weird... On 03/07/2015 18:30, Damien Cassou wrote: > Damien Cassou <damien.cassou(a)inria.fr> writes: > >> I'm trying to update the description of the Pillar project at >> http://www.smalltalkhub.com/#!/~Pier/Pillar/settings. Unfortunately, >> when I press the green "Update" button, I face a >> >> Oops! Invalid username or password >> >> red warning on top of the page and my changes are not saved.

July 3, 2015

can you explain that?

by Nicolai Hess

you can save the image with the shortcut cmd+shift+s the shortcut action is: [ Smalltalk snapshot: true andQuit: false. UIManager default inform: 'Image saved' ] Save the image and show a notification. If you do this shortuct, the image is saved and you'll see the notification - ok. If you close the image, without saving again and open the image again, it starts with showing this notification again. How can this work? The notification was sent after the image was saved.

July 3, 2015

Re: [Pharo-dev] Can someone add me to the Pharo team

by Esteban Lorenzano

aberg? done :) > On 03 Jul 2015, at 18:27, Damien Cassou <Damien.Cassou(a)inria.fr> wrote: > > > Alexandre Bergel <alexandre.bergel(a)me.com> writes: > >> On Smalltalkhub? >> I would like to contribute to Bloc > > I tried but got "Invalid username or password" > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill

July 3, 2015

Fwd: [Pharo-users] "Oops! Invalid username or password" when saving Settings on smalltalkhub

by Damien Cassou

Damien Cassou <damien.cassou(a)inria.fr> writes: > I'm trying to update the description of the Pillar project at > http://www.smalltalkhub.com/#!/~Pier/Pillar/settings. Unfortunately, > when I press the green "Update" button, I face a > > Oops! Invalid username or password > > red warning on top of the page and my changes are not saved. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

July 3, 2015

Re: [Pharo-dev] Can someone add me to the Pharo team

by Damien Cassou

Alexandre Bergel <alexandre.bergel(a)me.com> writes: > On Smalltalkhub? > I would like to contribute to Bloc I tried but got "Invalid username or password" -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

July 3, 2015

Can someone add me to the Pharo team

by Alexandre Bergel

On Smalltalkhub? I would like to contribute to Bloc Please :-) Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 3, 2015

Re: [Pharo-dev] GToolkit loading problem

by Esteban Lorenzano

> 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 <mailto:pavel.krivanek@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 <mailto:chisvasileandrei@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 <mailto:pavel.krivanek@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/ <https://ci.inria.fr/pharo/view/5.0-SysConf/job/Pharo-5.0-ConfigurationOfIDE/> > > Cheers, > -- Pavel > > > >

July 3, 2015

Re: [Pharo-dev] GToolkit loading problem

by Andrei Chis

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. 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 3, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] 2787bd: 50151

by Marcus Denker

> On 03 Jul 2015, at 16:22, Torsten Bergmann <astares(a)gmx.de> wrote: > >> 15871 enable ProcessList >> https://pharo.fogbugz.com/f/cases/15871 >> >> http://files.pharo.org/image/50/50151.zip > > Hi Marcus, > > there must be a reason to switch from a LinkedList to a special > ProcessList class that is bound to VM - still the bug tracker and the class > comments do not tell much about the "whyâ. The reason is that the ProcessList is very special: some methods are carefully written to not have any intererrupt point, for example (not using messages sends). In the past we had serious side effects from people improving LinkedListâ¦ in the end to the point that nobody dares to change it anymore. Having two solved that: -> ProcessList will be minmal, unchanging, for the VM -> LinkedList will be a linked list for people to use and that we can improve and change. Marcus

July 3, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] 2787bd: 50151

by Torsten Bergmann

> 15871 enable ProcessList > https://pharo.fogbugz.com/f/cases/15871 > > http://files.pharo.org/image/50/50151.zip Hi Marcus, there must be a reason to switch from a LinkedList to a special ProcessList class that is bound to VM - still the bug tracker and the class comments do not tell much about the "why". Anyone able to ellaborate why this is necessary/what's the plan behind that? Thanks T.

July 3, 2015