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

Re: [Pharo-dev] when is cleanUpForRelease called on the build server?

by Andrei Chis

Thanks Marcus. So you run the cleanup before running the tests. Cheers, Andrei On Thu, Mar 26, 2015 at 7:39 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 25 Mar 2015, at 23:26, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > Hi, > > When is cleanUpForRelease called during the build process on the Pharo CI? > Had a quick look but could not find it. > > We want to add some tests to our build to stress test the inspector and > spotter, to maybe catch future memory leaks :) > > > https://ci.inria.fr/pharo/job/Pharo-4.0-Update-Step-1-Tracker > > loads the update and then does the cleanup: > > ./pharo Pharo.image update --from-file=updates40.staged > ./pharo Pharo.image clean --release > >

March 26, 2015

Re: [Pharo-dev] could the size of Playground be reduced a bit

by Norbert Hartl

Even better than just reducing the fixed size. Thank you! Norbert > Am 26.03.2015 um 00:47 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > > Hi, > > In the latest GT-Playground and GT-Inspector you get the following behavior: > - you can resize the windows, and the windows spawned afterwards will remember the dimensions, or > - you can explicitly specify the size you prefer in the settings browser. > > https://pharo.fogbugz.com/f/cases/14541/Editing-the-default-inspector-windo… > > Cheers, > Doru > > > On Wed, Mar 25, 2015 at 11:43 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>> oh resizing is already mandatory I am afraid. When the object inspected is big, there is no other option but to resize the whole window. And many if not most useful Pharo objects worth inspecting are big. >> >> I rarely have to resize it (arguably I'm not using to full potential); but my point was that there should be sensible defaults for both primary (most common) use cases. You can never satisfy everyone 100%. >> >>> Plus resizing windows is part of the experience of using a window GUI system. >> >> As a long time user of dwm the very idea of resizing windows with mouse is repulsive to me. (I still struggle in this respect with Pharo... but I have a dream. :)) >> >> Peter > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

March 26, 2015

Re: [Pharo-dev] get.pharo.org broken ?

by Marcus Denker

Strange, the latest.zip did not have +r for others on the server. I changed it. Marcus > On 25 Mar 2015, at 21:42, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > And also > > # wget http://files.pharo.org/image/40/latest.zip > --2015-03-25 20:41:11-- http://files.pharo.org/image/40/latest.zip > Resolving files.pharo.org (files.pharo.org) 185.59.222.11 > Connecting to files.pharo.org (files.pharo.org)|185.59.222.11|:80... connected. > HTTP request sent, awaiting response... 403 Forbidden > 2015-03-25 20:41:11 ERROR 403: Forbidden. > > ! > >> On 25 Mar 2015, at 21:36, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> # curl get.pharo.org/40 | bash >> % Total % Received % Xferd Average Speed Time Time Time Current >> Dload Upload Total Spent Left Speed >> 100 2595 100 2595 0 0 8888 0 --:--:-- --:--:-- --:--:-- 8917 >> Downloading the latest 40 Image: >> http://files.pharo.org/image/40/latest.zip >> [image.ekAo7T/image.zip] >> End-of-central-directory signature not found. Either this file is not >> a zipfile, or it constitutes one disk of a multi-part archive. In the >> latter case the central directory and zipfile comment will be found on >> the last disk(s) of this archive. >> unzip: cannot find zipfile directory in one of image.ekAo7T/image.zip or >> image.ekAo7T/image.zip.zip, and cannot find image.ekAo7T/image.zip.ZIP, period. >> >> Esteban ? > >

March 26, 2015

Re: [Pharo-dev] Existing <script> <example> pragmas and new GT needs

by Sven Van Caekenberghe

What happened to "The needs of the many outweigh the needs of the few" - LLAP ? > On 25 Mar 2015, at 23:28, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi Torsten, > > We will rename <example> back to <gtExample> and keep the API as it is. That will leave Pharo 4 with one <example> method while the other 100 will use <gtExample>. This will be available with the next GT integration. > > The decision has nothing to do with arguments. This discussion managed to sadden me and I will not continue it anymore. The release is too important and we got distracted from the goal. > > I wish you all a peaceful night. > > Doru > > > On Wed, Mar 25, 2015 at 10:54 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > stepharo wrote: > >I'm confused. Did you use the <example> pragmas before? > > Yes, this was already integrated in Pharo 4 since several weeks. It allows marking an class > side method without relying on the exampleXXX pattern. Maybe I should have made more noise about > it. > > So you can have a class side example method to demonstrate or give something to > others to learn: > > tryThisOut > <example> > ... > > without having to rely on the exampleXXX pattern. > > Nautilus honors this the same way as for exampleXXX methods with a play icon that one > can click and that executes the example. No need to have or select "self tryThisOut" > in a comment. And you can choose selector names you like and that are good for your > users like "simpleExampleToTryOut" or "confusingExampleToDisplay". > > It would also allow us collect all example methods easily and display them in an example > browser for newbees they can use to go through all example methods and learn from > the code. > > > Tudor in parallel worked on <gtExample> and unfortunately changed this to <example> > afterwards as well (maybe upon your request). He has a new feature that when you open > an inspector on a class you can see "example instances" of that class in a new tab. > > For this to work he needed also a pragma - by choosing the same name we got this > conflict in the pragmas. > > But it is not about who was first - it is about correct naming. This new feature in GT > requires a method to return "example instances" - thats why I suggested to use a better > name like <exampleInstance> or just <exemplar>. > > With this we would be clear in naming, would not conflict and be sove both issues > (the new preview and not relying on exampleXXX for example methods). > > I would neither like to loose the fix that I already provided and that was integrated > nor the nice work of Tudor. > > > I'm ok with exemplar too. > > Attached is a changeset "GTExemplars.1.cs" that: > > - changes the GT use of <example>, <example:> and <exampleFrom:> to <exemplar> and <exemplar:> and <exemplarFrom:> > - it also uses correct method naming for the returned exemplars/sample instances of the class, for instance #gtExampleSimple -> simpleExemplar > - it also changes GTExample -> GTExemplar, GTExampleExtractionStrategy -> GTExamplarExtractionStrategy, ... > and also uses ...exemplar... instead of ...example... for the methods and temporaries in these classes. > > With this changeset the new feature does not conflict. The changeset is based on Pharo4.0 Latest update: #40582 as of today > and when quickly integrated this should be easy to fileIn/integrate into the externally managed GT tools as well > as the image. > > > With this integrated into GT/Pharo 4 we would not conflict and make things clear: > > 1. we use the term "example" for regular Smalltalk code examples as most of us knows from the past > either in an exampleXXX method or with the <example> pragma. > > 2. And we can use the concept and term "exemplar" to return instances/exemplars of a class and browse them > with the new preview feature Tudor introduced. > "Give me an exemplar of class Character, give me an exemplar of class String, ..." > > => I'll leave the decison to the community or finally the board to integrate this as I communicated my > points and reasons now often enough including an attached ready to be integrated solution. > > I did my homework now and leave this to others to decide and either deny it or open a bug to > integrate. > > > PS: From far it looks like a bikeshed discussion :) > > May be. But I'm very serious about this as you see because getting names and concepts right is often > the hardest part. And it would be hard to change after the release because people will use it already. > > Bye > T. > > > > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

March 26, 2015

Re: [Pharo-dev] Making Seaside work in Pharo 4

by Marcus Denker

It was in the âprivateâ category and as such removed when there where no senders anymore after a cleanup. > On 25 Mar 2015, at 18:55, stepharo <stepharo(a)free.fr> wrote: > > strange that it was removed. > > Le 24/3/15 09:21, Stephan Eggermont a Ã©crit : >> In Issue 13739, build 40145 classesInTheSelectedPackage in Nautilus was removed. What is the correct way to replace it? WABrowser uses a >> nautilus browser to show a web-based browser. >> (build 609, Seaside #'release3.1' pharo4, from ci) >> >> WABrowserTest>>testContentsNotifying >> | model | >> model := WABrowser browserClass new. >> model systemCategoryListIndex: (model systemCategoryList indexOf: 'Seaside-Tests-Pharo-Development'). >> model classListIndex: (model classList indexOf: #WABrowserTest). >> model messageCategoryListIndex: (model messageCategoryList indexOf: #'-- all --'). >> [ >> self assert: >> (model contents: 'sampleMethod >> ^ 1 + 1' >> notifying: self). >> self assert: message isNil ] >> ensure: [ WABrowserTest removeSelectorSilently: #sampleMethod ] >> >> Stephan >> >> >> > >

March 26, 2015

Re: [Pharo-dev] could the size of Playground be reduced a bit

by kilon alios

very useful thanks Tudor :) On Thu, Mar 26, 2015 at 1:47 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > In the latest GT-Playground and GT-Inspector you get the following > behavior: > - you can resize the windows, and the windows spawned afterwards will > remember the dimensions, or > - you can explicitly specify the size you prefer in the settings browser. > > > https://pharo.fogbugz.com/f/cases/14541/Editing-the-default-inspector-windo… > > Cheers, > Doru > > > On Wed, Mar 25, 2015 at 11:43 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > >> oh resizing is already mandatory I am afraid. When the object inspected >>> is big, there is no other option but to resize the whole window. And many >>> if not most useful Pharo objects worth inspecting are big. >>> >> I rarely have to resize it (arguably I'm not using to full potential); >> but my point was that there should be sensible defaults for both primary >> (most common) use cases. You can never satisfy everyone 100%. >> >> Plus resizing windows is part of the experience of using a window GUI >>> system. >>> >> As a long time user of dwm the very idea of resizing windows with mouse >> is repulsive to me. (I still struggle in this respect with Pharo... but I >> have a dream. :)) >> >> Peter >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

March 26, 2015

Re: [Pharo-dev] when is cleanUpForRelease called on the build server?

by Marcus Denker

> On 25 Mar 2015, at 23:26, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > Hi, > > When is cleanUpForRelease called during the build process on the Pharo CI? > Had a quick look but could not find it. > > We want to add some tests to our build to stress test the inspector and spotter, to maybe catch future memory leaks :) > https://ci.inria.fr/pharo/job/Pharo-4.0-Update-Step-1-Tracker <https://ci.inria.fr/pharo/job/Pharo-4.0-Update-Step-1-Tracker> loads the update and then does the cleanup: ./pharo Pharo.image update --from-file=updates40.staged ./pharo Pharo.image clean --release

March 26, 2015

Re: [Pharo-dev] get.pharo.org broken ?

by HernÃ¡n Morales Durand

I have the same behavior from the University machines [hernan@igevet sf]$ wget -O- -v get.pharo.org/30+vm | bash --2015-03-26 02:06:04-- http://get.pharo.org/30+vm Resolving get.pharo.org... 128.93.162.72 Connecting to get.pharo.org|128.93.162.72|:80... failed: Connection timed out. Retrying. --2015-03-26 02:07:08-- (try: 2) http://get.pharo.org/30+vm Connecting to get.pharo.org|128.93.162.72|:80... ^C >From my home it works perfectly. Cheers, HernÃ¡n 2015-03-25 17:42 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > And also > > # wget http://files.pharo.org/image/40/latest.zip > --2015-03-25 20:41:11-- http://files.pharo.org/image/40/latest.zip > Resolving files.pharo.org (files.pharo.org) 185.59.222.11 > Connecting to files.pharo.org (files.pharo.org)|185.59.222.11|:80... > connected. > HTTP request sent, awaiting response... 403 Forbidden > 2015-03-25 20:41:11 ERROR 403: Forbidden. > > ! > > > On 25 Mar 2015, at 21:36, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > # curl get.pharo.org/40 | bash > > % Total % Received % Xferd Average Speed Time Time Time > Current > > Dload Upload Total Spent Left > Speed > > 100 2595 100 2595 0 0 8888 0 --:--:-- --:--:-- > --:--:-- 8917 > > Downloading the latest 40 Image: > > http://files.pharo.org/image/40/latest.zip > > [image.ekAo7T/image.zip] > > End-of-central-directory signature not found. Either this file is not > > a zipfile, or it constitutes one disk of a multi-part archive. In the > > latter case the central directory and zipfile comment will be found on > > the last disk(s) of this archive. > > unzip: cannot find zipfile directory in one of image.ekAo7T/image.zip or > > image.ekAo7T/image.zip.zip, and cannot find > image.ekAo7T/image.zip.ZIP, period. > > > > Esteban ? > > >

March 26, 2015

Re: [Pharo-dev] could the size of Playground be reduced a bit

by Tudor Girba

Hi, In the latest GT-Playground and GT-Inspector you get the following behavior: - you can resize the windows, and the windows spawned afterwards will remember the dimensions, or - you can explicitly specify the size you prefer in the settings browser. https://pharo.fogbugz.com/f/cases/14541/Editing-the-default-inspector-windo… Cheers, Doru On Wed, Mar 25, 2015 at 11:43 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > oh resizing is already mandatory I am afraid. When the object inspected is >> big, there is no other option but to resize the whole window. And many if >> not most useful Pharo objects worth inspecting are big. >> > I rarely have to resize it (arguably I'm not using to full potential); but > my point was that there should be sensible defaults for both primary (most > common) use cases. You can never satisfy everyone 100%. > > Plus resizing windows is part of the experience of using a window GUI >> system. >> > As a long time user of dwm the very idea of resizing windows with mouse is > repulsive to me. (I still struggle in this respect with Pharo... but I have > a dream. :)) > > Peter > -- www.tudorgirba.com "Every thing has its own flow"

March 25, 2015

Re: [Pharo-dev] Update question

by Ben Coman

On Thu, Mar 26, 2015 at 3:01 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > > That wouldn't work. I save my image often under a different image name > because I tend to break the image or it crashes. With the changes log not > working the only feasible way is to make a lot of copies of your images. > I frequently use <Copy> image in PharoLauncher. I like that it autogenerates a new name. However its done outside the image so may not fit your workflow. Maybe dealing with images saved from within the image is an enhancement PharoLauncher could consider. cheers -ben

March 25, 2015