May 2017 - Pharo-dev - lists.pharo.org

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

by ClÃ©ment Bera

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. > 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 11, 2017

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

by Cyril Ferlicot D.

Le 10/05/2017 Ã 21:14, Myroslava Romaniuk a Ã©crit : > 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 Hello! I can help for this one :) SSH-agent is not working well on Windows. A workaround is to set the ssh keys before using Iceberg. To do so go to Settings -> Tools -> Software Configuration Management -> Iceberg -> Use custom SSH keys You need to check the box and to give the path of your ssh keys. For example: C:\Users\YourName\.ssh\id_rsa.pub C:\Users\YourName\.ssh\id_rsa If you don't have any SSH key, check here: https://help.github.com/articles/connecting-to-github-with-ssh/ > * 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 > > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

May 10, 2017

Re: [Pharo-dev] GSoC 2017 Introduction

by Mark Rizun

> Mark: hey cheers, I'll definitely let you know if I have any questions. > For now, is there some documentation / tutorials at hand that I could have > a look at to have a better understanding of the tool? > There are four things that I could think of: 1. Paper that explains the tool in quite straightforward way (find pdf atached). 2. PharoInProgress book chapter <https://github.com/SquareBracketAssociates/PharoInProgress/tree/master/Rewr…> - the documentation with examples and some details of the implementation (note, some places may be not up to date). It is written using Pillar, so you have to compile it in order to get the pdf. 3. Blog posts <http://myfuncoding.blogspot.fr/2014/08/rewrite-tool.html?view=sidebar>. 4. There is also a short video tutorial <http://www.screencast.com/t/LCEl0hFl>. When you work on the match-rewrite tool, please let me know if you need any assistance.

May 10, 2017

Re: [Pharo-dev] GSoC 2017 Introduction

by Myroslava Romaniuk

Ben: thanks! Yeah Stef came to my uni to give lectures to Masters students and also a few workshops open for everyone, and I decided to go and see what it was, and I was immediately interested. Plus later Yuriy also came to give a few lectures and we got talking about what I could for Pharo, etc...and well, now I'm here working on this project :) Stef: very grateful that you introduced me to Pharo, and thanks for your suggestions! Re: pre-commit quality feedback --- have a look at the alternative final subproject section in my proposal, there it's explained in more detail. I will only do that if I have extra time though. Mark: hey cheers, I'll definitely let you know if I have any questions. For now, is there some documentation / tutorials at hand that I could have a look at to have a better understanding of the tool? On 10 May 2017 at 23:27, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > 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 Mark Rizun

- 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. Hi Myroslava, I would be glad to help in case you have any questions concerning rewrite tool (or anything else). Cheers, Mark

May 10, 2017

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