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

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

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

by Sven Van Caekenberghe

SUPER !! Thanks > On 20 Mar 2016, at 19:49, Johan Brichau <johan(a)inceptive.be> wrote: > > 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]. > > 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

March 20, 2016

Seaside 3.1 and 3.2 in Pharo 5

by Johan Brichau

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]. 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/ <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

March 20, 2016

Re: [Pharo-users] Image Cleaner no longer useful?

by Stephan Eggermont

Hello Maximiliano On 20-03-16 13:29, Maximiliano Tabacman via Pharo-users wrote: > With the latest Image (50651) and VM, the issue remains the same. As Marcus wrote, that is a well-known problem. At the moment, there is one higher priority issue on the image side, and it might well be related. Furthermore, it might be related to the vm switch to spur, and stabilizing that is higher priority and currently takes a lot of effort, as you can see on pharoproject.slack.com, pharo-dev and vm-dev Stephan

March 20, 2016

Re: [Pharo-users] Image Cleaner no longer useful?

by Maximiliano Tabacman

With the latest Image (50651) and VM, the issue remains the same. The most critical part for me is the fact that cleaning the image (at least using ImageCleaner) does not reduce its size.I have a commercial product with users already using it, who obtain the product by downloading. This issue causes my product to be at least double the size in total because of the image not being reduced, and sometimes more. I have no idea how to help solve this issue, but if it remains once Pharo 5 is released next month, that means I won't be able to use it for my product, and I would be stuck with older versions where the cleaning process worked better. Should I be addressing this issue in another list? Maybe vote up how critical it is in some pending bugs list somewhere? Don't get me wrong, I love Pharo and all the community work being done. I love the fact that I can get a humble commercial product out to the users.I just think maybe other products are more server based and not affected by this issue, but for anyone creating products with Pharo that are to be downloaded by the customers it should be top priority. Thanks for Pharo, and thanks for any help or guidance you may be able to provide on this matter. On Sunday, February 7, 2016 1:10 PM, Maximiliano Tabacman via Pharo-users <pharo-users(a)lists.pharo.org> wrote: I've got some additional details. Using the old VM at:Â http://files.pharo.org/vm/pharo/win/Pharo-VM-win-stable.zip I downloaded a fresh 50491 image at:http://files.pharo.org/image/50-preSpur/50491.zip Opened a playground and executedImageCleaner cleanUpForProduction This was really fast, and in 2 minutes the process was complete. Then I downloaded the 50492 image at:http://files.pharo.org/image/50-preSpur/50492.zip Did the sameÂ ImageCleaner cleanUpForProduction,Â only this time is took about half an hour to do the same. Hope that helps to catch the reason.Thanks On Friday, February 5, 2016 9:33 AM, Maximiliano Tabacman via Pharo-users <pharo-users(a)lists.pharo.org> wrote: Thanks for the reply Marcus.I just checked, and can confirm that the old process took only 2 minutes and converted aÂ 58,2 MB image (includes Seaside and my web product) into aÂ 26,4 MB production image. By looking at PharoDebug.log, I can tell that this version is: VM: Win32 - IX86 - 6.1 - NBCoInterpreter NativeBoost-CogPlugin-HolgerHansPeterFreyther.21 uuid: e0df6e2d-5694-40e2-8035-dc217200b424 Sep 25 2014NBCogit NativeBoost-CogPlugin-HolgerHansPeterFreyther.21 uuid: e0df6e2d-5694-40e2-8035-dc217200b424 Sep 25 2014https://github.com/pharo-project/pharo-vm.git Commit: 81b5d19917dcb78f22482a780deec48c53738396 Date: 2014-09-20 14:36:18 +0200 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14858Image: Pharo5.0 [Latest update: #50491] Hope that helps. This is Pharo 5, so the Image Cleaner must have broken at some point after this version. Let me know if there is any additional information I can provide to help figure it out. On Thursday, February 4, 2016 12:22 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: Hello, Sorry for the late answer. I think there are multiple problemsâ¦ 1) slowness. This is strange that unloading packages is so slow. This looks like a bug to me. 2) image size in Pharo5: We have a bug right now that images *never* shrink. This means that if you savean image once with 80MB, even if the GC cleans up, the saved image stays 80MB. We should fix bothâ¦. On 25 Jan 2016, at 13:32, Maximiliano Tabacman via Pharo-users <pharo-users(a)lists.pharo.org> wrote: From: Maximiliano Tabacman <mtabacman(a)yahoo.com> Subject: Image Cleaner no longer useful? Date: 25 January 2016 at 13:31:28 GMT+1 To: "pharo-users(a)lists.pharo.org" <pharo-users(a)lists.pharo.org> Reply-To: Maximiliano Tabacman <mtabacman(a)yahoo.com> Hi, and sorry if this has already been discussed. In Pharo 3, I used to be able to do: ImageCleaner cleanUpForProduction and that would correctly remove a lot of unneeded code in the image when preparing for a productive release.Then I would save the cleaned image, and since it had been cleaned, it would be smaller than the original development image (say from 60 mb to 25 mb).This process would take about 2-3 minutes. Then, in Pharo 4 it seems some changes were made here, since the same process took a lot more, like 20 minutes. When I first tried Pharo 5, I was happy to see that it was again down to 2-3 minutes. And here comes my question...Why is it that since some 2 months ago (maybe more), the Pharo 5 images once again require like 20 minutes to complete the cleanUpForProduction process? Also, and this is the most relevant to me, it no longer reduces the image size.So if I want to release a Pharo 5 version based on the latest images, I would be shipping a product that is more than twice the size of previous public versions of my software! Thanks for any insights into this. If it is a known bug, I would like to know if there is any workaround, or alternative objects that I should be using for the process.Also, if it would help for me to run any tests in particular to share and help in fixing this, please let me know.

March 20, 2016

Re: [Pharo-users] extracting segments in an array

by Damien Pollet

SequenceableCollection mostly, but possibly streams as well On 19 March 2016 at 21:21, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > Hi Damien, > > I didn't understood, which kind of sequences? > > > 2016-03-19 7:40 GMT-03:00 Damien Pollet <damien.pollet+pharo(a)gmail.com>: > >> Yeah if we redesign the String API it should account for Arrays and >> probably other kinds of sequences tooâ¦ >> >> On 19 March 2016 at 11:28, stepharo <stepharo(a)free.fr> wrote: >> >>> copyFrom:to: >>> >>> Stef >>> >>> Le 19/3/16 11:22, stepharo a Ã©crit : >>> >>> Hi >>>> >>>> I have an array and I would like to extract a segment of elements and I >>>> did not find >>>> >>>> array from: start to: end >>>> >>>> Did I miss something obvious? >>>> >>>> Stef >>>> >>>> >>>> >>> >>> >> >

March 20, 2016