- Pharo-users - lists.pharo.org

Re: [Pharo-users] #ast vs. #parseTree

by Sean P. DeNigris

Marcus Denker-4 wrote > #ast returns a result from the cache, while #parseTree always gets a new > oneâ¦ Ah, okay. What is the difference? That is, how/when is the cache updated? Marcus Denker-4 wrote > Yes, it could be better. Like always. :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/ast-vs-parseTree-tp4893074p4893146.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 1, 2016

Re: [Pharo-users] RT export to PDF

by Stephan Eggermont

On 01/05/16 04:00, Arturo Zambrano wrote: > Hi, > I'm using RT on top of pharo5. > As I need to export to pdf, I also installed > RTPDFExporter > and > Artefact > > development versions > > Exporting to pdf fails with MNU RTPDFVisitor>>visitMapShape: > > any hint regarding this? The PDF exporter has its last updates in november, so might be slightly out of date. When comparing RTSVGVisitor2 to RTPDFVisitor, I notice some missing visitors. AFAIK, Artefact has limited bitmap support at the moment, and uses the JPEGReadWriter instead of embedding directly. http://forum.world.st/PNG-in-Artefact-td4798885.html You need to add something like RTPDFVisitor>>visitBitMapShape: aBitmapShape | s | s := WriteStream on: ByteArray new. TRPlatform current pngReadWriterClass putForm: (aBitmapShape form) onStream: s. page add: (PDFPngElement from: aBitmapShape encompassingRectangle topLeft x mm @ aBitmapShape encompassingRectangle topLeft y mm dimension: aBitmapShape width mm @ aBitmapShape height mm fromStream: s contents readStream) Stephan

May 1, 2016

Re: [Pharo-users] Pharo 3 / Pharo3 Dark Theme names

by Esteban Lorenzano

is for historical reasonsâ¦ there is no actual reason to not rename them :) > On 01 May 2016, at 11:06, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > yesâ¦ I am thinking that always when I happen to see it in the setting. >> On 30 Apr 2016, at 18:35, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> >> Hi, >> >> is there some reason why the theme is called "Pharo 3" and "Pharo3 Dark"â¦ I mean we are about to start Pharo 6 so maybe it should just be "Pharo Dark" and "Pharo Light" (or "Pharo" or "Pharo Default" or whatever) >> >> Peter > >

May 1, 2016

Re: [Pharo-users] Pharo 3 / Pharo3 Dark Theme names

by Marcus Denker

yesâ¦ I am thinking that always when I happen to see it in the setting. > On 30 Apr 2016, at 18:35, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Hi, > > is there some reason why the theme is called "Pharo 3" and "Pharo3 Dark"â¦ I mean we are about to start Pharo 6 so maybe it should just be "Pharo Dark" and "Pharo Light" (or "Pharo" or "Pharo Default" or whatever) > > Peter

May 1, 2016

Re: [Pharo-users] #ast vs. #parseTree

by Marcus Denker

#ast returns a result from the cache, while #parseTree always gets a new oneâ¦ yes, it could be documented. Yes, it could be better. Like always. Marcus > On 30 Apr 2016, at 22:25, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Why does CompiledMethod understand both? They are in the same protocol, > produce the same kindOf result, and neither has a method comment! :/ (Pharo > 4.0) > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/ast-vs-parseTree-tp4893074.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

May 1, 2016

Re: [Pharo-users] Create BaselineOf from ConfigurationOf

by Thierry Goubier

Le 30/04/2016 23:28, Sean P. DeNigris a Ã©crit : > I got tired of manually converting Configs into Baselines, so I wrote a > little script. You pass it the selector of a #baselineXyz: method, and it > converts it (i.e. changes the pragma, removes the blessing and repo, etc) > Hopefully you will find it useful. Cross posting to Metcello list... > > ConfigurationOf>>#createBaselineFrom: selector > > | projectName baselineName baseline methodTree commonBlockBody repoSetter | > > "Create new class" > projectName := self name allButFirst: self superclass name size. > baselineName := 'BaselineOf', projectName. > baseline := BaselineOf subclass: baselineName asSymbol > instanceVariableNames: '' > classVariableNames: '' > category: baselineName. > > "Convert baseline##: method" > methodTree := (self methodNamed: selector) parseTree. Oh, that's why you were asking for #ast versus #parseTree. Thierry > methodTree selector: #baseline:. > methodTree pragmas at: 1 put: (RBPragmaNode selector: #baseline arguments: > #()). > commonBlockBody := methodTree statements first arguments last body. > repoSetter := commonBlockBody statements detect: [ :e | e selector = > #repository: ]. > commonBlockBody removeNode: repoSetter. > > "Compile baseline method" > baseline compile: methodTree newSource classified: 'baseline' > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Create-BaselineOf-from-ConfigurationOf-tp4893076.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

May 1, 2016

Re: [Pharo-users] Create BaselineOf from ConfigurationOf

by Gabriel Cotelli

Nice. I will give it a try On Apr 30, 2016 19:03, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > I got tired of manually converting Configs into Baselines, so I wrote a > little script. You pass it the selector of a #baselineXyz: method, and it > converts it (i.e. changes the pragma, removes the blessing and repo, etc) > Hopefully you will find it useful. Cross posting to Metcello list... > > ConfigurationOf>>#createBaselineFrom: selector > > | projectName baselineName baseline methodTree commonBlockBody > repoSetter | > > "Create new class" > projectName := self name allButFirst: self superclass name size. > baselineName := 'BaselineOf', projectName. > baseline := BaselineOf subclass: baselineName asSymbol > instanceVariableNames: '' > classVariableNames: '' > category: baselineName. > > "Convert baseline##: method" > methodTree := (self methodNamed: selector) parseTree. > methodTree selector: #baseline:. > methodTree pragmas at: 1 put: (RBPragmaNode selector: #baseline > arguments: > #()). > commonBlockBody := methodTree statements first arguments last body. > repoSetter := commonBlockBody statements detect: [ :e | e selector > = > #repository: ]. > commonBlockBody removeNode: repoSetter. > > "Compile baseline method" > baseline compile: methodTree newSource classified: 'baseline' > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Create-BaselineOf-from-ConfigurationOf-tp4893076.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

May 1, 2016

RT export to PDF

by Arturo Zambrano

Hi, I'm using RT on top of pharo5. As I need to export to pdf, I also installed RTPDFExporter and Artefact development versions Exporting to pdf fails with MNU RTPDFVisitor>>visitMapShape: any hint regarding this? cheers, arturo

May 1, 2016

Create BaselineOf from ConfigurationOf

by Sean P. DeNigris

I got tired of manually converting Configs into Baselines, so I wrote a little script. You pass it the selector of a #baselineXyz: method, and it converts it (i.e. changes the pragma, removes the blessing and repo, etc) Hopefully you will find it useful. Cross posting to Metcello list... ConfigurationOf>>#createBaselineFrom: selector | projectName baselineName baseline methodTree commonBlockBody repoSetter | "Create new class" projectName := self name allButFirst: self superclass name size. baselineName := 'BaselineOf', projectName. baseline := BaselineOf subclass: baselineName asSymbol instanceVariableNames: '' classVariableNames: '' category: baselineName. "Convert baseline##: method" methodTree := (self methodNamed: selector) parseTree. methodTree selector: #baseline:. methodTree pragmas at: 1 put: (RBPragmaNode selector: #baseline arguments: #()). commonBlockBody := methodTree statements first arguments last body. repoSetter := commonBlockBody statements detect: [ :e | e selector = #repository: ]. commonBlockBody removeNode: repoSetter. "Compile baseline method" baseline compile: methodTree newSource classified: 'baseline' ----- Cheers, Sean -- View this message in context: http://forum.world.st/Create-BaselineOf-from-ConfigurationOf-tp4893076.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 30, 2016

#ast vs. #parseTree

by Sean P. DeNigris

Why does CompiledMethod understand both? They are in the same protocol, produce the same kindOf result, and neither has a method comment! :/ (Pharo 4.0) ----- Cheers, Sean -- View this message in context: http://forum.world.st/ast-vs-parseTree-tp4893074.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 30, 2016