- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] GSoC 2017 Introduction

by Yuriy Tymchuk

> On 10 May 2017, at 22:15, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > I think that we should remove the thiumb up/down because nobody uses them. Damn, I forgot to do thatâ¦ It would be nice to replace it with other stuff, but yes, it wonât make much sense especially when I stop looking at that.

May 10, 2017

Re: [Pharo-dev] GSoC 2017 Introduction

by Stephane Ducasse

Hello everyone I have been accepted as a GSoC student and my project is Advancing in Pharo Quality Support. Here <https://docs.google.com/document/d/1cX7VJ2QZejq_Cu6Ur28UCiUwzSD-Bu8GgSDqECi…>'s the link to my proposal, if you have any suggestions feel free to comment or send me an email, I would really appreciate some feedback. Here are also links to my github <https://github.com/myroslavarm> and linkedin <https://www.linkedin.com/in/myroslavarm/>. In short, my project consists of several subprojects: - updating rules (improving hints, moving the rules to corresponding packages) I would love to see more rules with automatic correction. Indeed repackageing some of them is a good idea. - advanced rule toggle (a functionality to enable/disable rules from Pharo settings, a shortcut to ban a rule globally) I think that we should remove the thiumb up/down because nobody uses them. - smart error handling (display errors that occured during critique computation along the actual critiques) With guille we are working to get a real class definition object (AST) so that smart suggestions and other suggestions get easier to express (and many other good properties). - match-rewrite tool (combines features of matchtool and rewritetool, improves the process of inspecting, creating, editing and removing rules) YES YES YES. It would be great if you can also agregate the tool of mark Rizun. BTW you should read the presentation of Jason Lecerf at pharodays because he will document the unification algorithm used by the rewrite rule engine and it may help you (at least it should help me). - pre-commit quality feedback (an extension to either monticello or iceberg that will show modified parts of a project and critiques related to them --- if I have time) I did not get this one. - making rules more maintainable while reporting encountered bugs Thanks very much for this amazing opportunity to be working with all of you, and for the help you're providing us, GSoC students, with - on Discord and in the mailing list. Looking forward to the amazing summer with the Pharo community! On Tue, May 9, 2017 at 10:58 PM, Myroslava Romaniuk <romaniuk(a)ucu.edu.ua> wrote: > Hello everyone > > I have been accepted as a GSoC student and my project is Advancing in > Pharo Quality Support. Here > <https://docs.google.com/document/d/1cX7VJ2QZejq_Cu6Ur28UCiUwzSD-Bu8GgSDqECi…>'s > the link to my proposal, if you have any suggestions feel free to comment > or send me an email, I would really appreciate some feedback. Here are also > links to my github <https://github.com/myroslavarm> and linkedin > <https://www.linkedin.com/in/myroslavarm/>. > > In short, my project consists of several subprojects: > > - updating rules (improving hints, moving the rules to corresponding > packages) > - advanced rule toggle (a functionality to enable/disable rules from > Pharo settings, a shortcut to ban a rule globally) > - smart error handling (display errors that occured during critique > computation along the actual critiques) > - match-rewrite tool (combines features of matchtool and rewritetool, > improves the process of inspecting, creating, editing and removing rules) > - pre-commit quality feedback (an extension to either monticello or > iceberg that will show modified parts of a project and critiques related to > them --- if I have time) > - making rules more maintainable while reporting encountered bugs > > Thanks very much for this amazing opportunity to be working with all of > you, and for the help you're providing us, GSoC students, with - on Discord > and in the mailing list. > > Looking forward to the amazing summer with the Pharo community! > > -- Myroslava >

May 10, 2017

Re: [Pharo-dev] 10/05/17 - Advancing in Pharo Code Quality Support - Myroslava Romaniuk

by Yuriy Tymchuk

At some point you should learn about pattern code and rewrite rules. And AFAIK the information is super limited. The is some info here: http://www.refactory.com/the-rewritetool <http://www.refactory.com/the-rewritetool>. There are also nice in-Pharo help chapters âRefactoring Framework > RB Refactoring Engineâ which explain matchers and so on. Donât rush with this, first figure out how the other things work, but maybe someone can refer to more literature. After you learn that, maybe you can write a few blogposts about âstarting with pattern syntax and rewrite rulesâ. Cheers. Uko > On 10 May 2017, at 21:14, Myroslava Romaniuk <romaniuk(a)ucu.edu.ua> wrote: > > 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

May 10, 2017

Re: [Pharo-dev] GSoC 2017 Introduction

by Stephane Ducasse

Hello myroslava I'm happy for you and this is great for the community. Stef @Ben: I gave lectures to oleks and myroslava when I was at UCU during the fall. On Wed, May 10, 2017 at 5:34 PM, Ben Coman <btc(a)openinworld.com> wrote: > Welcome Myro, > Good to see you getting involved early in the process. > I understand you bumped into Pharo at your university, but there seems > no great Pharo presence there. > I'd be interested to hear a bit more about how you discovered Pharo. > > cheers -ben > > On Wed, May 10, 2017 at 4:58 AM, Myroslava Romaniuk <romaniuk(a)ucu.edu.ua> > wrote: > > Hello everyone > > > > I have been accepted as a GSoC student and my project is Advancing in > Pharo > > Quality Support. Here's the link to my proposal, if you have any > suggestions > > feel free to comment or send me an email, I would really appreciate some > > feedback. Here are also links to my github and linkedin. > > > > In short, my project consists of several subprojects: > > > > updating rules (improving hints, moving the rules to corresponding > packages) > > advanced rule toggle (a functionality to enable/disable rules from Pharo > > settings, a shortcut to ban a rule globally) > > smart error handling (display errors that occured during critique > > computation along the actual critiques) > > match-rewrite tool (combines features of matchtool and rewritetool, > improves > > the process of inspecting, creating, editing and removing rules) > > pre-commit quality feedback (an extension to either monticello or iceberg > > that will show modified parts of a project and critiques related to them > --- > > if I have time) > > making rules more maintainable while reporting encountered bugs > > > > Thanks very much for this amazing opportunity to be working with all of > you, > > and for the help you're providing us, GSoC students, with - on Discord > and > > in the mailing list. > > > > Looking forward to the amazing summer with the Pharo community! > > > > -- Myroslava > >

May 10, 2017

10/05/17 - Advancing in Pharo Code Quality Support - Myroslava Romaniuk

by Myroslava Romaniuk

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

May 10, 2017

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

by Esteban A. Maringolo

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? Disclaimer: I don't know about the VM internals (*), and this is not a complain of any sort. I just wonder it is called that way. Regards! Esteban A. Maringolo (*) I did compile a Squeak VM a decade ago (added two primitives) but nothing more than that.

May 10, 2017

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

by Sophie Kaleba

Thanks for your help! @Nicolas, I'll do it that way 2017-05-10 17:15 GMT+02:00 Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com>: > Hi Sophie, > you could try and modify the plugins.int or plugins.ext files for various > pharo distributions and do a pull request on github opensmalltalk-vm. > Then let Esteban accept the request or not before the release of Pharo... > (if the build are green, there's no reason to not accept it). > > 2017-05-10 15:39 GMT+02:00 Max Leske <maxleske(a)gmail.com>: > >> OK, I see. >> >> >> On 10 May 2017, at 15:11, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: >> >> Hi Max, >> >> She has already done that. The point is to add the plugins in the default >> Pharo VM, so everyone can use the VM profiler. We would like to have the VM >> profiler loadable through the Pharo catalog, but many people won't be able >> to use it if the default Pharo VM does not support it... >> >> The plugin is lightweight, so I don't see why we can't have it. >> >> Best, >> >> On Wed, May 10, 2017 at 3:00 PM, Max Leske <maxleske(a)gmail.com> wrote: >> >>> Hi Sophie, >>> >>> You will have to compile your own VM for the moment. It's fairly easy >>> but you might run into problems when including the extra plugin. To build >>> the VM, follow the instructions on https://github.com/OpenSmal >>> ltalk/opensmalltalk-vm and read the README and HOWTO files. Simple >>> build example: >>> >>> cd ~/git/opensmalltalk-vm/build.macos32x86/pharo.cog.spur/ && ./mvm -d >>> >>> will build a debug VM. You'll have to modify one of the "plugins.*" >>> files to include the plugin. >>> >>> HTH, >>> Max >>> >>> On 10 May 2017, at 14:36, Sophie Kaleba <sophie.kaleba(a)gmail.com> wrote: >>> >>> Hi Esteban, Hi all, >>> >>> I am working on porting the Squeak VMProfiler to Pharo as a gsoc (I will >>> post a more detailed presentation about that in the mailing list later >>> today). >>> >>> While trying to use the profiler with the Pharo VM, I get the following >>> error : "PrimitiveFailed : primitive #primitiveExecutableModules in >>> VMProfilerLinuxSymbolsManager failed". (see stack trace attached). >>> >>> This plugin (VMProfileLinuxSupportPlugin) does not seem to be included >>> by default in the Pharo VM (it works with a Squeak VM). I haven't tried on >>> a mac, but I guess the plugin (VMProfileMacSupportPlugin) is missing too. >>> >>> For the moment, I am using the latest Squeak VM with my Pharo image but >>> it is not quite convenient. Would it be possible to include the 2 plugins >>> to the Pharo VM ? >>> >>> If I can be of any help, just tell me >>> Thanks! >>> >>> Sophie >>> >>> >>> >>> >>> >>> >>> <PrimitiveFailed.jpg> >>> >>> >>> >> >> >

May 10, 2017

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

by ClÃ©ment Bera

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. > > Esteban A. Maringolo > > > > > > > 2017-05-10 12:15 GMT-03:00 Nicolas Cellier <nicolas.cellier.aka.nice@ > gmail.com>: > > Hi Sophie, > > you could try and modify the plugins.int or plugins.ext files for > various > > pharo distributions and do a pull request on github opensmalltalk-vm. > > Then let Esteban accept the request or not before the release of Pharo... > > (if the build are green, there's no reason to not accept it). > > > > 2017-05-10 15:39 GMT+02:00 Max Leske <maxleske(a)gmail.com>: > >> > >> OK, I see. > >> > >> > >> On 10 May 2017, at 15:11, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > >> > >> Hi Max, > >> > >> She has already done that. The point is to add the plugins in the > default > >> Pharo VM, so everyone can use the VM profiler. We would like to have > the VM > >> profiler loadable through the Pharo catalog, but many people won't be > able > >> to use it if the default Pharo VM does not support it... > >> > >> The plugin is lightweight, so I don't see why we can't have it. > >> > >> Best, > >> > >> On Wed, May 10, 2017 at 3:00 PM, Max Leske <maxleske(a)gmail.com> wrote: > >>> > >>> Hi Sophie, > >>> > >>> You will have to compile your own VM for the moment. It's fairly easy > but > >>> you might run into problems when including the extra plugin. To build > the > >>> VM, follow the instructions on > >>> https://github.com/OpenSmalltalk/opensmalltalk-vm and read the README > and > >>> HOWTO files. Simple build example: > >>> > >>> cd ~/git/opensmalltalk-vm/build.macos32x86/pharo.cog.spur/ && ./mvm -d > >>> > >>> will build a debug VM. You'll have to modify one of the "plugins.*" > files > >>> to include the plugin. > >>> > >>> HTH, > >>> Max > >>> > >>> On 10 May 2017, at 14:36, Sophie Kaleba <sophie.kaleba(a)gmail.com> > wrote: > >>> > >>> Hi Esteban, Hi all, > >>> > >>> I am working on porting the Squeak VMProfiler to Pharo as a gsoc (I > will > >>> post a more detailed presentation about that in the mailing list later > >>> today). > >>> > >>> While trying to use the profiler with the Pharo VM, I get the following > >>> error : "PrimitiveFailed : primitive #primitiveExecutableModules in > >>> VMProfilerLinuxSymbolsManager failed". (see stack trace attached). > >>> > >>> This plugin (VMProfileLinuxSupportPlugin) does not seem to be included > by > >>> default in the Pharo VM (it works with a Squeak VM). I haven't tried > on a > >>> mac, but I guess the plugin (VMProfileMacSupportPlugin) is missing too. > >>> > >>> For the moment, I am using the latest Squeak VM with my Pharo image but > >>> it is not quite convenient. Would it be possible to include the 2 > plugins to > >>> the Pharo VM ? > >>> > >>> If I can be of any help, just tell me > >>> Thanks! > >>> > >>> Sophie > >>> > >>> > >>> > >>> > >>> > >>> > >>> <PrimitiveFailed.jpg> > >>> > >>> > >> > >> > > > >

May 10, 2017

Re: [Pharo-dev] GSoC 2017 Introduction

by Ben Coman

Welcome Myro, Good to see you getting involved early in the process. I understand you bumped into Pharo at your university, but there seems no great Pharo presence there. I'd be interested to hear a bit more about how you discovered Pharo. cheers -ben On Wed, May 10, 2017 at 4:58 AM, Myroslava Romaniuk <romaniuk(a)ucu.edu.ua> wrote: > Hello everyone > > I have been accepted as a GSoC student and my project is Advancing in Pharo > Quality Support. Here's the link to my proposal, if you have any suggestions > feel free to comment or send me an email, I would really appreciate some > feedback. Here are also links to my github and linkedin. > > In short, my project consists of several subprojects: > > updating rules (improving hints, moving the rules to corresponding packages) > advanced rule toggle (a functionality to enable/disable rules from Pharo > settings, a shortcut to ban a rule globally) > smart error handling (display errors that occured during critique > computation along the actual critiques) > match-rewrite tool (combines features of matchtool and rewritetool, improves > the process of inspecting, creating, editing and removing rules) > pre-commit quality feedback (an extension to either monticello or iceberg > that will show modified parts of a project and critiques related to them --- > if I have time) > making rules more maintainable while reporting encountered bugs > > Thanks very much for this amazing opportunity to be working with all of you, > and for the help you're providing us, GSoC students, with - on Discord and > in the mailing list. > > Looking forward to the amazing summer with the Pharo community! > > -- Myroslava

May 10, 2017

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

by Esteban A. Maringolo

If it is a plug-in, why does it need VM recompilation? Esteban A. Maringolo 2017-05-10 12:15 GMT-03:00 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: > Hi Sophie, > you could try and modify the plugins.int or plugins.ext files for various > pharo distributions and do a pull request on github opensmalltalk-vm. > Then let Esteban accept the request or not before the release of Pharo... > (if the build are green, there's no reason to not accept it). > > 2017-05-10 15:39 GMT+02:00 Max Leske <maxleske(a)gmail.com>: >> >> OK, I see. >> >> >> On 10 May 2017, at 15:11, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: >> >> Hi Max, >> >> She has already done that. The point is to add the plugins in the default >> Pharo VM, so everyone can use the VM profiler. We would like to have the VM >> profiler loadable through the Pharo catalog, but many people won't be able >> to use it if the default Pharo VM does not support it... >> >> The plugin is lightweight, so I don't see why we can't have it. >> >> Best, >> >> On Wed, May 10, 2017 at 3:00 PM, Max Leske <maxleske(a)gmail.com> wrote: >>> >>> Hi Sophie, >>> >>> You will have to compile your own VM for the moment. It's fairly easy but >>> you might run into problems when including the extra plugin. To build the >>> VM, follow the instructions on >>> https://github.com/OpenSmalltalk/opensmalltalk-vm and read the README and >>> HOWTO files. Simple build example: >>> >>> cd ~/git/opensmalltalk-vm/build.macos32x86/pharo.cog.spur/ && ./mvm -d >>> >>> will build a debug VM. You'll have to modify one of the "plugins.*" files >>> to include the plugin. >>> >>> HTH, >>> Max >>> >>> On 10 May 2017, at 14:36, Sophie Kaleba <sophie.kaleba(a)gmail.com> wrote: >>> >>> Hi Esteban, Hi all, >>> >>> I am working on porting the Squeak VMProfiler to Pharo as a gsoc (I will >>> post a more detailed presentation about that in the mailing list later >>> today). >>> >>> While trying to use the profiler with the Pharo VM, I get the following >>> error : "PrimitiveFailed : primitive #primitiveExecutableModules in >>> VMProfilerLinuxSymbolsManager failed". (see stack trace attached). >>> >>> This plugin (VMProfileLinuxSupportPlugin) does not seem to be included by >>> default in the Pharo VM (it works with a Squeak VM). I haven't tried on a >>> mac, but I guess the plugin (VMProfileMacSupportPlugin) is missing too. >>> >>> For the moment, I am using the latest Squeak VM with my Pharo image but >>> it is not quite convenient. Would it be possible to include the 2 plugins to >>> the Pharo VM ? >>> >>> If I can be of any help, just tell me >>> Thanks! >>> >>> Sophie >>> >>> >>> >>> >>> >>> >>> <PrimitiveFailed.jpg> >>> >>> >> >> >

May 10, 2017