March 2016 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [Pillar] Logo for Pillar

by Esteban A. Maringolo

I don't like it. It's more an illustration than an actual iso/logotype. Sorry. I didn't know there was a logo for Pillar, and though it's not fantastic, it is nice and continues with the style of a Pharo thing. Regards! Esteban A. Maringolo 2016-03-21 11:05 GMT-03:00 Thibault ARLOING <thibault.arloing(a)hotmail.fr>: > oh I didn't see either that pillar had a logo. > Moreover, he is better. > > thanks > > ________________________________________ > De : Pharo-users <pharo-users-bounces(a)lists.pharo.org> de la part de Damien Cassou <damien.cassou(a)inria.fr> > EnvoyÃ© : lundi 21 mars 2016 14:19 > Ã : Yuriy Tymchuk; Any question about pharo is welcome > Objet : Re: [Pharo-users] [Pillar] Logo for Pillar > > Yuriy Tymchuk <yuriy.tymchuk(a)me.com> writes: > >> IMHO itâs too airy, to much free area. By the way, have you seen the previous logo? >> https://github.com/pillar-markup > > I didn't know Pillar already had a logo :-). Thanks > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill > >

March 21, 2016

BaselineOf's and Loose Dependencies

by Sean P. DeNigris

I know this is not technically a Pharo question, but I'm in China on my honeymoon and can't access the Metacello Google group! There was a pattern in pre-BaselineOf Metacello where one would define dependencies loosely in the #baselineXyz:, and then pin them to a specific version in the #versionAbc:. For example: baseline100: spec ... project: 'BabyMock' with: [ spec className: #ConfigurationOfBabyMock; versionString: #'stable'; repository: 'http://smalltalkhub.com/mc/zeroflag/BabyMock/main/' ] ... and then: version10: spec ... spec project: 'BabyMock' with: '1.2' ... How does one handle this sort of thing with #baseline:import:? This is what I came up with: version10: spec ... baseline: 'BabyPhexample' with: [ spec repository: 'github://seandenigris/Baby-Phexample:INSERT-SHA-HERE/repository' ]; import: 'BabyPhexample'. spec project: 'BabyMock' with: '1.2' ... But I got this error from the last line: MessageNotUnderstood: receiver of "fetchUsing:" is nil Thanks. ----- Cheers, Sean -- View this message in context: http://forum.world.st/BaselineOf-s-and-Loose-Dependencies-tp4885749.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 21, 2016

Re: [Pharo-users] [Pharo-dev] DeprecationAssistant

by Yuriy Tymchuk

Oh, thatâs an interesting use case. Itâs not easy no make predictions further in stack so by default it is assumed that the change should happen in the method that has called the deprecated one. In fact usually this should help with the method deprecation, and in the particular case we are dealing with a class deprecation hacked as a method deprecation :) But itâs good that now I know more use cases ;) Uko > On 21 Mar 2016, at 14:56, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Ah okay! > But how does the system resolve it ? I mean, the class RTLabelled does not refer to RTLabeled. So, what is the magic behind your tool? > > I found an interesting situation. Look at this: > > <Screen Shot 2016-03-21 at 10.53.09 AM.png> > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On Mar 21, 2016, at 10:19 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote: >> >> Hi Alex, >> >> this is not about criticsâ¦ >> >> If you have a method like >> >> labeledObject >> ^ RTLabelled new >> >> in the latest roassal image and you will execute it, you will get a debugger deprecation warning with an option to fix that. >> >> Cheers. >> Uko >> >>> On 21 Mar 2016, at 14:07, Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >>> >>> Hi! >>> >>> I cannot figure out what I should expect after loading DeprecationAssistant. I have loaded it and created a method: >>> -=-=-=-=-=-=-=-=-= >>> foo >>> self deprecated: 'use bar insteadâ >>> -=-=-=-=-=-=-=-=-= >>> >>> Is there anything that should be displayed in the critic list? >>> >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>>> On Mar 21, 2016, at 9:59 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote: >>>> >>>> HI everyone, >>>> >>>> last week Iâve created a little tool that automates deprecation resolution. The goal is to provide a help based on the existing code (no need for extra actions). You can read more here: http://blog.yuriy.tymch.uk/2016/03/deprecationassistant-aiding-developers.h… <http://blog.yuriy.tymch.uk/2016/03/deprecationassistant-aiding-developers.h…> >>>> >>>> You can install and try it out with: >>>> Metacello new >>>> repository: 'github://Uko/DeprecationAssistant' <github://Uko/DeprecationAssistant'>; >>>> baseline: 'DeprecationAssistant'; >>>> load >>>> >>>> This will add additional actions to the debugger once you will get a deprecation warning. >>>> >>>> Have fun! >>>> Cheers. >>>> Uko >>> >> >

March 21, 2016

Re: [Pharo-users] [Pillar] Logo for Pillar

by Thibault ARLOING

oh I didn't see either that pillar had a logo. Moreover, he is better. thanks ________________________________________ De : Pharo-users <pharo-users-bounces(a)lists.pharo.org> de la part de Damien Cassou <damien.cassou(a)inria.fr> EnvoyÃ© : lundi 21 mars 2016 14:19 Ã : Yuriy Tymchuk; Any question about pharo is welcome Objet : Re: [Pharo-users] [Pillar] Logo for Pillar Yuriy Tymchuk <yuriy.tymchuk(a)me.com> writes: > IMHO itâs too airy, to much free area. By the way, have you seen the previous logo? > https://github.com/pillar-markup I didn't know Pillar already had a logo :-). Thanks -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

March 21, 2016

Re: [Pharo-users] [Pharo-dev] DeprecationAssistant

by Alexandre Bergel

Ah okay! But how does the system resolve it ? I mean, the class RTLabelled does not refer to RTLabeled. So, what is the magic behind your tool? I found an interesting situation. Look at this: Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Mar 21, 2016, at 10:19 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Hi Alex, > > this is not about criticsâ¦ > > If you have a method like > > labeledObject > ^ RTLabelled new > > in the latest roassal image and you will execute it, you will get a debugger deprecation warning with an option to fix that. > > Cheers. > Uko > >> On 21 Mar 2016, at 14:07, Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >> >> Hi! >> >> I cannot figure out what I should expect after loading DeprecationAssistant. I have loaded it and created a method: >> -=-=-=-=-=-=-=-=-= >> foo >> self deprecated: 'use bar insteadâ >> -=-=-=-=-=-=-=-=-= >> >> Is there anything that should be displayed in the critic list? >> >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >>> On Mar 21, 2016, at 9:59 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote: >>> >>> HI everyone, >>> >>> last week Iâve created a little tool that automates deprecation resolution. The goal is to provide a help based on the existing code (no need for extra actions). You can read more here: http://blog.yuriy.tymch.uk/2016/03/deprecationassistant-aiding-developers.h… <http://blog.yuriy.tymch.uk/2016/03/deprecationassistant-aiding-developers.h…> >>> >>> You can install and try it out with: >>> Metacello new >>> repository: 'github://Uko/DeprecationAssistant' <github://Uko/DeprecationAssistant'>; >>> baseline: 'DeprecationAssistant'; >>> load >>> >>> This will add additional actions to the debugger once you will get a deprecation warning. >>> >>> Have fun! >>> Cheers. >>> Uko >> >

March 21, 2016

Re: [Pharo-users] [Pillar] Logo for Pillar

by Damien Cassou

Yuriy Tymchuk <yuriy.tymchuk(a)me.com> writes: > IMHO itâs too airy, to much free area. By the way, have you seen the previous logo? > https://github.com/pillar-markup I didn't know Pillar already had a logo :-). Thanks -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

March 21, 2016

Re: [Pharo-users] [Pharo-dev] DeprecationAssistant

by Yuriy Tymchuk

Hi Alex, this is not about criticsâ¦ If you have a method like labeledObject ^ RTLabelled new in the latest roassal image and you will execute it, you will get a debugger deprecation warning with an option to fix that. Cheers. Uko > On 21 Mar 2016, at 14:07, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Hi! > > I cannot figure out what I should expect after loading DeprecationAssistant. I have loaded it and created a method: > -=-=-=-=-=-=-=-=-= > foo > self deprecated: 'use bar insteadâ > -=-=-=-=-=-=-=-=-= > > Is there anything that should be displayed in the critic list? > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On Mar 21, 2016, at 9:59 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote: >> >> HI everyone, >> >> last week Iâve created a little tool that automates deprecation resolution. The goal is to provide a help based on the existing code (no need for extra actions). You can read more here: http://blog.yuriy.tymch.uk/2016/03/deprecationassistant-aiding-developers.h… <http://blog.yuriy.tymch.uk/2016/03/deprecationassistant-aiding-developers.h…> >> >> You can install and try it out with: >> Metacello new >> repository: 'github://Uko/DeprecationAssistant' <github://Uko/DeprecationAssistant'>; >> baseline: 'DeprecationAssistant'; >> load >> >> This will add additional actions to the debugger once you will get a deprecation warning. >> >> Have fun! >> Cheers. >> Uko >

March 21, 2016

Re: [Pharo-users] Seaside 3.1 and 3.2 in Pharo 5

by Hilaire

Thanks Johan! Le 20/03/2016 19:49, Johan Brichau a Ã©crit : > If you are looking to use Seaside in Pharo 5, please go ahead and let us > know if you run into any issues. > Seaside 3.1.5 and 3.2.0 (unreleased) load into Pharo 5 and all tests are > green [1]. > -- Dr. Geo http://drgeo.eu

March 21, 2016

Re: [Pharo-users] DeprecationAssistant

by Alexandre Bergel

Hi! I cannot figure out what I should expect after loading DeprecationAssistant. I have loaded it and created a method: -=-=-=-=-=-=-=-=-= foo self deprecated: 'use bar insteadâ -=-=-=-=-=-=-=-=-= Is there anything that should be displayed in the critic list? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Mar 21, 2016, at 9:59 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > HI everyone, > > last week Iâve created a little tool that automates deprecation resolution. The goal is to provide a help based on the existing code (no need for extra actions). You can read more here: http://blog.yuriy.tymch.uk/2016/03/deprecationassistant-aiding-developers.h… <http://blog.yuriy.tymch.uk/2016/03/deprecationassistant-aiding-developers.h…> > > You can install and try it out with: > Metacello new > repository: 'github://Uko/DeprecationAssistant' <github://Uko/DeprecationAssistant'>; > baseline: 'DeprecationAssistant'; > load > > This will add additional actions to the debugger once you will get a deprecation warning. > > Have fun! > Cheers. > Uko

March 21, 2016

Re: [Pharo-users] [Pillar] Logo for Pillar

by Yuriy Tymchuk

Hi, IMHO itâs too airy, to much free area. By the way, have you seen the previous logo? https://github.com/pillar-markup Uko > On 18 Mar 2016, at 15:30, Thibault ARLOING <thibault.arloing(a)hotmail.fr> wrote: > > Hi, > > With a mate, we've worked on a logo for Pillar. > We just want feedbacks on it. > > You can fin the logo join files. > > thanks :) > > Good afternoon, > Thibault > <pillar2.svg>

March 21, 2016