- Pharo-dev - lists.pharo.org

New booklet available
by Stephane Ducasse May 14, 2017

May 14, 2017

A new booklet is joining the collection and it is on Voyage the object to document mapper developed by E. Lorenzano. Available in beta http://files.pharo.org/books/ and open to contributors at https://github.com/SquareBracketAssociates/Booklet-Voyage Enjoy Stef

1 0

10/05/17 - Advancing in Pharo Code Quality Support - Myroslava Romaniuk
by Myroslava Romaniuk May 14, 2017

May 14, 2017

A. Work done: - converted a new rule and updated my git repository - read chapters 5 and 6 of the 'Pharo by Example' book - started collaborating with my mentors using a Trello board B. Next steps: - continue reading 'Pharo by Example' - update and convert more rules - watch more tutorials relating to my project (e.g. matchtool tutorial, etc) C. Help required: - I'm seeing other Pharo members also struggling with the same error in iceberg (LGit_GIT_ERROR: error authenticating: failed connecting agent), Ben Coman suggested notifying the pharo-dev community. I know you're all really busy with the upcoming Pharo 6 release but since this bug is kind of pertinent to the new release I thought maybe I should report it on fogbugz? If yes, what priority, whom should I notify? P.S. for me it's the same error when downloading both the stable and the latest versions of the Pharo 6 VM. For now I'm still making do with the 60450 version but would really like to upgrade to a newer one and can't find the one that wouldn't cause any errors. I'm on Win 7 (64 bit). Would appreciate some advice or help with this - also if there's any advice regarding what I should read or look at that's connected to the work I'm doing on my GSoC project, that would be great

3 3

How to be able to get a debugger inside DNU
by Stephane Ducasse May 14, 2017

May 14, 2017

Hi In the past it was possible to step throw such code and now we cannot anymore because of a smart trick. I should say that I hate when we break the reachibility and understandibility of the system. So why I cannot get a debugger opens after the halt: ? How do I get that ? Now I will put traces: super cool! Stef doesNotUnderstand: aMessage "support sending message to access properties" | selector | selector := aMessage selector. self halt: aMessage selector. ^ selector isUnary ifTrue: [ (self hasPropertyAt: selector) ifTrue: [ self propertyAt: aMessage selector asSymbol ] ifFalse: [ super doesNotUnderstand: aMessage ] ] ifFalse: [ selector numArgs = 1 ifTrue: [ self propertyAt: aMessage selector allButLast asSymbol put: aMessage argument ] ifFalse: [ super doesNotUnderstand: aMessage ] ]

3 4

[ANN] Pompeii Volcanic Graphics, a mesh based 2D graphics API
by Ronie Salgado May 13, 2017

May 13, 2017

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

6 9

Official cover for the Pharo booklet collection
by Stephane Ducasse May 13, 2017

May 13, 2017

Tx damien Stef [image: Inline image 1]

4 4

Re: [Pharo-dev] Missing plugins to make the vmProfiler work
by csrabak＠bol.com.br May 13, 2017

May 13, 2017

2 1

Re: [Pharo-dev] immediateByteSubclass: ?
by Stephane Ducasse May 12, 2017

May 12, 2017

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 > > > > > >

1 0

immediateByteSubclass: ?
by Stephane Ducasse May 12, 2017

May 12, 2017

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

3 2

Re: [Pharo-dev] [ann] bloc & cairo+morphic
by Tudor Girba May 12, 2017

May 12, 2017

Hi, It seems that my initial message generated a misunderstanding. My original blog post was meant to communicate two things: 1. That the known Bloc project has received a new feature that the community raised as a problem (i.e., host & backend). 2. Address the other concern that the community raised: how to sustain the Bloc development in terms of engineering effort. This is why we announced the financial support for the work of Alex that is valid from this point on. The post was certainly not intended to overlook the people that contributed to the overall project. I apologize if it looked like this. To clarify the historical perspective, we now added an explicit history page on the official project page: https://github.com/pharo-graphics/Bloc/blob/master/HISTORY.md I also changed the blog post to more clearly communicate the intent: http://www.humane-assessment.com/blog/bloc-flexible-backends-hosts/ I hope this addresses the concerns. I am really excited that Alain joined and that we can get even more traction around Bloc. Cheers, Doru > On May 12, 2017, at 7:56 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > BTW for an historical perspective > > RMoD me and igor were also involved far less than the effort of alain but as he mentioned it we collaborated on it. I spent time on documenting several versions and I stopped disgusted to see the total lack of attention for comments. > Then Rmod paid nearly a year of effort on Athens, SDL20 support, a year on TxText. I find really strange that we are not even mentioned in any support. > > Stef > > > On Thu, May 11, 2017 at 8:12 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Doru can you change the humane assessment blog post? > > > On Thu, May 11, 2017 at 8:07 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Indeed, this is wonderful news that you will rejoin your baby project :). > > Cheers, > Doru > > > > On May 11, 2017, at 6:40 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > > > Hi Alain! > > > > Thanks for the mail (even if the historial part has always been pretty clear to me). > > We miss you! Be back soon! > > > > Cheers, > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > >> On May 11, 2017, at 12:36 PM, Alain Plantec via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > >> > >> > >> From: Alain Plantec <alain.plantec(a)yahoo.com> > >> Subject: Re: [Pharo-users] [ann] bloc & cairo+morphic > >> Date: May 11, 2017 at 12:36:36 PM GMT-3 > >> To: Pharo Development List <pharo-dev(a)lists.pharo.org> > >> Cc: Alain Plantec <alain.plantec(a)yahoo.com>, Moose-related development <moose-dev(a)list.inf.unibe.ch>, Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > >> > >> > >> Hello Doru, all, > >> > >> Iâm really happy to see Bloc progresses. > >> Even Iâm not active since more than one year, Bloc is still an important project for me. > >> > >> but let me complete this short historical presentation a little bit. > >> > >> Bloc is a project that I initiated in 2013 in collaboration with RMOD following experiments made around the ROME project. > >> The idea was to completely revisit the 2D framework of Pharo to address Morphic limits. > >> Following an invitation of the Software Composition Group (thanks to Oscar Nierstrasz and to Doru here), > >> I presented the first version of Bloc at Bern (March, 2015), then Doru and Aliaksel joined the project. > >> One year ago, during his PhD at Brest, Glenn Cavarle produced a new version of the Bloc infrastructure that is now the > >> one used together with the layouting system that was implemented by Aliaksel. > >> > >> Please, do not use the humane assessment web site but the github project one instead. > >> > >> I will restart working on Bloc/Brick soon in the context of a project that we recently signed with the Thales company. > >> > >> Thanks, > >> Cheers > >> > >> Alain > >> > >> > >>> On 8 mai 2017, at 23:00, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >>> > >>> Hi, > >>> > >>> We are happy to announce that based on the work of Glenn, Alex extended Bloc (Sparta) to work directly in the Morphic world using Cairo as a backend. > >>> > >>> Cairo is less powerful than Moz2D (see the screenshot below for an example), but the implementation addresses a concern that the community raised regarding a perceived increased liability due to the dependency to Moz2D. Essentially this means that Bloc can be treated as another graphical library that can coexist with Morphic without requiring any external VM plugin. > >>> > >>> <bloc-two-backends-morphic-host-figures.png> > >>> > >>> I would also like to point out that adding a new backend and host was possible because of the many iterations (including throwing away whole implementations) that Alex and Glenn went through. I think they did an amazing job. > >>> > >>> You can find a bit more details about Bloc here: > >>> http://www.humane-assessment.com/blog/bloc-flexible-backends-hosts/ > >>> > >>> Another issue raised regarding Bloc was that of the engineering effort required to make it a reality. That is why I would also like to announce that Alex joined feenk.com where he is primarily working on the graphical stack for Pharo. > >>> > >>> Cheers, > >>> Doru > >>> > >>> > >>> -- > >>> www.tudorgirba.com > >>> www.feenk.com > >>> > >>> "To lead is not to demand things, it is to make them happen." > >>> > >>> > >>> > >>> > >> > >> > >> > >> > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)list.inf.unibe.ch > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- > www.tudorgirba.com > www.feenk.com > > "Yesterday is a fact. > Tomorrow is a possibility. > Today is a challenge." > > > > > > > -- www.tudorgirba.com www.feenk.com "Presenting is storytelling."

1 0

Re: [Pharo-dev] Missing plugins to make the vmProfiler work on Pharo
by csrabak＠bol.com.br May 12, 2017

May 12, 2017

On Thu, 11 May 2017 11:34:47 +0200, Cl?ment Bera <bera.clement(a)gmail.com> wrote: > On Wed, May 10, 2017 at 8:12 PM, Esteban A. Maringolo > <emaringolo(a)gmail.com> wrote: > > > 2017-05-10 13:38 GMT-03:00 Cl?ment Bera <bera.clement(a)gmail.com>: > > > On Wed, May 10, 2017 at 5:28 PM, Esteban A. Maringolo < > > emaringolo(a)gmail.com> wrote: > > > > >> If it is a plug-in, why does it need VM recompilation? > > > Internal plugins require VM recompilation. Only external plugins > > > do not. > > It was more of a semantic question, I'd expect a plug-in to be > > that, pluggable, as you say external plugins are. Or what is the > > "pluggability" of such plugins? > > > I would say there is 3 levels of pluggability: 1 non optional > internal plugin, pluggable because it can be replaced by another > internal plugin implementing the same API at VM compilation time. > Used for modularity of specific aspects of the VM. 2 optional > internal plugin, pluggable because it can be removed / added / > replaced at VM compilation time. Used to improve performance over > external plugin or to access VM functions not exposed to external > plugins. 3 external plugin, pluggable because it can be removed / > added / replaced after the VM is compiled. Used for all other > plugins. > So they're all pluggable in some way. > I'm on this vital industry for 45+ years and I already learned that words and names have usages and except when standarized via certains bodies aimed specifically the meaning can vary even within the same realm of the art. That written, and without attempting to start a semantic discussion, however feeling a contribution may be useful, I would say that the 'levels' one and two described above would better called "modules" instead of plugins. In my way of understanding this non mother tongue "compile time plugins" seem to be more a figure of speech than the offering of 'plugability' which plugins offer, or perhaps, in my humble perception ought to offer. Also, I think it would be less surprising for most people when exposed to the subject (module == compiling, plugin == run time). Just my 0,0199999.... -- Cesar Rabak

2 1