May 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Seaside-dev] Updated Seaside Control Panel for Pharo 6 / Seaside 3.2

by Johan Brichau

> I want to try (in the future), but the way I have Seaside in my images, it is loaded from StHub, so I have no GitHub repos. > > Is there a place/document that describes the procedure of how to do it the recommended way ? And a description of how the releases are structured ? I started writing that last year: https://github.com/SeasideSt/Seaside/wiki/Contributing <https://github.com/SeasideSt/Seaside/wiki/Contributing> Since Pharo 6 has Iceberg now, I think itâs a good time to make the real switch. Last year, Philippe made all changes to the develop branch at the ESUG sprint. I dropped the ball on Seaside last year and did not produce any updated configuration or anything. Trying to pick it up right now and hoping others will follow the model ;) Johan

May 25, 2017

Re: [Pharo-dev] [Seaside-dev] Updated Seaside Control Panel for Pharo 6 / Seaside 3.2

by Sven Van Caekenberghe

> On 25 May 2017, at 09:48, Johan Brichau <johan(a)inceptive.be> wrote: > > Hi Sven and Thorsten, > > Thanks for this. Iâm taking the steps necessary to integrate everything now: > - copy to github > - adapt the configuration for 3.2.x OK, thanks, Johan. > In the future, making pull requests against the github repo will be the easiest and advised way. I want to try (in the future), but the way I have Seaside in my images, it is loaded from StHub, so I have no GitHub repos. Is there a place/document that describes the procedure of how to do it the recommended way ? And a description of how the releases are structured ? > Iâll ping back here later today.. > > johan > >> On 25 May 2017, at 00:38, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Thx Torsten. >> >> Is that enough to get it included in the main development line, what else has to happen ? >> >>> On 24 May 2017, at 22:34, Torsten Bergmann <astares(a)gmx.de> wrote: >>> >>> Hi Sven, >>> >>> I uploaded the MCZ to the Seaside repo htto://smalltalkhub.com/mc/Seaside/Seaside32/main >>> and tested it. Looks fine and all is working for me. >>> >>> The only thing I'm not sure about is that Philippe (PMM) in Seaside-Pharo-Tools-Spec-pmm.21 >>> made a distinction to either use NewListModel or FastTableModel. >>> The issue was also noted in https://github.com/SeasideSt/Seaside/issues/869 >>> >>> I guess this not necessary anymore as Pharo 6 has FastTableModel only. >>> >>> Additionally: >>> ============ >>> I extended your version so that "Browse" opens a real webbrowser when two conditions are >>> met: - the Pharo image includes the WebBrowser package (which one can load from catalog) >>> - teh adaptor is running >>> >>> In any other case it has the same behavior as before by just inspecting the adaptor. >>> >>> This extension can be found in "Seaside-Pharo-Tools-Spec-TorstenBergmann.28" in the >>> same repository. >>> >>> Thanks >>> Torsten >>> >>>> Gesendet: Mittwoch, 24. Mai 2017 um 16:27 Uhr >>>> Von: "Sven Van Caekenberghe" <sven(a)stfx.eu> >>>> An: "Pharo Development List" <pharo-dev(a)lists.pharo.org>, "Seaside - developer list" <seaside-dev(a)lists.squeakfoundation.org> >>>> Betreff: [Pharo-dev] Updated Seaside Control Panel for Pharo 6 / Seaside 3.2 >>>> >>>> Hi, >>>> >>>> I updated the Seaside Control Panel for Pharo 6 / Seaside 3.2. As far as I can see, it works fine now. >>>> >>>> I don't know the exact procedure to get this into Seaside proper, hence I include the MC package. >>>> >>>> It is obviously important to get this in before we release Pharo 6, but it is probably also a good idea that somebody else has a look at what I did. >>>> >>>> === >>>> Name: Seaside-Pharo-Tools-Spec-SvenVanCaekenberghe.20 >>>> Author: SvenVanCaekenberghe >>>> Time: 24 May 2017, 4:17:49.490067 pm >>>> UUID: b1168881-a70c-0d00-9de6-8d500cd45859 >>>> Ancestors: Seaside-Pharo-Tools-Spec-JohanBrichau.19 >>>> >>>> Updated the Seaside Control Panel for Pharo 6 / Seaside 3.2 using latest Spec conventions >>>> >>>> - Add a refresh button to the main toolbar to sync with changes done outside the UI (add a #refreshAdaptors action and use it for add/remove updating as well) >>>> - Inform the user when remove fails due to a still running adaptor >>>> - Use IconListModel instead of NewListModel >>>> - Fix selection maintenance on the list of adaptors >>>> - Fix the context menu on the list of adaptors >>>> - Use new recommended icon access method >>>> - Added help strings to the buttons in the main toolbar >>>> - Added a proper About text >>>> - Add a window icon >>>> - Remove unused state/action stuff from the toolbar implementation >>>> === >>>> >>>> Sven >>>> >>>> >>>> >>>> PS: The 'Spec UI Framework' book was helpful as was Nicolai's help on the ML - Thank you. >>>> >>>> >>> _______________________________________________ >>> seaside-dev mailing list >>> seaside-dev(a)lists.squeakfoundation.org >>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev >> >> _______________________________________________ >> seaside-dev mailing list >> seaside-dev(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev > > _______________________________________________ > seaside-dev mailing list > seaside-dev(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

May 25, 2017

Re: [Pharo-dev] Booklet suggestion

by K K Subbu

Ben, I think there is a deeper need here. Writing good document is hard and keeping it in sync with code is harder still. A book/booklet separates content from the code and being frozen in time faces obsolescence. I would prefer to see a guidebook framework in Pharo that every package author can use to create a simple narrative on its features. Package authors and consumers have an incentive to keep the code and content in sync. If an Object is a recursion on the notion of a computer, why not provide, say a Note, as a recursive simplification of a book? The framework could be on the lines of Plugins, Tests. E.g. Package-Core Package-Plugins Package-Tests *Package-Guide* The guide framework should support active code (say to pop the source code for a method), active links to guides on which this package depends, automatic generation of table of contents, index of class references. Most of features already exists in Pharo but spread all over. They need a home. A package could also extend this basic framework with features (e.g. PDF package could export articles to PDF, Zinc could generate HTML). Regards .. Subbu On Thursday 25 May 2017 07:03 AM, Ben Coman wrote: > I've seen a few requests for short bits of code to use in playground for > a demo presentation. I wonder if it would be good to have a booklet to > gather these - seeded with Sven's excellent article... > https://medium.com/concerning-pharo/elegant-pharo-code-bb590f0856d0 > > It could include the recent meta-programming scripts like searching for > all class instance variables starting with a capital letter. > > The book might be named "Snippets", in a format presentable to laser > print on-site - something physical for attendees to take away with them > to quick demo to others back in their office. > > I can take the lead in setting it up. Anyone remember any relevant > posts in our archives? > > cheers -ben

May 25, 2017

Re: [Pharo-dev] [Seaside-dev] Updated Seaside Control Panel for Pharo 6 / Seaside 3.2

by Johan Brichau

Hi Sven and Thorsten, Thanks for this. Iâm taking the steps necessary to integrate everything now: - copy to github - adapt the configuration for 3.2.x In the future, making pull requests against the github repo will be the easiest and advised way. Iâll ping back here later today.. johan > On 25 May 2017, at 00:38, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Thx Torsten. > > Is that enough to get it included in the main development line, what else has to happen ? > >> On 24 May 2017, at 22:34, Torsten Bergmann <astares(a)gmx.de> wrote: >> >> Hi Sven, >> >> I uploaded the MCZ to the Seaside repo htto://smalltalkhub.com/mc/Seaside/Seaside32/main >> and tested it. Looks fine and all is working for me. >> >> The only thing I'm not sure about is that Philippe (PMM) in Seaside-Pharo-Tools-Spec-pmm.21 >> made a distinction to either use NewListModel or FastTableModel. >> The issue was also noted in https://github.com/SeasideSt/Seaside/issues/869 >> >> I guess this not necessary anymore as Pharo 6 has FastTableModel only. >> >> Additionally: >> ============ >> I extended your version so that "Browse" opens a real webbrowser when two conditions are >> met: - the Pharo image includes the WebBrowser package (which one can load from catalog) >> - teh adaptor is running >> >> In any other case it has the same behavior as before by just inspecting the adaptor. >> >> This extension can be found in "Seaside-Pharo-Tools-Spec-TorstenBergmann.28" in the >> same repository. >> >> Thanks >> Torsten >> >>> Gesendet: Mittwoch, 24. Mai 2017 um 16:27 Uhr >>> Von: "Sven Van Caekenberghe" <sven(a)stfx.eu> >>> An: "Pharo Development List" <pharo-dev(a)lists.pharo.org>, "Seaside - developer list" <seaside-dev(a)lists.squeakfoundation.org> >>> Betreff: [Pharo-dev] Updated Seaside Control Panel for Pharo 6 / Seaside 3.2 >>> >>> Hi, >>> >>> I updated the Seaside Control Panel for Pharo 6 / Seaside 3.2. As far as I can see, it works fine now. >>> >>> I don't know the exact procedure to get this into Seaside proper, hence I include the MC package. >>> >>> It is obviously important to get this in before we release Pharo 6, but it is probably also a good idea that somebody else has a look at what I did. >>> >>> === >>> Name: Seaside-Pharo-Tools-Spec-SvenVanCaekenberghe.20 >>> Author: SvenVanCaekenberghe >>> Time: 24 May 2017, 4:17:49.490067 pm >>> UUID: b1168881-a70c-0d00-9de6-8d500cd45859 >>> Ancestors: Seaside-Pharo-Tools-Spec-JohanBrichau.19 >>> >>> Updated the Seaside Control Panel for Pharo 6 / Seaside 3.2 using latest Spec conventions >>> >>> - Add a refresh button to the main toolbar to sync with changes done outside the UI (add a #refreshAdaptors action and use it for add/remove updating as well) >>> - Inform the user when remove fails due to a still running adaptor >>> - Use IconListModel instead of NewListModel >>> - Fix selection maintenance on the list of adaptors >>> - Fix the context menu on the list of adaptors >>> - Use new recommended icon access method >>> - Added help strings to the buttons in the main toolbar >>> - Added a proper About text >>> - Add a window icon >>> - Remove unused state/action stuff from the toolbar implementation >>> === >>> >>> Sven >>> >>> >>> >>> PS: The 'Spec UI Framework' book was helpful as was Nicolai's help on the ML - Thank you. >>> >>> >> _______________________________________________ >> seaside-dev mailing list >> seaside-dev(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev > > _______________________________________________ > seaside-dev mailing list > seaside-dev(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

May 25, 2017

Re: [Pharo-dev] multiple crashes on macOS Sierra

by Tudor Girba

Indeed, I was also in a Bloc image. I am now trying again in the latest Pharo/Moose and a fresh VM. Doru > On May 25, 2017, at 9:34 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi doru > > Yes I get the same. Now I was also in the bloc image, I got crash when resizing the host window. > > Stef > > On Wed, May 24, 2017 at 10:28 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Today I experienced multiple crashes on macOS Sierra. > > These happened during regular programming, mostly while typing code. I attached here the crash dump(s). I believe I heard Phil having the same issue with the stable Pharo VM. > > Does anyone else has the same issue? > > The VM is: > CoInterpreter VMMaker.oscog-eem.2203 uuid: 12d4afae-8498-4e76-8efe-60eba6ef4db2 May 2 2017 > StackToRegisterMappingCogit VMMaker.oscog-eem.2203 uuid: 12d4afae-8498-4e76-8efe-60eba6ef4db2 May 2 2017 > VM: 201705021552 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Tue May 2 08:52:41 2017 -0700 $ Plugins: 201705021552 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > > The Pharo update number is: 60482 > > Cheers, > Doru > > -- > www.tudorgirba.com > www.feenk.com > > "From an abstract enough point of view, any two things are similar." > > > > -- www.tudorgirba.com www.feenk.com "Some battles are better lost than fought."

May 25, 2017

Re: [Pharo-dev] multiple crashes on macOS Sierra

by Stephane Ducasse

Hi doru Yes I get the same. Now I was also in the bloc image, I got crash when resizing the host window. Stef On Wed, May 24, 2017 at 10:28 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Today I experienced multiple crashes on macOS Sierra. > > These happened during regular programming, mostly while typing code. I > attached here the crash dump(s). I believe I heard Phil having the same > issue with the stable Pharo VM. > > Does anyone else has the same issue? > > The VM is: > CoInterpreter VMMaker.oscog-eem.2203 uuid: 12d4afae-8498-4e76-8efe-60eba6ef4db2 > May 2 2017 > StackToRegisterMappingCogit VMMaker.oscog-eem.2203 uuid: > 12d4afae-8498-4e76-8efe-60eba6ef4db2 May 2 2017 > VM: 201705021552 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > Date: Tue May 2 08:52:41 2017 -0700 $ Plugins: 201705021552 > https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > > The Pharo update number is: 60482 > > Cheers, > Doru > > -- > www.tudorgirba.com > www.feenk.com > > "From an abstract enough point of view, any two things are similar." > > > >

May 25, 2017

Re: [Pharo-dev] Pharo booklet collection

by Stephane Ducasse

Thanks damien I will duplicate this script to all the booklets repo. My plan is to have also a jenkins job for each of them. On Tue, May 23, 2017 at 11:11 PM, Damien Pollet <damien.pollet(a)gmail.com> wrote: > Check the travis configuration file. It has the docker invocation that > will get the correct image and build the booklet. > https://github.com/SquareBracketAssociates/Booklet-Reddit/blob/master/. > travis.yml > > You can also build without docker but that requires an up-to-date TeXlive > 2016 (unfortunately we rely on some fixes that are not in the installation > iso, so you'd have to either use the net installer or do `tlmgr update > --self --all` after installing the iso snapshot) > > On 23 May 2017 at 15:25, Tim Mackinnon <tim(a)testit.works> wrote: > >> Hi - so I forked a repo (the Reddit one), and am reading through it to >> check for typos (Iâve see a few). Obviously I can correct those, but how do >> I actually preview my changes to ensure I havenât screwed it all up? >> >> Iâm guessing I need to install Docker and pull down a specific image - >> which I can then use to generate the output to test it? Or, is there an ST >> image that I can run on this directory? >> >> As a quick scan of whats in a book repo - it all looks a bit more >> complicated than I expected - with make files and what look like âinplace >> templatesâ (as in format1.format2.format3 etc). Having played around with >> Metalsmith.io I think its sort of similar, but It seems like there is >> more to learn somehow? >> >> Tim >> >> On 6 May 2017, at 11:36, Stephane Ducasse <stepharo.self(a)gmail.com> >> wrote: >> >> Hi phil >> >> yes I loved this idea. We got burned by that too. >> >> About pillar. The departure of Damien was not expected and it slows us >> quite a bit. >> >> We (mainly me helped with maxime) are working on >> - making the pillar core nicer >> - less dependencies >> - and with a small in image renderer :) We had fun with guille >> >> >> - In the pharo 60 version I started to clean the command-line. >> - merged many unmerged changes. >> >> But even with all the tests it is not easy.... >> I'm testing in addition with reall >> - book production >> - slides >> - html >> >> But it takes time and energy. I'm trying to remove the dependencies to >> magritte for example. >> >> Stef >> >> >> <Screen Shot 2017-05-06 at 12.33.18.png> >> >> >> On Sat, May 6, 2017 at 9:30 AM, phil(a)highoctane.be <phil(a)highoctane.be> >> wrote: >> >>> For books, there is the docker-texlive thing from Damien that we >>> looked into yesterday because TexLive was giving some headaches. >>> >>> https://github.com/philippeback/docker-texlive >>> >>> has my current thing for one to build a container with all >>> prerequisites for TexLive and Pharo installed. >>> >>> Idea is to clone the book repo on the host and get into an container >>> to build the book. >>> >>> There is a /work volume that can be mapped onto the host with the >>> docker run's -v command. >>> >>> Then just use ./download.sh in there to install Pharo and pillar in >>> the container. Do not do that in the host or you'll end up with wrong >>> versions (like my host is CentOS and the container is Ubuntu, even >>> worse with host is macOS or Windows). >>> >>> Then "make book" should give a book in build/ >>> There is a "make wipeout" command that obliterates the build folder >>> for good so you can start clean. No harm done on your files. >>> >>> Will document more of this but woul dbe nice if someone could check >>> this out too. >>> >>> There is a script in base/ to build the docker image. >>> >>> Phil >>> >>> On Sat, May 6, 2017 at 9:20 AM, Stephane Ducasse >>> <stepharo.self(a)gmail.com> wrote: >>> > I fixed it. >>> > The code for the web site in on github. >>> > >>> > Stef >>> > >>> > On Tue, May 2, 2017 at 10:32 PM, Esteban A. Maringolo < >>> emaringolo(a)gmail.com> >>> > wrote: >>> >> >>> >> Correct link seems to be >>> >> >>> >> >>> >> http://files.pharo.org/books-pdfs/booklet-Glorp/2017-05-02-G >>> lorp.spiral.pdf >>> >> Esteban A. Maringolo >>> >> >>> >> >>> >> 2017-05-02 17:28 GMT-03:00 phil(a)highoctane.be <phil(a)highoctane.be>: >>> >> > link for glorp gives smacc book error >>> >> > >>> >> > On Tue, May 2, 2017 at 10:25 PM, Stephane Ducasse >>> >> > <stepharo.self(a)gmail.com> >>> >> > wrote: >>> >> >> >>> >> >> Hi Pharoers >>> >> >> >>> >> >> You are lucky. The "Pharo booklet collection" edited by S. Ducasse >>> is >>> >> >> arriving... >>> >> >> >>> >> >> Are you ready to read nice and focused booklets? >>> >> >> >>> >> >> You can find at http://files.pharo.org/books/ in beta version: >>> >> >> >>> >> >> Smacc: the Smalltalk Compiler Compiler by J. Brant, T. Goubier, J. >>> >> >> Lecerf >>> >> >> and S. Ducasse. >>> >> >> Glorp: the Object Relational Mapper framework by E. Maringolo, N. >>> Pratt >>> >> >> and R. Withney >>> >> >> >>> >> >> All the book material is hosted on >>> >> >> https://github.com/SquareBracketAssociates so you can contribute! >>> Fix >>> >> >> typos >>> >> >> and propose new material. >>> >> >> >>> >> >> We are planning a booklet on Magritte, Reddit in 10 cool classes, >>> >> >> Voyage, >>> >> >> and Mocking with BabyMock and Mocketry, XML (but we need a writer) >>> and >>> >> >> potentially PetitParser. >>> >> >> >>> >> >> If you have material for a tutorial and you would like to be part >>> of >>> >> >> the >>> >> >> Pharo Booklet Collection contact S. Ducasse. >>> >> >> >>> >> >> S. Ducasse >>> >> > >>> >> > >>> >> >>> > >>> >>> >> >> > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet >

May 25, 2017

100% out next 4 days

by Esteban Lorenzano

Hi, Iâve been on holidays the whole week but listening and answering mails in general. Now Iâm out of internet until monday (I hope to survive ;) ). Anyway, any question/PR/etc.: monday ! :) cheers, Esteban

May 25, 2017

Booklet suggestion

by Ben Coman

I've seen a few requests for short bits of code to use in playground for a demo presentation. I wonder if it would be good to have a booklet to gather these - seeded with Sven's excellent article... https://medium.com/concerning-pharo/elegant-pharo-code-bb590f0856d0 It could include the recent meta-programming scripts like searching for all class instance variables starting with a capital letter. The book might be named "Snippets", in a format presentable to laser print on-site - something physical for attendees to take away with them to quick demo to others back in their office. I can take the lead in setting it up. Anyone remember any relevant posts in our archives? cheers -ben

May 25, 2017

NLP Library + Generating Documentation

by Myroslava Romaniuk

For my university end-of-term programming project which I am doing in Pharo, I created a method that returns a Bag of all words used in the courses' description repeated the same amount of times that they are in the text (I am working with Udacity API) so I could use them as keywords and determine which technologies are mentioned the most in each course. I am wondering how could I remove 'this' from the list of repeated words, and how to remove punctuation marks attached to the word? Do I use sentence segmentation in this NLP library <https://github.com/mark-watson/nlp_smalltalk> or is there another way to do that? And I don't really need verbs either so I suppose I should use Entity Recognition from the NLP Library? One more thing: as this is my uni project it needs to be sufficiently documented. Is there a way to generate documentation in Pharo? Cheers, Myroslava

May 24, 2017