- Pharo-users - lists.pharo.org

Re: [Pharo-users] How to create a minimal image ?

by Stephane Ducasse

We are talking about **Pharo Core** and we will reduce it even more. Then you can load the UI. And no UI is not the very essence of Smalltalk. You can connect remotely to a live kernel and program it and this is still a live system. On Mon, Aug 28, 2017 at 1:33 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > for me Pharo and GUI go hand in hand, I cannot imagine Pharo without GUI. I > also despise the command line. Plus once you remove the GUI you kill the > very essence of Smalltalk. > > But if that is what you(you as all people who support this) like and need, > that's your choice and I respect that. > > Even back in the 80s when almost everything was command lines , I was > drooling over Amiga's 500 beautiful coloured GUIs. It started my fascination > with computer graphics and later 3d graphics and sound. > > So me and the GUI are very old friends and we go hand in hand :) > > Of course I understand if we want to go super minimal the GUI has to go > together with many other things that make Pharo what it is. But I dont care > for such extremes. I just wanted to reduce the fat. > > On Mon, Aug 28, 2017 at 2:24 PM Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: >> >> What do you expect from such minimal image? Because we can produce several >> intermediate steps on the way to the standard full Pharo image >> (BaselineOfMorphicCore, BaselineOfMorphic, BaselineOfUI, >> BaselineOfBasicTools...) >> >> -- Pavel >> >> 2017-08-28 13:17 GMT+02:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: >>> >>> oh , then its not what I am thinking as minimal image. Pity, oh well , I >>> will wait for bootstrap to mature then :) >>> >>> On Mon, Aug 28, 2017 at 2:09 PM Pavel Krivanek <pavel.krivanek(a)gmail.com> >>> wrote: >>>> >>>> The minimal image is headless image without any GUI. It is useless to >>>> try to open it this way. >>>> >>>> -- Pavel >>>> >>>> 2017-08-28 13:03 GMT+02:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: >>>>> >>>>> hmm does not work for me, it open the icon of pharo on macos sierra >>>>> dock and it stays there doing nothing >>>>> right clicking on it and choosing quit does nothing, so I am have to >>>>> use force quit to make it close >>>>> >>>>> I have downloaded pharo 6.1 from the website, default download, 32 bit, >>>>> minimal 32 bit image. I drag and drop image on top of pharo. >>>>> >>>>> On Mon, Aug 28, 2017 at 10:29 AM Pavel Krivanek >>>>> <pavel.krivanek(a)gmail.com> wrote: >>>>>> >>>>>> 2017-08-26 19:31 GMT+02:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: >>>>>>> >>>>>>> I remember that the website used to link to a minimal image download >>>>>>> but it does not seem there is one anymore >>>>>>> >>>>>>> Is still minimal image maintained ? >>>>>> >>>>>> >>>>>> yes, as part of the bootstrap process >>>>>> >>>>>>> >>>>>>> Are there ways to make a image minimal ? >>>>>> >>>>>> >>>>>> it is created in bootstrap/scripts/build.sh under name >>>>>> Pharo7.0-metacello-* and saved on files.pharo.org as >>>>>> http://files.pharo.org/image/70/latest-minimal-32.zip or >>>>>> http://files.pharo.org/image/70/latest-minimal-64.zip >>>>>> >>>>>> So you do not need to do it by yourself. >>>>>> >>>>>> -- Pavel >>>> >>>> >> >

Aug. 31, 2017

Re: [Pharo-users] How to create a minimal image ?

by Stephane Ducasse

If you remove AST you will not get the compiler working at all. On Mon, Aug 28, 2017 at 1:43 PM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > Hi Pavel, > > Can you show how to produce an image without the following packages? > > Tests > Spotter > Glamour/GT > Metacello > AST/Refactoring > > Cheers, > > HernÃ¡n > > > 2017-08-28 8:24 GMT-03:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: >> What do you expect from such minimal image? Because we can produce several >> intermediate steps on the way to the standard full Pharo image >> (BaselineOfMorphicCore, BaselineOfMorphic, BaselineOfUI, >> BaselineOfBasicTools...) >> >> -- Pavel >> >> 2017-08-28 13:17 GMT+02:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: >>> >>> oh , then its not what I am thinking as minimal image. Pity, oh well , I >>> will wait for bootstrap to mature then :) >>> >>> On Mon, Aug 28, 2017 at 2:09 PM Pavel Krivanek <pavel.krivanek(a)gmail.com> >>> wrote: >>>> >>>> The minimal image is headless image without any GUI. It is useless to try >>>> to open it this way. >>>> >>>> -- Pavel >>>> >>>> 2017-08-28 13:03 GMT+02:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: >>>>> >>>>> hmm does not work for me, it open the icon of pharo on macos sierra dock >>>>> and it stays there doing nothing >>>>> right clicking on it and choosing quit does nothing, so I am have to use >>>>> force quit to make it close >>>>> >>>>> I have downloaded pharo 6.1 from the website, default download, 32 bit, >>>>> minimal 32 bit image. I drag and drop image on top of pharo. >>>>> >>>>> On Mon, Aug 28, 2017 at 10:29 AM Pavel Krivanek >>>>> <pavel.krivanek(a)gmail.com> wrote: >>>>>> >>>>>> 2017-08-26 19:31 GMT+02:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: >>>>>>> >>>>>>> I remember that the website used to link to a minimal image download >>>>>>> but it does not seem there is one anymore >>>>>>> >>>>>>> Is still minimal image maintained ? >>>>>> >>>>>> >>>>>> yes, as part of the bootstrap process >>>>>> >>>>>>> >>>>>>> Are there ways to make a image minimal ? >>>>>> >>>>>> >>>>>> it is created in bootstrap/scripts/build.sh under name >>>>>> Pharo7.0-metacello-* and saved on files.pharo.org as >>>>>> http://files.pharo.org/image/70/latest-minimal-32.zip or >>>>>> http://files.pharo.org/image/70/latest-minimal-64.zip >>>>>> >>>>>> So you do not need to do it by yourself. >>>>>> >>>>>> -- Pavel >>>> >>>> >> >

Aug. 31, 2017

Re: [Pharo-users] Code mystery

by Stephane Ducasse

Can you open a bug entry? I can tell you that we clean a lot but human activity will always leads to glitches. On Tue, Aug 29, 2017 at 1:23 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > You are not going crazy that's an ugly method. Probably the author intended > to use dir and the forgot about it and instead hard coded the dir path > inside a class method. A mistake that can happen to anyone. > > The method will have to be updated anyway because name is to be removed, so > it won't work. > > As always too much code too few people. If you think that's bad embrace > yourself if you try to read Morphic code. Huge suffering for me when I tried > to learn how the task bar works and apparently using it wrong it freezes the > image. > > Tons of Pharo code needs a clean but needs also a lot more people. > On Tue, 29 Aug 2017 at 01:52, PBKResearch <peter(a)pbkresearch.co.uk> wrote: >> >> Hello All >> >> >> >> Following the discussion on dark mode, I was browsing the code on themes >> (in Moose 6.1 = Pharo 6.0, Latest update: #60486). In Class ThemeIcons, I >> found this method: >> >> >> >> downloadTo: dir >> >> | zipArchive | >> >> >> >> zipArchive := self class destinationPath / (self name, >> '.zip'). >> >> zipArchive exists >> >> ifFalse: [ >> >> ZnClient new >> >> url: self url; >> >> downloadTo: >> zipArchive ]. >> >> >> >> ^ zipArchive >> >> >> >> The mystery is that the argument dir is not referred to anywhere in the >> code. It probably works, because the only invocation of the method is from >> ThemeIcons>>downloadFromUrl, which sets the argument from self class >> destinationPath, and the code above recreates this as the path to >> zipArchive. >> >> >> >> I thought I understood Smalltalk coding fairly well, but this really >> puzzles me. Why would anyone code like this? Shouldnât it be picked up by a >> code critic? Or am I going crazy? >> >> >> >> Any help gratefully received >> >> >> >> Peter Kenny

Aug. 31, 2017

Re: [Pharo-users] Where do I find a Pillar syntax summary?

by Stephane Ducasse

All the pharo books I produced are in github/SquareBracketAssociates and the pdf are on books.pharo.org Now I made sure that the bintray produces pdf so that people can see the pdf once they edit commit the file On Mon, Aug 28, 2017 at 1:29 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > Found the Pillar chapter of the Pharo enterprise book ("A web > perspective") by following the link on the wiki > > https://github.com/pharo-project/pharo/blob/master/wiki/contents/projects.m… > > then > > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… > > Then https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… > > So the information is somewhat hidden but available and only the link > from the Pharo books website is broken..... > > > On 8/28/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> P.S. Important Pillar links I have collected last week >> >> https://github.com/pharo-project/pharo/blob/master/wiki/contents/projects.m… >> >> Includes this one >> http://pillarhub.pharocloud.com/hub/pillarhub/pillarcheatsheet >> Alistair writes it is fine in Pharo 6 for what he is using it for. >> >> In particular I am interested in adding pictures which are within the >> Pharo image. >> >> On 8/28/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>> Stephane >>> >>> I went to the Pharo book web site, >>> >>> Enterprise Pharo - a web perspective >>> Enterprise Pharo is the third volume of the series. >>> >>> This link >>> >>> http://files.pharo.org/books/enterprise-pharo/ >>> >>> and clicked on 'Pillar' >>> >>> and for >>> >>> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >>> >>> got HTTP ERROR 404 >>> >>> I think you are currently updating the book and that there are also PDFs. >>> >>> How can I get at a recent version? Integration server? Where? >>> >>> --Hannes >>> >>> >>> >>> On 8/26/17, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>>> the most up to date description is in the web perspective book and not >>>> much changed since then. >>>> We are picky when it is about the changing the syntax so it nearly did >>>> not change. >>>> >>>> Stef >>>> >>>> On Fri, Aug 25, 2017 at 10:55 AM, H. Hirzel <hannes.hirzel(a)gmail.com> >>>> wrote: >>>>> At the moment my interest is to have a description of all the Pillar >>>>> syntax features Pharo 5 and 6 supports. >>>>> >>>>> a) in an example document >>>>> b) as a list >>>>> >>>>> As for Pillar syntax versions: >>>>> >>>>> I can imagine that there have been changes in the past. I just don't >>>>> know. >>>>> And there might be changes in the future. So a version indication is >>>>> helpful even if it just says that Pharo 6 supports the same Pillar >>>>> version as it was in Pharo x (x = 2,3,4,5 ?). >>>>> >>>>> On 8/24/17, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>>>>> Good suggestion. >>>>>> Now I have no time for pillar per se. Now if you do it I will add it >>>>>> to pillar without hesitation. >>>>>> Tomorrow we will >>>>>> use bintray for all the projects to save the pdf (booklet, books). >>>>>> migrate the mooc to the makefile generator developed by luc. >>>>>> make sure that it works for Pillar 50 and 60. >>>>>> migrate other pillar projects to use the same. >>>>>> >>>>>> BTW we do not really want to have multiple version of the syntax. >>>>>> For example Pillar 50 and 60 are the same from a syntax point of view. >>>>>> >>>>>> On Thu, Aug 24, 2017 at 11:24 AM, H. Hirzel <hannes.hirzel(a)gmail.com> >>>>>> wrote: >>>>>>> Alistair, >>>>>>> >>>>>>> Thank you for the link to the Pillar syntax summary >>>>>>> >>>>>>> http://pillarhub.pharocloud.com/hub/pillarhub/pillarcheatsheet >>>>>>> >>>>>>> and the confirmation that the constructs there work in Pharo 6 & 7 >>>>>>> for >>>>>>> basic cases. This is fine for me at the moment. >>>>>>> >>>>>>> >>>>>>> Stephan D >>>>>>> Thanks for being ready to check the full feature support in Pillar. >>>>>>> >>>>>>> A suggestion: >>>>>>> A new style sheet could come as well together with a test document >>>>>>> (with version indication included) for the Pillar parser. >>>>>>> >>>>>>> Then it is straightforward to determine if a particular Pillar >>>>>>> installation supports a particular Pillar markup version. >>>>>>> >>>>>>> The Pillar-Tests-PetitPillar package tests individual features but >>>>>>> not >>>>>>> all in one go. If we have a test case which tests all features in one >>>>>>> go it has a triple function: >>>>>>> 1) It is a syntax summary of all features. >>>>>>> 2) It serves as a living documentation. >>>>>>> 3) It helps to determine if a particular pillar installation in an >>>>>>> image supports a particular Pillar version. >>>>>>> >>>>>>> --Hannes >>>>>>> >>>>>>> On 8/23/17, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>>>>>>> +Handling all the cases: summing a die/die handle with a die/die >>>>>>>> handle >>>>>>>> .>file://figures/DieDoubleDispatchFull.pdf|width=70|label=figDieDoubleDispatchFull+ >>>>>>>> >>>>>>>> See Figure *@figDieDoubleDispatchFull* for internal ref is missing. >>>>>>>> >>>>>>>> Two Column is missing. I do not know it works in Latex. >>>>>>>> >>>>>>>> I will try to create one a new style sheet. >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Aug 23, 2017 at 9:46 PM, Alistair Grant >>>>>>>> <akgrant0710(a)gmail.com> >>>>>>>> wrote: >>>>>>>>> On Wed, Aug 23, 2017 at 09:11:47PM +0200, H. Hirzel wrote: >>>>>>>>>> Thanks, it is useful. >>>>>>>>>> Date is 24 June 2014. >>>>>>>>>> Not sure if it is the latest version for what I have now in Pharo >>>>>>>>>> 6. >>>>>>>>>> >>>>>>>>>> --Hannes >>>>>>>>> >>>>>>>>> True, but it only covers the basic text mark-up and I don't think >>>>>>>>> that >>>>>>>>> has changed recently. Anyway, I haven't found anything wrong with >>>>>>>>> it >>>>>>>>> in >>>>>>>>> Pharo 6 & 7 (admittedly, with only basic pillar usage). >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> Alistair >>>>>>>>> >>>>>>>>> >>>>>>>>>> On 8/23/17, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>>>>>>>>> > How about: >>>>>>>>>> > >>>>>>>>>> > http://pillarhub.pharocloud.com/hub/pillarhub/pillarcheatsheet >>>>>>>>>> > >>>>>>>>>> > Cheers, >>>>>>>>>> > Alistair >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>> >> >

Aug. 31, 2017

Re: [Pharo-users] CodeImporter. 256 literals limit

by Andreas Sunardi

Esteban, I'm happy to report this package works for me, in my RH/CentOS 6 environment. I have to do a bit more since I have to install it in a network path (can't install in each server). If there's a download option instead of an rpm, such as that in Pharo 5 download website, that would be great. But I don't want to complain about it. The response and support from this community has been very impressive and I'm very grateful for it. Thank you very much! -- Andreas On Wed, Aug 30, 2017 at 2:02 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > you can try the new (still experimental) packaging for Pharo: > > CentOS 6.8: > > # Add the repo > $ yum-config-manager --add-repo http://download.opensuse.org/ > repositories/devel:/languages:/pharo:/latest/CentOS_6/devel: > languages:pharo:latest.repo > > # Install 32bit packages (with X11 dependency for *-ui or not) > > $ yum install pharo6-32-ui.i686 or pharo6-32.i386 > > # Install 64bit packages > > $ yum install pharo6-64-ui.x86_64 pharo6-64.x86_64 > > that will install correct vm for your distribution. > > cheers, > Esteban > > > > On 29 Aug 2017, at 18:58, Andreas Sunardi <a.sunardi(a)gmail.com> wrote: > > Point well taken. Unfortunately, I'm not in charge of the infrastructure. > I don't know if my experience is typical or not, but it's difficult for IT > to find a period to disrupt engineering projects, potentially breaking > tools, without drawing fire from engineering :) > > > On Tue, Aug 29, 2017 at 8:45 AM, Richard Sargent <richard.sargent@ > gemtalksystems.com> wrote: > >> my work environment is using RedHat6/CentOS6 with glibc 2.12 >>> >> >> That's seven years of unpatched security vulnerabilities! Are you sure >> you really want to stay at such great risk? >> >> >> On Tue, Aug 29, 2017 at 8:30 AM, Andreas Sunardi <a.sunardi(a)gmail.com> >> wrote: >> >>> That sounds good. Unfortunately for me, my work environment is using >>> RedHat6/CentOS6 with glibc 2.12. Is there Pharo6 with glibc < 2.15 support. >>> Or is there a way for me to build that myself? >>> >>> It's quite a departure to change my DSL into defining multiple methods. >>> But that's my own problem. >>> >>> I'm happy to hear Pharo 6 can support a lot more literals. I tested my >>> code on Pharo 6 (on my Windows box) and it works. I see SistaV1 compiler in >>> Pharo 5 setting, but that causes Pharo to crash. >>> >>> Thank you guys for your answers. I think I have the information I need >>> to make decision. But if there is a way to get Pharo 6 that works with >>> glibc < 2.15, please let me know. >>> >>> Thank you >>> -- >>> Andreas >>> >>> On Tue, Aug 29, 2017 at 12:34 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> >>> wrote: >>> >>>> Hi, >>>> >>>> If your tool works in Pharo 6, you can use the other bytecode set which >>>> supports up to 32k literals. To do so, go to: >>>> World Menu > Settings > Compiler > Encoder >>>> and pick SistaV1 instead of V3PlusClosures >>>> Try to load your code. The default Pharo 6 VM supports both bytecode >>>> sets. >>>> >>>> Alternatively you need to split your methods with many literals in >>>> multiple methods with less literals, which is usually quite tricky to do >>>> right. >>>> >>>> On Tue, Aug 29, 2017 at 4:52 AM, Andreas Sunardi <a.sunardi(a)gmail.com> >>>> wrote: >>>> >>>>> I have written a tool (Pharo5) where user gives an input file to it, >>>>> where the content is a smalltalk code, a DSL. I used a subclass of >>>>> CodeImporter class to evaluate this input file. >>>>> >>>>> Recently my user used an input file where it hit the 256 literal limit >>>>> (total of unique string, number, method name, etc), down in >>>>> OpalEncoderForV3PlusClosures >> genPushLiteral:. The number seems to be >>>>> hard coded and related to byte code generator, not something I can simply >>>>> increase. I wasn't aware of this limitation. >>>>> >>>>> Before I overhaul my tool, I thought I should ask. Is there another >>>>> alternative to evaluate a smalltalk file/script? The file is small, 27k, >>>>> but the number of unique literals in it is > 256. Is it possible at all, >>>>> seeing that the limit is related to byte code generator. >>>>> >>>>> Thank you in advance >>>>> -- >>>>> Andreas Sunardi >>>>> >>>> >>>> >>> >> > >

Aug. 31, 2017

Re: [Pharo-users] #parseMethod:onError: isn't as obvious as expected - is it me?

by Marcus Denker

> On 31 Aug 2017, at 19:07, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > On Wed, Aug 30, 2017 at 9:50 PM, Tim Mackinnon <tim(a)testit.works> wrote: >> Iâm looking for some feedback on the usage of RBParser>>#parseMethod:onError:. >> >> I am looking at ways of improving the way we edit code - and making things work (as least for me - but maybe for everyone) a bit more like IntelliJ where they have some great code operations and very good keyboard support. We are certainly close, but at times feel a bit clumsy - which is a shame as we have far better infrastructure to support equivalent features. So I thought I would have a go. > > Excellent!!! > > >> Anyway - step one (which I think Iâve come close on), was to teach senders/implementors to look at the AST so you donât have to highlight exactly what you want to search on - instead it can infer from your cursorâ¦ however my next step was to improve how we can select code to ease refactoring, bracketing etcâ¦ > > Yes but we have to handle broken code then. > Did you check how smart suggestions did it for code that compiled? > I looked some weeks ago and made some notes what to doâ¦ but I fear this has to wait for next week, there is no way that I can do anything till ESUGâ¦ Marcus

Aug. 31, 2017

Re: [Pharo-users] #parseMethod:onError: isn't as obvious as expected - is it me?

by Stephane Ducasse

On Wed, Aug 30, 2017 at 9:50 PM, Tim Mackinnon <tim(a)testit.works> wrote: > Iâm looking for some feedback on the usage of RBParser>>#parseMethod:onError:. > > I am looking at ways of improving the way we edit code - and making things work (as least for me - but maybe for everyone) a bit more like IntelliJ where they have some great code operations and very good keyboard support. We are certainly close, but at times feel a bit clumsy - which is a shame as we have far better infrastructure to support equivalent features. So I thought I would have a go. Excellent!!! > Anyway - step one (which I think Iâve come close on), was to teach senders/implementors to look at the AST so you donât have to highlight exactly what you want to search on - instead it can infer from your cursorâ¦ however my next step was to improve how we can select code to ease refactoring, bracketing etcâ¦ Yes but we have to handle broken code then. Did you check how smart suggestions did it for code that compiled? > > So this is where Iâve hit a few issues which strike me as confusing (and I will freely admit that Iâm not a mega compiler, parser guy - but Iâd love to beâ¦). > > The following code blows up strangely - and I think its very confusingâ¦ as it turns out that #parseMethod:onError: doesnât work like I would expect (and this is where Iâm after feedback). It seems that the onError block doesât actually exit parsing - it takes the result and then keeps running with something in an intermediate state - thus below, when I try to parse with a subset of the code (and maybe this is a naive approach to handle the case when you start typing code in the middle of a complete method, but want to parse it before youâve entered a final â.â or â;â) - you actually end up with an AST that is using all of the source code because the result of the error block is then applied inside the executing method. > > I find this very confusing? There are no comments in this code, and for me the convention of onError: is to execute in isolation unless there is a parameter that the error block can interact with. Iâm wondering if those with more knowledge agree - or if it is my naivetÃ©? > > This was my original code (and yes it needs refactoring a bit) - but anyway: > > bestNodeInTextAreaOnError: aBlock > "Find the best node in the editor text area at the current pointer location" > > | ast start stop node source | > > start := self textArea startIndex. > stop := self textArea stopIndex. > > source := self textArea string trimRight. > > ast := RBParser parseMethod: source onError: [ > RBParser parseExpression: source onError: [ > source := (source truncateTo: stop) trimRight. > > RBParser parseMethod: source onError: [ > RBParser parseExpression: source onError: aBlock ]]]. > > stop > source size ifTrue: [ > start := stop := source size]. > > node := ast bestNodeFor: (start to: stop). > > node ifNil: aBlock. > > ^node > > But this doesnât work, as âastâ is incorrect when it parses truncated source. To work around what Iâm seeing I have to instead extract the ast assignment to another method that looks as follows - but to me it seems very unexpected to have the explicit ^ statements? > > agressivelyParse: source at: loc > "Find the best node in the editor text area at the current pointer location" > > ^RBParser parseMethod: source onError: [ > ^RBParser parseExpression: source onError: [ | reducedSrc | > reducedSrc := (source truncateTo: loc) trimRight. > > ^RBParser parseMethod: reducedSrc onError: [ > ^RBParser parseExpression: reducedSrc onError: [^nil]]]]. > > This forces the ast to be exactly what I would expect - but Iâm wondering if I am missing something obvious? > > Tim

Aug. 31, 2017

Re: [Pharo-users] [Pillar] Pillar source code of ESUG 2015 presentation? Presentations done with Pillar?

by H. Hirzel

Thank you, Stef https://github.com/SquareBracketAssociates/PharoMooc/tree/master/support/be… On 8/31/17, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hannes > > the beamer templates manage the first page. > Have a look in the support/ folder. > > Stef > > On Thu, Aug 31, 2017 at 4:12 PM, Cyril Ferlicot > <cyril.ferlicot(a)gmail.com> wrote: >> There is some doc in the section 3.12 of the documentation >> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >> >> I don't know if everything is here but there is some doc at least :) >> >> On Thu, Aug 31, 2017 at 4:08 PM, H. Hirzel <hannes.hirzel(a)gmail.com> >> wrote: >>> On 8/31/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>>> A useful file which shows what is possible to do slides >>>> >>>> https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slides/1-T… >>> >>> Correction: >>> This file shows how to do slides with Pillar >>> >>> https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slides/1-T… >>> >>> My questions thus are specifically: >>> >>> 1. How do I do a title slide? >>> 2. What do I do inside the ${....}$ . >>> Where do I find documentation on the options for these $ enclosed >>> commands? >>> >>> --Hannes >>> >> >> >> >> -- >> Cyril Ferlicot >> https://ferlicot.fr >> >> http://www.synectique.eu >> 2 rue Jacques PrÃ©vert 01, >> 59650 Villeneuve d'ascq France >> > >

Aug. 31, 2017

Re: [Pharo-users] new chapter on double dispatch for new book :)

by Stephane Ducasse

Yes I like this book. Now what I suggest is to try on a separate class hierarchy because breaking + can blow up your image. On Tue, Aug 29, 2017 at 10:28 PM, Yves Lenfant <lenfantyv(a)wanadoo.fr> wrote: > Thanks for your quick reply. > OK, your chapter highligths the polymorpism not the inheritance. > > So I will try to change the Number methods in a dedicated image... > > Anyway, in the book InsideSmalltalk P. 250, it explains that (I quote) > > I suppose the "Number" mecanism is more complex than I can expect. > > Yves > > > > -- > View this message in context: http://forum.world.st/new-chapter-on-double-dispatch-for-new-book-tp4963645… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Aug. 31, 2017

Re: [Pharo-users] [Pillar] Pillar source code of ESUG 2015 presentation? Presentations done with Pillar?

by Stephane Ducasse

Hannes the beamer templates manage the first page. Have a look in the support/ folder. Stef On Thu, Aug 31, 2017 at 4:12 PM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > There is some doc in the section 3.12 of the documentation > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… > > I don't know if everything is here but there is some doc at least :) > > On Thu, Aug 31, 2017 at 4:08 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> On 8/31/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>> A useful file which shows what is possible to do slides >>> >>> https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slides/1-T… >> >> Correction: >> This file shows how to do slides with Pillar >> >> https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slides/1-T… >> >> My questions thus are specifically: >> >> 1. How do I do a title slide? >> 2. What do I do inside the ${....}$ . >> Where do I find documentation on the options for these $ enclosed commands? >> >> --Hannes >> > > > > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France >

Aug. 31, 2017