March 2018 - Pharo-users - lists.pharo.org

GTInspector globally configuring visible tags

by Peter UhnÃ¡k

Hi, is it possible to globally configure GTInspector to show only certain tags (<gtInspectorTag: ...>) ? Thanks, Peter

March 1, 2018

Re: [Pharo-users] Ever growing image

by Hilaire

ok, thanks for the clarification. It is not really a concern to built and shrink DrGeo image. Hilaire Le 01/03/2018 Ã 16:26, Stephane Ducasse a Ã©critÂ : > We have a bug in the GC but this one is siply crashing the image not > growing it. > I think that what esteban is mentioning is that your code or some > parts of Pharo may be > leaking memory. We got some experience with GT for example. -- Dr. Geo http://drgeo.eu

March 1, 2018

Re: [Pharo-users] Ever growing image

by Stephane Ducasse

We have a bug in the GC but this one is siply crashing the image not growing it. I think that what esteban is mentioning is that your code or some parts of Pharo may be leaking memory. We got some experience with GT for example. Stef On Thu, Mar 1, 2018 at 4:05 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > Le 01/03/2018 Ã 16:03, Esteban Lorenzano a Ã©crit : >> >> but the âeasy leakingâ syndrom, yes;) > > ah? > > > -- > Dr. Geo > http://drgeo.eu > > >

March 1, 2018

Re: [Pharo-users] Ever growing image

by Hilaire

Le 01/03/2018 Ã 16:03, Esteban Lorenzano a Ã©critÂ : > but the âeasy leakingâ syndrom, yes;) Â ah? -- Dr. Geo http://drgeo.eu

March 1, 2018

Re: [Pharo-users] Ever growing image

by Esteban Lorenzano

> On 1 Mar 2018, at 15:55, Hilaire <hilaire(a)drgeo.eu> wrote: > > Hi, > > Does the current 64bits VM suffers of the ever growing image syndrom? no. but the âeasy leakingâ syndrom, yes ;) Esteban > > Thanks > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > >

March 1, 2018

Ever growing image

by Hilaire

Hi, Does the current 64bits VM suffers of the ever growing image syndrom? Thanks Hilaire -- Dr. Geo http://drgeo.eu

March 1, 2018

Re: [Pharo-users] Exporting Pillar docs (Pillar7)

by Stephane Ducasse

In fact in Pillar 6/7 you can take template or create your own the variables are mustache variables. So this basically means that you inject the latex generated by Pillar into the latex document template you want. Have a look at the template folder. On Tue, Feb 27, 2018 at 2:42 PM, Arturo Zambrano <arturo.zambrano(a)gmail.com> wrote: > Thanks for your help. > > I will use markdown as a preview, so th PR*Writer write:document is OK. > For the last phase I plan to use latex to generate a pdf following certain > presentation rules. > > I wonder if it is possible to use pillar 7 templates programmatically. > Is there some example I can follow? > > Thanks again! > > > > On Mon, Feb 19, 2018 at 6:42 AM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> >> >> On Sun, Feb 18, 2018 at 9:01 PM, Stephane Ducasse < >> stepharo.self(a)gmail.com> wrote: >> >>> Hi arturo >>> >>> What you saw is the pipeline to produce book and others. Now I do not >>> think that you need it. >>> To export markdown you do not need the pillar configuration and the rest. >>> Check the chapter 6 in the publishing a booklet with pillar document. >>> >>> You can just get your document using the Pillar parser. >>> >>> | wiki doc | >>> wiki := '!My Document'. >>> doc := PRPillarParser parse: wiki >>> >>> Or from a file: >>> >>> PRPillarParser parse: (FileSystem workingDirectory / 'foo.pillar') >>> >>> readStream >>> >>> You can also instantiate the document model, one node after the other, >>> start- ing with PRDocument and adding sub-instances of PRDocumentItem: >>> >>> | document title figure| >>> >>> document := PRDocument new. >>> >>> title := PRHeader new >>> >>> level: 1; >>> >>> add: (PRText content: 'foo'); >>> >>> yourself. >>> >>> figure := PRFigure new >>> >>> add: (PRText content: 'Alias'); >>> >>> then to export in HTML you just ask the htmlWriter. So I think that >>> this is the same for markdown. >>> >>> PRHTMLWriter write: document >>> >>> >>> Now pay attention because we are currently rewriting the pipeline of >>> document production in Pillar 70. >>> >> >> Yeh, but ideally the pipeline should only automatically orchestrate what >> people should be still able to do programatically :) >> >> So I think keeping >> >> PRHTMLWriter write: document >> >> and >> >> PRHTMLWriter write: document toStream: ... >> >> & family, is good. >> >> >>> This is why this is not in master but in a specific branch. >>> >>> Stef >>> >>> >>> >>> >>> >>> >>> On Sun, Feb 18, 2018 at 7:13 PM, Arturo Zambrano >>> <arturo.zambrano(a)gmail.com> wrote: >>> > Hi, >>> > I figured it out (at least in part) >>> > >>> > configuration := PRPillarConfiguration new. >>> > configuration outputType: PRMarkdownWriter. >>> > export:=PRExportPhase new . >>> > export executeOn: >>> > (PRCompilationContext withDocument: document withConfiguration: >>> > configuration) >>> > >>> > >>> > This code snipped generates a Json file which contains the markdown... >>> how >>> > do I generate just the markdown? >>> > >>> > TIA >>> > Arturo >>> > >>> > >>> > On Sun, Feb 18, 2018 at 2:16 PM, Arturo Zambrano < >>> arturo.zambrano(a)gmail.com> >>> > wrote: >>> >> >>> >> Hi, >>> >> can someone please tell me how to export a document using pillar7? >>> >> >>> >> For pillar5 the example used to be: >>> >> >>> >> configuration := PRPillarConfiguration new. >>> >> configuration outputType: PRHTMLWriter. >>> >> PRExportPhase executeOn: { document } with: configuration. >>> >> >>> >> >>> >> Thanks! >>> > >>> > >>> >>> >> >> >> -- >> >> >> >> Guille Polito >> >> Research Engineer >> >> Centre de Recherche en Informatique, Signal et Automatique de Lille >> >> CRIStAL - UMR 9189 >> >> French National Center for Scientific Research - *http://www.cnrs.fr >> <http://www.cnrs.fr>* >> >> >> *Web:* *http://guillep.github.io* <http://guillep.github.io> >> >> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >> > >

March 1, 2018

Re: [Pharo-users] [ANN] 900 pull requests closed for Pharo7!

by CÃ©drick BÃ©ler

March 1, 2018

Re: [Pharo-users] [ANN] 900 pull requests closed for Pharo7!

by Marcus Denker

We are at 949 nowâ¦ And not all are smallâ¦ e.g. one in preparation: https://github.com/pharo-project/pharo/pull/871 > On 1 Mar 2018, at 01:16, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > Congrats! > > Pharo series 7 is worthy our patience, because of all the hard work all of you are doing and improvements behind. > > Thanks, > > Offray > > On 24/02/18 11:49, Arturo Zambrano wrote: >> Amazing job. A big THANK YOU to all Pharo contributors. >> >> On Fri, Feb 23, 2018 at 9:57 AM, Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >> Impressive! >> >> Alexandre >> >> http://bergel.eu <http://bergel.eu/> >> >> Le 23 fÃ©vr. 2018 Ã 09:27, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> a Ã©crit : >> >>> Hi, >>> >>> March 11, we passed 800. Today (just now) we closed 900 full requests! >>> >>> https://github.com/pharo-project/pharo/pulls <https://github.com/pharo-project/pharo/pulls> >>> >>> Marcus >> >

March 1, 2018

Re: [Pharo-users] [ANN] 900 pull requests closed for Pharo7!

by Offray Vladimir Luna CÃ¡rdenas

Congrats! Pharo series 7 is worthy our patience, because of all the hard work all of you are doing and improvements behind. Thanks, Offray On 24/02/18 11:49, Arturo Zambrano wrote: > Amazing job. A big THANK YOU to all Pharo contributors.Â > > On Fri, Feb 23, 2018 at 9:57 AM, Alexandre Bergel > <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: > > Impressive! > > AlexandreÂ > > http://bergel.eu <http://bergel.eu> > > Le 23 fÃ©vr. 2018 Ã 09:27, Marcus Denker <marcus.denker(a)inria.fr > <mailto:marcus.denker@inria.fr>> a Ã©critÂ : > >> Hi, >> >> March 11, we passed 800. Today (just now) we closed 900 full >> requests! >> >> https://github.com/pharo-project/pharo/pulls >> <https://github.com/pharo-project/pharo/pulls> >> >> Marcus > >

March 1, 2018