- Pharo-users - lists.pharo.org

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

DeprecationAssistant

by Yuriy Tymchuk

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'; 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

Seaside 3.1 and 3.2 in Pharo 5

by Torsten Bergmann

Issues I've found directly: 1. Seaside still uses #subStrings: instead of substrings: on several places. #subStrings: is deprecated since April 2015. 2. The Seaside control panel icon in menu is not displayed => the icon expression in WAPharoServerAdapterSpecBrowser(class)>>menuCommandOn: returns a blank icon because it is not found Changing to: menuCommandOn: aBuilder <worldMenu> (aBuilder item: #ServerAdapterBrowser) order: 0.21; parent: #Tools; label: 'Seaside Control Panel'; icon: (Smalltalk ui icons seasideAdaptorRunningIcon); action: [ WAPharoServerAdapterSpecBrowser open ] will fix that. 3. Running/stopped icons in Server adopter are not shown in Pharo 5. Change to iconForAdaptor: anAdaptor ^ anAdaptor isRunning ifTrue:[Smalltalk ui icons seasideAdaptorRunningIcon] ifFalse:[Smalltalk ui icons seasideAdaptorStoppedIcon ] to make it work.

March 20, 2016

Re: [Pharo-users] [Pharo-dev] 3 new Pharo videos

by Alexandre Bergel

Hubcap is great!! It should definitely be part of Pharo. Can it show the project description? Cheers, Alexandre > On Mar 18, 2016, at 4:56 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > > I provided 3 new videos about my tools/goodies on YouTube: > > Pharo OS-Linux-Ubuntu > https://www.youtube.com/watch?v=1X42GFbW4hg > > Pharo Hubcap > https://www.youtube.com/watch?v=2Kwr8bkSI7M > > Pharo Pomodoro > https://www.youtube.com/watch?v=w00IBi9iM2Y > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 20, 2016

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

by Johan Brichau

Hi Cyril, > I use Seaside 3.1 in Pharo 5 and I have an application running with this > setup currently. Great! There were indeed very few failing tests that were fixed quickly. I think most of Seaside was just working and you confirm that. > This is the main issues I got the past few weeks: > - When we load Seaside of Pharo 5 we have to add "onWarningLog" in order > to avoid a lot of deprecation warning. > - When we register a component to WAAdmin we also have a deprecation > warning. For Seaside 3.1.5, this will remain the case. The tests are fixed and the broken parts have been replaced but the deprecation warning about #subStrings: will not be fixed anymore in Seaside 3.1 For Seaside 3.2, they have been addressed and you should not get any of those anymore. > - In the status component we got a MNU in the VM tab thanks for reporting, will look into that. > - In the latest Pharo5 the seaside adaptor is not launched by default on > 8080. We have to add it manually (probably because of the SessionManager > changes). Aha, indeed. The Grease abstraction for this needs to be changed. Will take a look asap. > If I see other problems I will contact you :) Great. You can also report issues on the issue tracker: https://github.com/SeasideSt/Seaside/issues <https://github.com/SeasideSt/Seaside/issues> > > In my baseline I load Seaside3 stable, which is the realise 3.1 I think. Yes, thatâs correct. I would suggest using 3.2.0 from now on if youâre not running a production environment though. Itâs still a moving target but itâs good if people experiment with it. cheers Johan

March 20, 2016

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

by Cyril Ferlicot D.

Le 20/03/2016 19:49, Johan Brichau a Ã©crit : > Hi Pharoers, > > 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]. > Hi, I use Seaside 3.1 in Pharo 5 and I have an application running with this setup currently. I thought about sending a mail to the seaside mailing list soon but if you ask I will respond here :) This is the main issues I got the past few weeks: - When we load Seaside of Pharo 5 we have to add "onWarningLog" in order to avoid a lot of deprecation warning. - When we register a component to WAAdmin we also have a deprecation warning. - In the status component we got a MNU in the VM tab - In the latest Pharo5 the seaside adaptor is not launched by default on 8080. We have to add it manually (probably because of the SessionManager changes). If I see other problems I will contact you :) In my baseline I load Seaside3 stable, which is the realise 3.1 I think. > Also: I know the finalization of 3.2.0 is long overdue, so news about > that is coming soon. > > cheers, > Johan > > [1] https://ci.inria.fr/pharo-contribution/job/Seaside/ > > âLoad release 3.1" > Metacello new > configuration: 'Seaside3'; > repository: > 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; > version: #'release3.1'; > load. > > âLoad pre-release 3.2" > Metacello new > configuration: 'Seaside3'; > repository: > 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; > version: #â3.2.0'; > load -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

March 20, 2016