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

Re: [Pharo-dev] Pharo booklet collection

by Damien Pollet

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/.trav… 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 23, 2017

Re: [Pharo-dev] 60494 Red-pane-of-death when sources file missing

by Eliot Miranda

Hi Ben, On May 21, 2017, at 9:01 AM, Ben Coman <btc(a)openinworld.com> wrote: 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-missing cheers -ben I don't know if this is related but an image Max Leske provided me to look at ImageSegments I noticed that start up without a sources file took of the order of a minute, whereas startup with a source file was the usual snappy affair. Max's image is Pharo6.0 [Latest update: #60482]. I've attached the PharoDebug.log

May 23, 2017

Re: [Pharo-dev] FileTree/Iceberg and SSDs, change the file format

by Jan Vrany

Hi, > > Is it possible to build a file responder right into Pharo and > > expose packages through WebDAV or FUSE or sshfs service? Then the > > contents can go directly from RAM (pharo) to RAM (repo server or > > git) without going through slow disk filesystem. > > Yes it's possible and really interesting for lots of reasons.Â Â Not > sure why no one is exploring this avenue. I did explored this path with FUSE ages age (~10 yeas, IIRC) and, if my memory is not failing me, was possible but turned out to be useless in practice. The problem was that the call to fuse entered a kernel and sit there until there was a FS request at which point it called back my smalltalk. This means smalltalk was unresponsive most of the time. Besides, one needed superuser priviledges and all that stuff. Things may be different these days. Some another 10 years before me Claus did exactly the same thing using NFSv3, being able to "mount" running Smalltalk image. Last time I tried it still worked. I was never used for anything practical, as far as I can recall. Jan > > > > Regards .. Subbu > > > >

May 23, 2017

Re: [Pharo-dev] FileTree/Iceberg and SSDs, change the file format

by Eliot Miranda

Hi Subbu, > On May 21, 2017, at 11:26 PM, K K Subbu <kksubbu.ml(a)gmail.com> wrote: > >> On Sunday 21 May 2017 11:34 PM, Dale Henrichs wrote: >> As part of his work on Cypress 2.0 Martin McClure is planning on >> supporting a file per class disk format in addition to the file per >> method format and possibly a file per package format. >> >> I'm not sure whether Martin is at the point where he is ready to share >> his plans, but this is a problem that is being worked on and when Martin >> is ready for feedback he'll publish his spec. > > Is it possible to build a file responder right into Pharo and expose packages through WebDAV or FUSE or sshfs service? Then the contents can go directly from RAM (pharo) to RAM (repo server or git) without going through slow disk filesystem. I should say that there's a poor implementation ration for Squeak; poor because it uses the C binding. The right way is to go directly over sockets. This provides efficiency, flexibility and some degree of concurrency; all of which are lacking when programming against the C binding. One could do so much with this other than merely an elegant interface to a vcs. As my friend David Simmons points out, the major benefit of Docker is being able to configure (and hence version) an os virtual machine through the host file system, instead of having to start up the os virtual machine and configure within it and its own file system. A FUSE interface for Pharo/Squeak/Cuis (I'm going to start calling this triad Cusp, Cuis union Squeak & Pharo) would allow non-Smalltalker dev ops people to configure (or monitor, or...) a Cusp image as if it were done familiar native tool. > > Regards .. Subbu >

May 23, 2017

Re: [Pharo-dev] FileTree/Iceberg and SSDs, change the file format

by Eliot Miranda

Hi Subbu, > On May 21, 2017, at 11:26 PM, K K Subbu <kksubbu.ml(a)gmail.com> wrote: > >> On Sunday 21 May 2017 11:34 PM, Dale Henrichs wrote: >> As part of his work on Cypress 2.0 Martin McClure is planning on >> supporting a file per class disk format in addition to the file per >> method format and possibly a file per package format. >> >> I'm not sure whether Martin is at the point where he is ready to share >> his plans, but this is a problem that is being worked on and when Martin >> is ready for feedback he'll publish his spec. > > Is it possible to build a file responder right into Pharo and expose packages through WebDAV or FUSE or sshfs service? Then the contents can go directly from RAM (pharo) to RAM (repo server or git) without going through slow disk filesystem. Yes it's possible and really interesting for lots of reasons. Not sure why no one is exploring this avenue. > > Regards .. Subbu >

May 23, 2017

Re: [Pharo-dev] Class syntax brainstorming

by Luc Fabresse

2017-05-22 16:26 GMT+02:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Honestly, I do not like that much having a more declarative (less > Smalltalksish) definition. In fact, one of the things I was always proud of > showing to Smalltalk newcomers, that when they created a class, all they > were doing was a "DoIt" to tell the superclass to create the new subclass. > And then showing how they could copy and paste that into a workspace and > DoIt. Or Debug it. > > So..if it were for me, I would keep a Smalltalk syntax with a plain > message send. Sure, a builder kind of API is better to me, like Luc > proposes. Also, I do prefer too the #createAndInstall kind of message so > that we can have a flavour of #createClass that only creates the class but > doesn't install it into the system. > good point! > > Cheers, > > On Mon, May 22, 2017 at 10:48 AM, Ben Coman <btc(a)openinworld.com> wrote: > >> >> >> On Mon, May 22, 2017 at 3:25 PM, Luc Fabresse <luc.fabresse(a)gmail.com> >> wrote: >> >>> 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 >>> >> >> (btw, I assume you mean mutated.) >> >> >>> each time and the class definition is not explicit" >>> name: #A; >>> ivs: 'a b c'; >>> traits: { TEquality }. >>> >> >> What about... >> >> Object subclass: [ :def | def >> name: 'MyClass' ; "optional and create an anonymous class if not >> specified" >> instanceVariables: 'a b c' ; >> classVariables: 'M N O'; >> classInstanceVariables: 'x y z' ; >> traits: {TEquality} ; >> package: 'Plop']. >> >> Object>>subclass: builderBlock >> ^ (builderBlock value: ClassDefinition new) createClass >> >> or similar to Guille's declarative proposal... >> >> Object subclass: { >> name: 'Myclass', >> a: InstVar, >> b: InstVar, >> c: InstVar >> } >> >> >> cheers -ben >> > > > > -- > Mariano > http://marianopeck.wordpress.com >

May 23, 2017

Re: [Pharo-dev] Class syntax brainstorming

by Luc Fabresse

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

May 23, 2017

[pharo-project/pharo-core] ed847b: 60497

by GitHub

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

May 23, 2017

[pharo-project/pharo-core]

by GitHub

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

May 23, 2017

Re: [Pharo-dev] FileTree/Iceberg and SSDs, change the file format

by Dale Henrichs

Stephan, Out of curiosity. Why are you copying the git repo? In my normal usage, I clone a git repository on disk and then share that repository amongst all of the image/stones on that machine ... The upshot is that I almost never copy the repo. I use push to publish changes to common git repo and pull to update the local disk copy and those commands update only the files that have changed ... That isn't to say the I NEVER copy a git repo, but it is not something that I do frequently ... Dale On 5/21/17 8:25 AM, Stephan Eggermont wrote: > 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 >

May 23, 2017