- Pharo-dev - lists.pharo.org

Pharo booklet collection
by Stephane Ducasse May 25, 2017

May 25, 2017

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

5 10

100% out next 4 days
by Esteban Lorenzano May 25, 2017

May 25, 2017

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

1 0

NLP Library + Generating Documentation
by Myroslava Romaniuk May 24, 2017

May 24, 2017

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

1 0

Re: [Pharo-dev] Pharo booklet collection
by Tim Mackinnon May 24, 2017

May 24, 2017

I have submitted a pull request for the Reddit booklet - I didnât get a chance to try the docker image to see the results (I will get up to speed with that) - but I didnât want to have a branch out for too long. Its my first try at this (I liked the tutorial, it taught me a lot), and I wasnât sure how much to change in the text (and I certainly donât want to upset any previous authors - as its very readable in its present form). Tim > On 23 May 2017, at 18:34, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > Hi tim > > you can follow the pillar chapter in entreprise book. > Now to produce pdf you have to install latex so I would not worry and do the pull request. > I will set up a jenkins job for each of the booklet so that people do not have to install latex. > > Stef > > >> On 23 May 2017, at 15:25, Tim Mackinnon <tim(a)testit.works <mailto:tim@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 <http://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 <mailto:stepharo.self@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 <mailto:phil@highoctane.be> <phil(a)highoctane.be <mailto:phil@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 <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 <mailto:stepharo.self@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 <mailto:emaringolo@gmail.com>> >>> > wrote: >>> >> >>> >> Correct link seems to be >>> >> >>> >> >>> >> http://files.pharo.org/books-pdfs/booklet-Glorp/2017-05-02-Glorp.spiral.pdf <http://files.pharo.org/books-pdfs/booklet-Glorp/2017-05-02-Glorp.spiral.pdf> >>> >> Esteban A. Maringolo >>> >> >>> >> >>> >> 2017-05-02 17:28 GMT-03:00 phil(a)highoctane.be <mailto:phil@highoctane.be> <phil(a)highoctane.be <mailto:phil@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 <mailto:stepharo.self@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/ <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 <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 >>> >> > >>> >> > >>> >> >>> > >>> >>> >> > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> > http://www.synectique.eu <http://www.synectique.eu/> / http://www.pharo.org <http://www.pharo.org/> > 03 59 35 87 52 > Assistant: Julie Jonas > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France >

1 0

FileTree/Iceberg and SSDs, change the file format
by Stephan Eggermont May 24, 2017

May 24, 2017

At the PharoDays I was painfully reminded that SSDs perform really badly when using small files. The Bloc tutorial used a github filetree repo and that has a lot of files. The whole folder is 116 MB in 16K files. Copying that amount of data should not be noticable, taking about a third of a second. With it being in so many files, it took more than half a minute, or a hundred times as long. That is too much overhead. How can we improve the file format in a way that keeps the cross-platform exchange advantages and a reasonable way to view diffs and propose small changes using the github web tools? Cuis uses a different format with git. How does that compare? What is used in Squeak? Stephan

7 14

60494 Red-pane-of-death when sources file missing
by Ben Coman May 23, 2017

May 23, 2017

We must be getting close to Pharo 6 Release. Due to missing PharoV60.soruces file, image 60494 get a red-pane-of-death in class pane. Even though the release would bypass this by including the file, we should be more robust to the missing sources file. Hopefully this fix can make it last minute into the release... https://pharo.fogbugz.com/f/cases/20074/Red-pane-of-death-when-sources-file… cheers -ben

2 1

Class syntax brainstorming
by Luc Fabresse May 23, 2017

May 23, 2017

Hi, Following Pharo Days, I brainstormed about some possible class definition syntaxes. What I have in mind: "basic mechanics, only THIS one in the image!" ClassDefinition new superclass: Object; "optional. If not specified, Object by default ;-)" name: #A; "optional and create an anonymous class if not specified" instVars: 'a b c'; traits: {TEquality}; package: 'Plop'; createClass. " this message sent might be hidden by the browser when accepting" "---------------" "Some IDEAS (but I did not find one that I really like) of scripting/shorter syntaxes that must ALWAYS end up calling the above basic mechanics at the end:" Class fromDefinition: [ :def | def name: #sub; instVars: 'w r g'; superclass: Object ]. Object subclass "<-- returns a subclass of Object but the problem is that the new class is muted each time and the class definition is not explicit" name: #A; ivs: 'a b c'; traits: { TEquality }. { #superclass -> Object. #name -> #sub. #instVars -> 'a b c' } asClass. { Object asSuperclass. #sub asClassName. 'a b c' asInstVars. 'c' asClassVar } asClass. "litteral approach" #( name A superclass Object instVars #(a b c) instVar d ) asClass #Luc

14 17

Re: [Pharo-dev] Class syntax brainstorming
by Luc Fabresse May 23, 2017

May 23, 2017

2017-05-22 15:06 GMT+02:00 Milan Vavra via Pharo-dev < pharo-dev(a)lists.pharo.org>: > > > ---------- Message transfÃ©rÃ© ---------- > From: Milan Vavra <vavra_milan(a)yahoo.com> > To: pharo-dev(a)lists.pharo.org > Cc: > Bcc: > Date: Mon, 22 May 2017 06:06:26 -0700 (PDT) > Subject: Re: Class syntax brainstorming > >ClassDefinition new > > superclass: Object; "optional. If not specified, Object by default > ;-)" > > name: #A; "optional and create an anonymous class if not specified" > > instVars: 'a b c'; > > traits: {TEquality}; > > package: 'Plop'; > > createClass. " this message sent might be hidden by the browser > when > accepting" > > > > I would like to suggest to consider replacing > instVars: 'a b c'; > > with > instVars: #( > b > a > c > ); > +1 ! > > That is, to replace the String with names separated by whitespace, by an > array of Symbols, one name per line. > > > This would make it possible to put comments right next to variable names > like this: > > instVars: #( > b "comment about b" > a "comment about a" > c "comment about c" > ); > > Which is similar to what can be done in other object oriented languages > like Java or C++. > > This would also make for nice diffs of changes to the class definition - > when put into git - when instance variables are added, removed or > renamed. > > instVars: #( > b > - a > + d > c > ); > > > Best Regards, > > Milan Vavra > > > > -- > View this message in context: http://forum.world.st/Class- > syntax-brainstorming-tp4947801p4947858.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > >

1 0

[pharo-project/pharo-core] ed847b: 60497
by GitHub May 23, 2017

May 23, 2017

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: ed847b82140bc72ef6cf1191fdd1c3e483651c85 https://github.com/pharo-project/pharo-core/commit/ed847b82140bc72ef6cf1191… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-05-23 (Tue, 23 May 2017) Changed paths: M BaselineOfIDE.package/BaselineOfIDE.class/instance/actions/additionalInitialization.st M ImportingResource-Help.package/ImportingResourceHelp.class/class/accessing/pages.st M ImportingResource-Help.package/ImportingResourceHelp.class/class/documentation/encodingAndDecoding.st A ImportingResource-Help.package/ImportingResourceHelp.class/class/documentation/encodingAndDecodingImage.st M ImportingResource-Help.package/ImportingResourceHelp.class/class/documentation/overview.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60496.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60497.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60496.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60497.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60497 20084 Highlight Message Send is not enabled by default in bootstrapped/reloaded image https://pharo.fogbugz.com/f/cases/20084 20072 Importing Resource Help needs improvement https://pharo.fogbugz.com/f/cases/20072 19809 Failing test: WeakAnnouncerTest>>#testNoDeadWeakSubscriptions https://pharo.fogbugz.com/f/cases/19809 http://files.pharo.org/image/60/60497.zip

1 0

[pharo-project/pharo-core]
by GitHub May 23, 2017

May 23, 2017

Branch: refs/tags/60497 Home: https://github.com/pharo-project/pharo-core

1 0