- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ann] bloc & cairo+morphic

by Tudor Girba

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

May 12, 2017

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

by Eliot Miranda

Hi Cesar, > On May 11, 2017, at 12:10 PM, csrabak(a)bol.com.br wrote: > >> 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). +1. I think the system designers agreed with you because the way to find out what plugins are available is Smalltalk listLoadedModules > Just my 0,0199999.... > > -- > Cesar Rabak _,,,^..^,,,_ (phone)

May 12, 2017

[pharo-project/pharo-core] 4778e8: 60486

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 4778e8f6a49f99d25ca2860d8e36d4f08d545211 https://github.com/pharo-project/pharo-core/commit/4778e8f6a49f99d25ca2860d… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-05-12 (Fri, 12 May 2017) Changed paths: M BaselineOfIDE.package/BaselineOfIDE.class/instance/actions/additionalInitialization.st M BaselineOfIDE.package/BaselineOfIDE.class/instance/baseline/baseline_.st M BaselineOfIDE.package/BaselineOfIDE.class/instance/baseline/groups_.st M BaselineOfMorphic.package/BaselineOfMorphic.class/instance/actions/postload_package_.st M Glamour-Morphic-Brick.package/GLMHorizontalLinearLayout.class/instance/width/widthParentDependency_.st M Glamour-Morphic-Brick.package/GLMLinearLayout.class/instance/testing/hasWidthRestrictions_.st M Glamour-Morphic-Brick.package/GLMTabSelectorBrick.class/instance/actions/updateTabs.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60485.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60486.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60485.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60486.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60486 20050 Theme must be reset at the end of BaselineOfIDE loading https://pharo.fogbugz.com/f/cases/20050 20051 Tab labels in Glamour should not shrink if there is available space https://pharo.fogbugz.com/f/cases/20051 20049 TravisIntegrationHelp is not loaded into the bootstrapped image https://pharo.fogbugz.com/f/cases/20049 http://files.pharo.org/image/60/60486.zip

May 12, 2017

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60486 Home: https://github.com/pharo-project/pharo-core

May 12, 2017

Re: [Pharo-dev] Does OSSubprocess works on ARM vm?

by Mariano Martinez Peck

mmmm I don't know. Can you at least try for the first time in a 32 bits ARM ? On Fri, May 12, 2017 at 5:00 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi. > > I decided to ask before I will try it. > > Best regards, > Denis > -- Mariano http://marianopeck.wordpress.com

May 12, 2017

Does OSSubprocess works on ARM vm?

by Denis Kudriashov

Hi. I decided to ask before I will try it. Best regards, Denis

May 12, 2017

Re: [Pharo-dev] Extending the debugger inspector with a new presentation

by Denis Kudriashov

Hi. One possibility is to follow BytecodeDebugger approach. Try to look how it is implemented 2017-05-12 9:53 GMT+02:00 <tdupriez(a)ens-paris-saclay.fr>: > Hello, > > I would like to extend the debugger with some context-dependent > information. > I am playing with metalinks and I would like to show, in the debugger, > some information if my metalinks are in the selected method. > This means that: > - I need to add a new presentation in the debugger next to the "variable" > and "evaluator" ones. > - I need to filter that presentation to show it depending on which method > is selected. > > I tried to extend ProtoObject with a method like: > > gtDebuggerExpressionMachinViewIn: composite > <gtDebuggerPresentationOrder: 21> > > composite text > title: 'My machin'; > display: [ :browser :debugger | debugger asString] > > However, this did not add a presentation in the debugger. It only show up > when selecting an object in the debugger inspector (see screenshot). > > How can I extend the debugger as I want? > > Thanks > Thomas and Guille >

May 12, 2017

Extending the debugger inspector with a new presentation

by tdupriez＠ens-paris-saclay.fr

Hello, I would like to extend the debugger with some context-dependent information. I am playing with metalinks and I would like to show, in the debugger, some information if my metalinks are in the selected method. This means that: - I need to add a new presentation in the debugger next to the "variable" and "evaluator" ones. - I need to filter that presentation to show it depending on which method is selected. I tried to extend ProtoObject with a method like: gtDebuggerExpressionMachinViewIn: composite <gtDebuggerPresentationOrder: 21> composite text title: 'My machin'; display: [ :browser :debugger | debugger asString] However, this did not add a presentation in the debugger. It only show up when selecting an object in the debugger inspector (see screenshot). How can I extend the debugger as I want? Thanks Thomas and Guille

May 12, 2017

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

by csrabak＠bol.com.br

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

May 11, 2017

Re: [Pharo-dev] [Moose-dev] [Pharo-users] [ann] bloc & cairo+morphic

by Tudor Girba

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

May 11, 2017