- Pharo-dev - lists.pharo.org

[ANN] Pompeii Volcanic Graphics, a mesh based 2D graphics API

by Ronie Salgado

Hello, I am releasing a first version of a new 2D graphics API that I am making for Pharo, using OpenGL. [image: ImÃ¡genes integradas 1] [image: ImÃ¡genes integradas 2] http://smalltalkhub.com/#!/~ronsaldo/PompeiiGraphics https://youtu.be/emE6_1RpAo8 This 2D graphics API is not vectorial based becase it does not use SVG style paths. This API is triangle mesh based, so it is more friendlier with the GPU than Athens or Sparta. With this API I did a basic gui toolkit, with only two widgets: buttons and label. I did this Widget toolkit to not mess with Bloc, and because I need something relatively stable for the Woden 2 level editor. For now, I am leaving this widget toolkit mostly as a demo. Hopefully it is possible to make Bloc backend using this API. During the process of making this API, I had to fix several bugs with OSWindow, and bugs in the interaction between OSWindow and OpenGL. The biggest problem was a race condition between the creation of an OSWindow using SDL2, and the events (such as Expose) that are sent to the just created Window. As for Mac OS X, OSWindow is out of service until a pull request ( https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/138 ) gets integrated into the VM. Best regards, Ronie

May 12, 2017

Re: [Pharo-dev] Official cover for the Pharo booklet collection

by Oleks

It looks wonderful! -- View this message in context: http://forum.world.st/Official-cover-for-the-Pharo-booklet-collection-tp494… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 12, 2017

Git breaks Monticello's version numbers

by Oleksandr Zaytsev

Hello Two days ago I was trying to send the slice with my fix to PolyMath using Monticello. But the version number got set to 1494471195. Today I realized that all the packages to which I commit are numbered like that. Cyril Ferlicot explained to me that this happens when I mix git and Monticello commits. He suggested that I use a separate image for committing to GitHub, or file out/file in if there is a lot of changes to commit. Can this be considered a bug? Should I report it? I think it would be causing problems for many people. Oleks

May 12, 2017

Re: [Pharo-dev] Missing plugins to make the vmProfiler work

by csrabak＠bol.com.br

May 12, 2017

Re: [Pharo-dev] Official cover for the Pharo booklet collection

by serge.stinckwich＠gmail.com

Nice !!! EnvoyÃ© de mon iPhone > Le 12 mai 2017 Ã 20:43, Stephane Ducasse <stepharo.self(a)gmail.com> a Ã©crit : > > Tx damien > > Stef > > <bklet-Glorp.jpg>

May 12, 2017

Re: [Pharo-dev] immediateByteSubclass: ?

by Stephane Ducasse

Tx we will remove it. In pharo 70 we will have - a classParser with a class definition to handle all the terrible logic of importing - a fluid class definition - and it will help removing duplicated and old logic with a huge number of optional parameters ... Stef On Fri, May 12, 2017 at 8:25 PM, Benoit St-Jean via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > > > ---------- Forwarded message ---------- > From: Benoit St-Jean <bstjean(a)yahoo.com> > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Cc: > Bcc: > Date: Fri, 12 May 2017 18:25:53 +0000 (UTC) > Subject: Re: [Pharo-dev] immediateByteSubclass: ? > If that's of any help, I was able to track it back to Squeak 5.0 and it > had no sender in that version too! The author's initials are eem. > > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > Instagram: Chef_Benito > IRC: lamneth > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) > > > ------------------------------ > *From:* ClÃ©ment Bera <bera.clement(a)gmail.com> > *To:* Pharo Development List <pharo-dev(a)lists.pharo.org> > *Sent:* Friday, May 12, 2017 1:40 PM > *Subject:* Re: [Pharo-dev] immediateByteSubclass: ? > > This one looks strange and seems indeed to be dead code. > > Maybe it was an attempt to make a specific class definition keyword for > CompiledMethod / CompiledCode / CompiledBlock. Right now there is a > specific case in the code somewhere to use the specific compiledCode layout > for those 3 classes instead of the byte layout which is normally used for > the keyword variableByteSubclass: that those 3 classes use. > > I am not sure immediateByteSubclass: makes sense though. I would rather > have compiledCodeSubclass, variablePointerAndByteSubclass or something like > that. > > On Fri, May 12, 2017 at 5:39 PM, Stephane Ducasse <stepharo.self(a)gmail.com > > wrote: > > Hi > > with guille we are working on a class parser and our game is to make sure > that we can parse all the crazy class definitions among which > > variableWordSubclass: > ephemeronSubclass: > weakSubclass: > variableByteSubclass: > variableSubclass: > immediateSubclass: > subclass: aSubclassSymbol layout: > > And we found this method definition and it has no senders and we wonder if > it is just plain deadcode? > > immediateByteSubclass: className instanceVariableNames: instvarNames > classVariableNames: classVarNames package: package > "Added to allow for a simplified subclass creation experience. " > > ^ self > immediateSubclass: className > instanceVariableNames: instvarNames > classVariableNames: classVarNames > package: package > > S & G > > > > > >

May 12, 2017

Official cover for the Pharo booklet collection

by Stephane Ducasse

Tx damien Stef [image: Inline image 1]

May 12, 2017

Re: [Pharo-dev] immediateByteSubclass: ?

by Benoit St-Jean

If that's of any help, I was able to track it back to Squeak 5.0 and it had no sender in that version too!Â The author's initials are eem. Â ----------------- BenoÃ®t St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero".Â (A. Einstein) From: ClÃ©ment Bera <bera.clement(a)gmail.com> To: Pharo Development List <pharo-dev(a)lists.pharo.org> Sent: Friday, May 12, 2017 1:40 PM Subject: Re: [Pharo-dev] immediateByteSubclass: ? This one looks strange and seems indeed to be dead code.Â Maybe it was an attempt to make a specific class definition keyword for CompiledMethod / CompiledCode / CompiledBlock. Right now there is a specific case in the code somewhere to use the specific compiledCode layout for those 3 classes instead of the byte layout which is normally used for the keywordÂ variableByteSubclass: that those 3 classes use. I am not sureÂ immediateByteSubclass: makes sense though. I would rather have compiledCodeSubclass, variablePointerAndByteSubclass or something like that. On Fri, May 12, 2017 at 5:39 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: HiÂ with guille we are working on a class parser and our game is to make sure that we can parse all the crazy class definitions among whichÂ variableWordSubclass:ephemeronSubclass:weakSubclass:variableByteSubclass:variableSubclass:immediateSubclass:Â subclass: aSubclassSymbol Â layout: And we found this method definition and it has no senders and we wonder ifÂ it is just plain deadcode? immediateByteSubclass: className instanceVariableNames: instvarNames classVariableNames: classVarNames package: package "Added to allow for a simplified subclass creation experience. " ^ self immediateSubclass: className instanceVariableNames: instvarNames classVariableNames: classVarNames package: package S & G

May 12, 2017

Re: [Pharo-dev] immediateByteSubclass: ?

by ClÃ©ment Bera

This one looks strange and seems indeed to be dead code. Maybe it was an attempt to make a specific class definition keyword for CompiledMethod / CompiledCode / CompiledBlock. Right now there is a specific case in the code somewhere to use the specific compiledCode layout for those 3 classes instead of the byte layout which is normally used for the keyword variableByteSubclass: that those 3 classes use. I am not sure immediateByteSubclass: makes sense though. I would rather have compiledCodeSubclass, variablePointerAndByteSubclass or something like that. On Fri, May 12, 2017 at 5:39 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi > > with guille we are working on a class parser and our game is to make sure > that we can parse all the crazy class definitions among which > > variableWordSubclass: > ephemeronSubclass: > weakSubclass: > variableByteSubclass: > variableSubclass: > immediateSubclass: > subclass: aSubclassSymbol layout: > > And we found this method definition and it has no senders and we wonder if > it is just plain deadcode? > > immediateByteSubclass: className instanceVariableNames: instvarNames > classVariableNames: classVarNames package: package > "Added to allow for a simplified subclass creation experience. " > > ^ self > immediateSubclass: className > instanceVariableNames: instvarNames > classVariableNames: classVarNames > package: package > > S & G >

May 12, 2017

immediateByteSubclass: ?

by Stephane Ducasse

Hi with guille we are working on a class parser and our game is to make sure that we can parse all the crazy class definitions among which variableWordSubclass: ephemeronSubclass: weakSubclass: variableByteSubclass: variableSubclass: immediateSubclass: subclass: aSubclassSymbol layout: And we found this method definition and it has no senders and we wonder if it is just plain deadcode? immediateByteSubclass: className instanceVariableNames: instvarNames classVariableNames: classVarNames package: package "Added to allow for a simplified subclass creation experience. " ^ self immediateSubclass: className instanceVariableNames: instvarNames classVariableNames: classVarNames package: package S & G

May 12, 2017