- Pharo-users - lists.pharo.org

Call for Spanish/ Portuguese and more subtitles for the PharoMooc

by Stephane Ducasse

Hi guys The Pharo is a wonderful vehicule to promote Pharo and we need your help to translate the subtitles to different languages. This year we will have english voices paid by Inria (thanks) but we cannot do everything and we need your help. https://github.com/SquareBracketAssociates/PharoMooc/tree/master/Subtitles Stef

Aug. 25, 2017

Morphic renderer for Pillar?

by H. Hirzel

Hello Stephane On 8/24/17, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: [...] > > This is good that there is Section 7 this in the doc. [1] We started to > build a simple Morphic renderer for Pillar. > We should continue. If someone wants to have fun. This would be nice > to have see it coming to live. I am interested in this. Where is the code? BTW if other people want to do a Pillar renderer for Bloc I have no problem with that..... :-; [...] Regards --Hannes [1] https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf…

Aug. 25, 2017

Re: [Pharo-users] [ANN] Pharo wiki , is here

by H. Hirzel

On 8/25/17, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > On Thu, Aug 24, 2017 at 11:32 PM Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > >> You have Netstyle/Workflow too. >> > > done > > "Why are you using markup documents to create the wiki when you could > use Github wiki itself? > > For portability?" > > good question. Yes for flexibility , another reason however is that Github > wiki is a separate repo and I did not want that because in the very back of > my head I am considering the option of creating software to allow access to > wiki from inside Pharo and I wanted to be all (content and code) in the > same repo. Its a very low priority for now. > > Also Github wiki is basically the same as I am doing with some extra format > (table of contents) , in my case I dont care because Github allows me to > define HTML templates that will format the wiki webpage and make it look a > a lot more polished that pharo wiki looks like. Generally there are some > cool stuff you can do with Markdown and Github , plus the fact that > markdown can embed HTML etc. +1 > There is also the option of Gitbook which has some nice features for > generating polished and well structured documentation. +1 > So I like to keep my options open. For now I am focusing 100% on content. +10

Aug. 25, 2017

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

by H. Hirzel

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. 25, 2017

Re: [Pharo-users] [Pillar] Installed the Pillar document preparation system into 6.1, how do I start using it?

by Tudor Girba

On Aug 25, 2017, at 8:53 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > > >> Am 24.08.2017 um 22:34 schrieb Stephane Ducasse <stepharo.self(a)gmail.com>: >> >> In Pharo 60 (and not in Pharo 50) I extracted the command line logic >> into a specific object so that we do not have to be bound to use the >> command line. You can have a look in the CLI package. >> >> This is good that there is Section 7 this in the doc. We started to >> build a simple Morphic renderer for Pillar. >> We should continue. If someone wants to have fun. This would be nice >> to have see it coming to live. >> > A morphic renderer? Wouldn't it be fun to do one for bloc? I think we should slowly collect some tools that use bloc in order to get the tension making it the "default" thingie. On its way :) Doru >> On my todo: I also want to use mustache inside Pharo and not >> generating files on the disk. >> > That should be doable by deleting some code. > > Norbert > >> Stef >> >> On Fri, Aug 18, 2017 at 10:08 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>> Exactly. >>> >>> Section 7 of >>> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >>> >>> has an example >>> >>> >>> | wiki | >>> wiki := '!My Document'. >>> PRPillarParser parse: wiki >>> >>> >>> Or >>> >>> PRPillarParser parse: (FileSystem workingDirectory / 'foo.pillar') >>> readStream >>> >>> >>> and then >>> >>> >>> PRHTMLWriter write: document >>> >>> >>> This put together gives >>> >>> PRHTMLWriter write: ( >>> PRPillarParser parse: (FileSystem workingDirectory / 'welcome.pillar') >>> ) >>> >>> >>> If I inspect the result of this expression I get the HTML string. >>> >>> Thank you Cyril. This is what I was looking for. >>> >>> --Hannes >>> >>> >>> >>> >>> On 8/18/17, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: >>>> On ven. 18 aoÃ»t 2017 at 21:43, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>>> >>>>> Thank you Cyril for the link to the tutorial. >>>>> >>>>> >>>>> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >>>>> >>>>> I see that Pillar is a command line tool. The welcome example taken >>>>> from this tutorial is: >>>>> >>>>> Pharo.exe Pillar.image pillar export --to=html >>>>> --outputFile=welcome welcome.pillar >>>>> >>>>> How can I run a command like this from within Pharo in a "playground" >>>>> (former workspace)? >>>>> >>>>> Later on I plan to construct a simple GUI with text boxes for Pillar >>>>> sources and have some buttons executing these commands. >>>>> >>>>> --Hannes >>>>> >>>>> >>>> >>>> I remember writing a part "Pillar from Pharo" in this doc. I'm not sure it >>>> is still up to date but you can try to check part 7 of the doc I sent. >>>> -- >>>> Cyril Ferlicot >>>> https://ferlicot.fr >>>> >>>> http://www.synectique.eu >>>> 2 rue Jacques PrÃ©vert 01, >>>> 59650 Villeneuve d'ascq France >>>> >>> > -- www.tudorgirba.com www.feenk.com "Problem solving efficiency grows with the abstractness level of problem understanding."

Aug. 25, 2017

Re: [Pharo-users] Minimizing an Application

by Dimitris Chloupis

I still dont know what opening has to do with transmitting, even when you do it remotely , a socket / websocket connection should be all you need. For me transmitting the entire image would be necessary only in the case you want to install it remotely and that remote location has no immediate access to the installation. On Fri, Aug 25, 2017 at 7:14 AM Ben Coman <btc(a)openinworld.com> wrote: > I understand that to mean effectively that you are "opening" the image > across the net - so eventually you need to whole image transmitted, but you > don't have to wait for the whole thing before you start running it. > cheers -ben > > > On Fri, Aug 25, 2017 at 2:00 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: > >> Indeed that can be a barrier but why you would want to transmit an >> entire image instead of portion of it using something like fuel files or >> other binary formats ? It would dramatically reduce the size of data you >> transmit. >> >> On Thu, Aug 24, 2017 at 8:10 PM Craig Latta <craig(a)blackpagedigital.com> >> wrote: >> >>> >>> > ...10mbs which is the size pharo image can be reduced to is nothing >>> > for todays TBs hard drives and GBs flash drives and online storage. >>> > Unless you do an embedded app and 10 mbs are huge for your limited >>> > storage. >>> >>> Or you want to minimize initial startup time, including the time it >>> takes to transmit the entire system over the net. >>> >>> >>> -C >>> >>> -- >>> Craig Latta >>> Black Page Digital >>> Amsterdam :: San Francisco >>> craig(a)blackpagedigital.com >>> voice through 2017-09-12: >>> + 1 510 833 5799 <(510)%20833-5799> (SMS ok) >>> +31 20 893 2796 <+31%2020%20893%202796> (no SMS) >>> >>> >>> >

Aug. 25, 2017

Re: [Pharo-users] [Pillar] Installed the Pillar document preparation system into 6.1, how do I start using it?

by Norbert Hartl

> Am 24.08.2017 um 22:34 schrieb Stephane Ducasse <stepharo.self(a)gmail.com>: > > In Pharo 60 (and not in Pharo 50) I extracted the command line logic > into a specific object so that we do not have to be bound to use the > command line. You can have a look in the CLI package. > > This is good that there is Section 7 this in the doc. We started to > build a simple Morphic renderer for Pillar. > We should continue. If someone wants to have fun. This would be nice > to have see it coming to live. > A morphic renderer? Wouldn't it be fun to do one for bloc? I think we should slowly collect some tools that use bloc in order to get the tension making it the "default" thingie. > On my todo: I also want to use mustache inside Pharo and not > generating files on the disk. > That should be doable by deleting some code. Norbert > Stef > > On Fri, Aug 18, 2017 at 10:08 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> Exactly. >> >> Section 7 of >> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >> >> has an example >> >> >> | wiki | >> wiki := '!My Document'. >> PRPillarParser parse: wiki >> >> >> Or >> >> PRPillarParser parse: (FileSystem workingDirectory / 'foo.pillar') >> readStream >> >> >> and then >> >> >> PRHTMLWriter write: document >> >> >> This put together gives >> >> PRHTMLWriter write: ( >> PRPillarParser parse: (FileSystem workingDirectory / 'welcome.pillar') >> ) >> >> >> If I inspect the result of this expression I get the HTML string. >> >> Thank you Cyril. This is what I was looking for. >> >> --Hannes >> >> >> >> >> On 8/18/17, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: >>> On ven. 18 aoÃ»t 2017 at 21:43, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>> >>>> Thank you Cyril for the link to the tutorial. >>>> >>>> >>>> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >>>> >>>> I see that Pillar is a command line tool. The welcome example taken >>>> from this tutorial is: >>>> >>>> Pharo.exe Pillar.image pillar export --to=html >>>> --outputFile=welcome welcome.pillar >>>> >>>> How can I run a command like this from within Pharo in a "playground" >>>> (former workspace)? >>>> >>>> Later on I plan to construct a simple GUI with text boxes for Pillar >>>> sources and have some buttons executing these commands. >>>> >>>> --Hannes >>>> >>>> >>> >>> I remember writing a part "Pillar from Pharo" in this doc. I'm not sure it >>> is still up to date but you can try to check part 7 of the doc I sent. >>> -- >>> Cyril Ferlicot >>> https://ferlicot.fr >>> >>> http://www.synectique.eu >>> 2 rue Jacques PrÃ©vert 01, >>> 59650 Villeneuve d'ascq France >>> >>

Aug. 25, 2017

Re: [Pharo-users] SmartTest - ESUG 2017 - Trailer

by Tudor Girba

The bar is getting higher :) Doru > On Aug 24, 2017, at 10:18 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > :) > Ready for the ESUG innovation award competition. > > > On Thu, Aug 24, 2017 at 6:49 PM, Dimitris Chloupis > <kilon.alios(a)gmail.com> wrote: >> lol by far the most funny pharo teaser I have watched and the tool looks >> extra useful , well done :) >> >> On Thu, Aug 24, 2017 at 6:33 PM Benoit Verhaeghe <benoit.verhaeghe(a)inria.fr> >> wrote: >>> >>> Hi everyone, >>> >>> I'm glad to present you the trailer of SmartTest for ESUG >>> https://www.youtube.com/watch?v=jAvfdN2z5-s >>> >>> BenoÃ®t Verhaeghe > -- www.tudorgirba.com www.feenk.com "No matter how many recipes we know, we still value a chef."

Aug. 25, 2017

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini

by john pfersich

I don't know if it matters, but on my Retina 5K, 27 inch, Late 2015 iMac, AMD Radeon R9 M395 wirh 2048 MB running MacOS 10.12.6 I don't have a problem resizing or maximizing Pharo 6.1. On Mon, Jul 31, 2017 at 6:28 AM, Ted F.A.van Gaalen <tedvga(a)gmail.com> wrote: > > > > Hi, I reverted to 5.0 because Pharo 6.0 and 6.1 64 bit hangs on > my Mac Mini with UDH 4K screen (may that has to do with?) > with its maiden image (at first start after download > when: I resize or go to full screen. Maybe VM problem? > my mac Mini metrics: > *Hardware Overview:* > > Model Name: Mac mini > Model Identifier: Macmini6,2 > Processor Name: Intel Core i7 > Processor Speed: 2,6 GHz > Number of Processors: 1 > Total Number of Cores: 4 > L2 Cache (per Core): 256 KB > L3 Cache: 6 MB > Memory: 4 GB > Boot ROM Version: MM61.0106.B1F > SMC Version (system): 2.8f0 > > maybe this problem was already reported, but could find it. > > > Kind Regards > TedvG > > > >

Aug. 25, 2017

Re: [Pharo-users] Object>>#name deprecated in Pharo 6 -- what do I need to do?

by Ben Coman

I don't have an Image to check, but I believe Object>>name just does "^self printString", so by default, in your application send #printString instead of #name. cheers -ben P.S. Perhaps this would be a good candidate for automated rewrite? On Thu, Aug 24, 2017 at 8:49 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > Hello > > In the last days there was a discussion that > > Object>>#name > > > should no longer be used. I did not follow the discussion in detail. > What was decided how #name should be replaced? > > What do I need to do if I get a deprecation warning [1]? > > > Thanks for the answer in advance > > Hannes > > > > > [1] > The method Object>>#name called from PPCMNode>>#gtTreeViewIn: has been > deprecated. > Implement your own domain representation of an object, or use > #asString or #printString instead. > > Select Proceed to continue, or close this window to cancel the operation. > >

Aug. 25, 2017