- Pharo-dev - lists.pharo.org

Regarding the autocomplete project information

by Siddharth Gupta

Hello, I am interested in taking up the autoComplete project. I played around Pharo last year too. Could you tell me places to start from, with respect to the autocomplete project. Regards Siddharth Gupta, Ph: 9871012292 Linkedin <https://www.linkedin.com/in/sidgupta234/> | Github <https://github.com/sidgupta234> | Codechef <https://www.codechef.com/users/sidgupta234> | Twitter <https://twitter.com/SidGupta234> | Facebook <https://www.facebook.com/profile.php?id=1483695876>

March 2, 2017

Re: [Pharo-dev] [ANN] Regex Tester Tool for Pharo

by Max Leske

Awesome! Thanks! > On 1 Mar 2017, at 21:32, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi, > > I wrote a little tool to test regular expressions and verify that > given samples match it. It also helps to divide an expression into > subexpressions to retrieve parts of a matched string. > > Screenshot is attached. Code, load instructions and full tutorial > on how to use it is on https://github.com/astares/Pharo-Regex-Tools > > Hope it is useful for others too. Have fun! > > Bye > T.<Tool.png>

March 1, 2017

Re: [Pharo-dev] [ANN] Regex Tester Tool for Pharo

by stepharong

Torsten Olivier in our team that is perl freaks from time to time, told me that this is sad that Pharo regexp are not compatible with the "standard" = rePlugin. And I think that his remark makes sense. I was wondering if we should not ressurect the RePlugin to make sure that users can use perlish regexp and do not feel that our world is strange. Do you have experience with re in the past? What do you think about this proposal? Stef > Hi, > > I wrote a little tool to test regular expressions and verify that > given samples match it. It also helps to divide an expression into > subexpressions to retrieve parts of a matched string. > > Screenshot is attached. Code, load instructions and full tutorial > on how to use it is on https://github.com/astares/Pharo-Regex-Tools > > Hope it is useful for others too. Have fun! > > Bye > T. -- Using Opera's mail client: http://www.opera.com/mail/

March 1, 2017

Re: [Pharo-dev] [ANN] XML Metadata Interchange (XMI) for Pharo

by stepharong

Hi torsten do you know the work of peter to generate classes out of XMI and populate models? Because it complements your approach. stef On Wed, 01 Mar 2017 22:26:05 +0100, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi, > if you work with UML, modeling tools or model data exchange often you > might know XMI - > the XML Metadata Interchange format. > I wrote a little package that makes it easier to work and browse data > based on this > format within Pharo. > For instance you can open an XMI object either from a given stream > or URL: > (XMIFile fromURL: 'http://www.omg.org/spec/UML/20131001/UML.xmi') > inspect > You can also open a file > XMIFile importFile > Code is available on https://github.com/astares/Pharo-XMI > The package includes a small GT extension allowing you to walk and dive > through the XMI > structure (see attached screenshot) and as the XMI nodes are unified it > is easy to > code some code generators or transformers in Pharo afterwards. > For instance I used this package for a simple Pharo code generator based > on Eclipse EMF models/diagrams. > Within the code you will find some examples to browse through prominent > XMI models like: > - UML Spec > => (XMIFile fromURL: 'http://www.omg.org/spec/UML/20131001/UML.xmi') > inspect > - VISUAL PARADIGM > => (XMIFile fromURL: > 'https://raw.githubusercontent.com/staruml/XMI/master/unittest-files/VP_XMI2…') > inspect > - ENTERPRISE ARCHITECT > => (XMIFile fromURL: > 'https://raw.githubusercontent.com/staruml/XMI/master/unittest-files/EA_XMI2…') > inspect > - ARCHIMATE > => (XMIFile fromURL: > 'https://www.reflektis.com/repos/archimate-3.0.xmi) inspect > Once the inspector opens you have to select the "rootNode" and then the > "Hierarchy" tab. > In Pharo 6 you can load "XMI" right from catalog. Hope the package is > useful for others too. > Bye > T. -- Using Opera's mail client: http://www.opera.com/mail/

March 1, 2017

[ANN] XML Metadata Interchange (XMI) for Pharo

by Torsten Bergmann

Hi, if you work with UML, modeling tools or model data exchange often you might know XMI - the XML Metadata Interchange format. I wrote a little package that makes it easier to work and browse data based on this format within Pharo. For instance you can open an XMI object either from a given stream or URL: (XMIFile fromURL: 'http://www.omg.org/spec/UML/20131001/UML.xmi') inspect You can also open a file XMIFile importFile Code is available on https://github.com/astares/Pharo-XMI The package includes a small GT extension allowing you to walk and dive through the XMI structure (see attached screenshot) and as the XMI nodes are unified it is easy to code some code generators or transformers in Pharo afterwards. For instance I used this package for a simple Pharo code generator based on Eclipse EMF models/diagrams. Within the code you will find some examples to browse through prominent XMI models like: - UML Spec => (XMIFile fromURL: 'http://www.omg.org/spec/UML/20131001/UML.xmi') inspect - VISUAL PARADIGM => (XMIFile fromURL: 'https://raw.githubusercontent.com/staruml/XMI/master/unittest-files/VP_XMI2…') inspect - ENTERPRISE ARCHITECT => (XMIFile fromURL: 'https://raw.githubusercontent.com/staruml/XMI/master/unittest-files/EA_XMI2…') inspect - ARCHIMATE => (XMIFile fromURL: 'https://www.reflektis.com/repos/archimate-3.0.xmi) inspect Once the inspector opens you have to select the "rootNode" and then the "Hierarchy" tab. In Pharo 6 you can load "XMI" right from catalog. Hope the package is useful for others too. Bye T.

March 1, 2017

[ANN] Regex Tester Tool for Pharo

by Torsten Bergmann

Hi, I wrote a little tool to test regular expressions and verify that given samples match it. It also helps to divide an expression into subexpressions to retrieve parts of a matched string. Screenshot is attached. Code, load instructions and full tutorial on how to use it is on https://github.com/astares/Pharo-Regex-Tools Hope it is useful for others too. Have fun! Bye T.

March 1, 2017

Re: [Pharo-dev] [squeak-dev] Re: [vwnc] Does anyone have a "new" string literal?

by DavidLeibs

Let me add some more motivation and background for the discussion. I responded to stepharong(a)free.fr questions by mail yesterday but it didn't wind up on the forum. Sorry about that. http://www.erights.org/elang/quasi/overview.html Provides very good background for quasi-liberals. I believe this work lead to the ES6 solution by way of Mark Miller. As to macros I would posit that you have been using them in Smalltalk80 all along without the benefit of having the capability for yourself. There are a classic set of selectors that get special processing by the compiler. "to: do:" is an example of one. It gets turned into a while loop by AST transformation. These special selectors that are really macros are known to the compiler in a special table. A proper macro system opens the capability up everyone. As to 30 years without noticing that macros were needed, I would say they are long over due. I needed them back in 1997 when Adele Goldberg and I had a company called Neometron. We used them for for a large system that had thousands of templates in a template language which had escapes Smalltalk80 code embedded within. Also embedded within the tempting code and Smalltalk code was SQL code. This was allowed to be recursive so it was a little language free for all. We did not want string concatenation style coding with errors only found at run time. By having a Smalltalk80 with macros and quasi-literal little languages we and our non programmer users continued to compile method by method in the browser as usual but all the errors in template or sql syntax were found at compile time. There were no external files and everything continued to work with Change Sets and Change List technology that allowed recovering after a crash. The compile time processing by way of compiler staging plugins also allowed for an order of magnitude performance increase because there was a lot of evaluations that could be done in advance. By doing the work properly in the parser and compiler and making sure code transformations tracked source code offsets proper single stepping in the debugger was preserved. Of course if really aggressive rewriting was done you would sometimes have to debug in the expansion but we emitted code to help the debugger with macros and custom optimizations. The need to debug some macros in the expansion is a very old unsolved problem. Sadly, I was unable to convince Eliot and Steve Dahl to incorporate the work into Visualworks 20 years ago. Also sadly, I don't spend a lot of effort arguing with people that don't understand the need for some technology I see as useful. I have continually had to wait years before the time was right. :-) I know this will sound a bit "Snarky" but for more examples I suggest taking a look at 60 years of Lisp. Stochastic sampeling of the corpus should be revealing. :-) And now for a appeal to authority, "Lisp isn't a language, it's a building material." - Alan Kay and in conclusion: Simple quasi-literally are relatively easy and can be done with out being too disruptive. A real macro system takes very careful design that leads to compiler plugins that can go way beyond macros and open up a world compile time meta programming and the wonderful world of application dependent optimizations. cheers, -David (voice from the distant past) Leibs -- View this message in context: http://forum.world.st/Re-vwnc-Does-anyone-have-a-new-string-literal-tp46670… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 1, 2017

Re: [Pharo-dev] strange idea about slots

by Richard Sargent

Ben Coman wrote > I'm not sure I'm thinking straight, but I wonder... > Can you put Slots inside an Association? > > For example, could have two slots x and y, > and then be able to do the following... > > (x -> y) substitute: (1 -> 2). > self assert: x equals: 1. > self assert: y equals: 2. > > So the association method #substitute: > assigns into the relevant variables. > > And even better if you could do... > (x -> y) := (1 -> 2). > and... > { x. y ) := #(1 2). > > For example, when you're hacking fast and want to return two values from a > method without mucking around with creating an object for this, it might > look like... > myCalc > ^#(1 2) > > but instead of... > result := inst myCalc. > x := result at: 1. > y := result at: 2. > > you could do... > { x . y } := inst myCalc. I see this often, and even practice it sometimes. :-( But every time I think about it, I get frustrated. We have no problem creating instances of an existing class (Array, Association, even Dictionary) to return multiple values from a method. However, I always feel like doing so abdicates our responsibilities. At least with a Dictionary, the values are properly identified rather than stuffed into an anonymous collection or mis-represented as key and value. Ultimately, I always conclude that this anti-pattern indicates a modelling failure. Why not create a class which does the computation, holds the several desired result objects, and provides the ability to answer them? Worst case, you have a simple computation that produces more than one result object. In such a case, create a data transfer object (no real behaviour) that holds the results in appropriately named instance variables. There seems to be a fear of creating new classes. Don't let that rule your designs. > cheers -ben -- View this message in context: http://forum.world.st/strange-idea-about-slots-tp4936623p4936691.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 1, 2017

Re: [Pharo-dev] Google Summer of Code 2017: Call for mentors for Pharo Consortium

by Max Leske

It seems that I canât. Itâs not in the list of channels, I guess I have to be invited. > On 1 Mar 2017, at 20:19, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > Please join the #gsoc-planning channel on Slack ! > > On Wed, Mar 1, 2017 at 8:16 PM, Max Leske <maxleske(a)gmail.com> wrote: >> Good stuff! >> >> Iâm up for mentoring. >> >>> On 1 Mar 2017, at 13:45, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: >>> >>> Heartiest Congratulations ! >>> >>> Pharo Consortium has been selected as a mentor organisation for Google >>> Summer of Code 2017. >>> >>> Google Summer of Code is a global program focused on introducing >>> students to open source software development. >>> >>> Students work on a 3 month programming project with an open source >>> organisation during their break from university. Read more at >>> https://summerofcode.withgoogle.com/ >>> >>> How the program works ? >>> >>> Organizations: >>> Open source projects apply to be mentor organizations. Once accepted, >>> organizations discuss possible ideas with students and then decide on >>> the proposals they wish to mentor for the summer. They provide mentors >>> to help guide each student through the program. >>> >>> Mentors: >>> Existing contributors with the organizations can choose to mentor a >>> student project. Mentors and students work together to determine >>> appropriate milestones and requirements for the summer. Mentor >>> interaction is a vital part of the program. A mentor may propose or >>> endorse a project and each project has to be about Pharo or its >>> ecosystem (e.g., a library). Projects will be mentored by one or more >>> mentors and executed by one student. >>> >>> Students: >>> Students contact the mentor organizations they want to work with and >>> write up a project proposal for the summer. If accepted, students >>> spend a month integrating with their organizations prior to the start >>> of coding. Students then have three months to code, meeting the >>> deadlines agreed upon with their mentors. Student coding period: May >>> 30 - Aug 29 (Entire timeline can be viewed at: >>> https://summerofcode.withgoogle.com/how-it-works/#timeline) Student >>> stipend: https://developers.google.com/open-source/gsoc/help/student-stipends >>> >>> We are currently at the phase of identifying mentors and projects. The >>> next phases will be about students selecting projects, and the >>> community selecting the projects with their associated mentors and >>> students which will be sponsored by the GSOC program. >>> >>> How to register ? >>> Simply by replying to this email and joining the Slack channel... to >>> have more discussion about what project the mentor will take up, what >>> she/he wants at the end of the coding period and then we can invite >>> them to the GSoC org dashboard). >>> >>> Hence, we invite regular & enthusiastic Pharo contributors to be a >>> mentor with Pharo Consortium for GSoC 2017: >>> >>> 1. Kindly respond on this thread if you'd like to be a mentor, or wish >>> to propose a project. >>> >>> An existing list of projects is already available here: >>> http://gsoc.pharo.org/ and we already have a handful of projects and >>> mentors chosen. Feel free to collaborate with existing mentors as >>> well. >>> >>> 2. Join dedicated channels, #gsoc-students for general interactions >>> with students & #gsoc-planning channel only for GSOC admins and >>> mentors on Pharo slack. In order to get an invitation for >>> pharoproject.slack.com visit the URL here: >>> http://slackinvites.pharo.org/ >>> >>> 3. Please open relevant issues and make a roadmap of the projects >>> being mentored by you so that students can start contributing to them >>> already. If you want to mentor a project and there is no open-source >>> repository at the moment, please built one ASAP. >>> >>> 4. If you know any students that might be interested to work on Pharo >>> during the summer and be a part of GSoC as well, please ask him/her to >>> start contributing to the Pharo projects, discuss their proposal, >>> follow instructions that shall be posted soon in this mailing thread >>> and submit their application by April 3, 2017. >>> We don't know the number of slots attributed by Google to Pharo org, >>> but the more students proposal we will receive, the more slots will be >>> attributed to us. >>> >>> We remind you about the mentor responsibilities: >>> >>> ... to your Org Admins >>> >>> - Communicate availability and interaction expectations >>> - Inform when mentoring capacity will be reduced, as early as possible >>> (e.g., family, health, vacation) >>> - Inform when there is an issue with a student >>> - Lacking communication, activity, visibility (MIA), or progress >>> - Participant Agreement violations (e.g., plagiarism, harassment, fraud) >>> - Bad fit or stepping down >>> - Formally evaluate student participation. >>> - Communicate with admin and student before failing >>> >>> ... to your Students >>> >>> - Help and/or teach the student >>> - how to be a part of your community >>> - communicate more effectively and in the open >>> - work with your orgâs preferred communication channel (IRC, Slack, etc) >>> - use your orgâs version control system >>> - ask good questions and get answers to their questions >>> - provide convincing technical argument and constructive discussion >>> - be independently motivated and productive >>> - solve difficult technical problems >>> - Keep track of their progress, keep student informed as to their status >>> - Communicate on a regular basis, once a week or better (for GSoC) >>> - Give constructive feedback, be patient, and be respectful >>> - Respond to questions within 24 hours (occasionally under 36 hours is ok) >>> - Establish realistic work objectives and timeline expectations >>> - Re-evaluate scope with student when significantly ahead of or behind >>> expectations >>> - Work with devs and community to facilitate acceptance of student work >>> >>> Read more about responsibilities here: >>> https://developers.google.com/open-source/gsoc/help/responsibilities >>> >>> Looking forward to a great guided summer by the talented mentors of >>> our organisation. >>> >>> Warm Regards >>> Pharo Organisation Admins >>> (Alexandre Bergel, Jigyasa Grover, Serge Stinckwich & Yuriy Tymchuk) >>> >> >> > > > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ >

March 1, 2017

Re: [Pharo-dev] Google Summer of Code 2017: Call for mentors for Pharo Consortium

by Serge Stinckwich

Please join the #gsoc-planning channel on Slack ! On Wed, Mar 1, 2017 at 8:16 PM, Max Leske <maxleske(a)gmail.com> wrote: > Good stuff! > > Iâm up for mentoring. > >> On 1 Mar 2017, at 13:45, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: >> >> Heartiest Congratulations ! >> >> Pharo Consortium has been selected as a mentor organisation for Google >> Summer of Code 2017. >> >> Google Summer of Code is a global program focused on introducing >> students to open source software development. >> >> Students work on a 3 month programming project with an open source >> organisation during their break from university. Read more at >> https://summerofcode.withgoogle.com/ >> >> How the program works ? >> >> Organizations: >> Open source projects apply to be mentor organizations. Once accepted, >> organizations discuss possible ideas with students and then decide on >> the proposals they wish to mentor for the summer. They provide mentors >> to help guide each student through the program. >> >> Mentors: >> Existing contributors with the organizations can choose to mentor a >> student project. Mentors and students work together to determine >> appropriate milestones and requirements for the summer. Mentor >> interaction is a vital part of the program. A mentor may propose or >> endorse a project and each project has to be about Pharo or its >> ecosystem (e.g., a library). Projects will be mentored by one or more >> mentors and executed by one student. >> >> Students: >> Students contact the mentor organizations they want to work with and >> write up a project proposal for the summer. If accepted, students >> spend a month integrating with their organizations prior to the start >> of coding. Students then have three months to code, meeting the >> deadlines agreed upon with their mentors. Student coding period: May >> 30 - Aug 29 (Entire timeline can be viewed at: >> https://summerofcode.withgoogle.com/how-it-works/#timeline) Student >> stipend: https://developers.google.com/open-source/gsoc/help/student-stipends >> >> We are currently at the phase of identifying mentors and projects. The >> next phases will be about students selecting projects, and the >> community selecting the projects with their associated mentors and >> students which will be sponsored by the GSOC program. >> >> How to register ? >> Simply by replying to this email and joining the Slack channel... to >> have more discussion about what project the mentor will take up, what >> she/he wants at the end of the coding period and then we can invite >> them to the GSoC org dashboard). >> >> Hence, we invite regular & enthusiastic Pharo contributors to be a >> mentor with Pharo Consortium for GSoC 2017: >> >> 1. Kindly respond on this thread if you'd like to be a mentor, or wish >> to propose a project. >> >> An existing list of projects is already available here: >> http://gsoc.pharo.org/ and we already have a handful of projects and >> mentors chosen. Feel free to collaborate with existing mentors as >> well. >> >> 2. Join dedicated channels, #gsoc-students for general interactions >> with students & #gsoc-planning channel only for GSOC admins and >> mentors on Pharo slack. In order to get an invitation for >> pharoproject.slack.com visit the URL here: >> http://slackinvites.pharo.org/ >> >> 3. Please open relevant issues and make a roadmap of the projects >> being mentored by you so that students can start contributing to them >> already. If you want to mentor a project and there is no open-source >> repository at the moment, please built one ASAP. >> >> 4. If you know any students that might be interested to work on Pharo >> during the summer and be a part of GSoC as well, please ask him/her to >> start contributing to the Pharo projects, discuss their proposal, >> follow instructions that shall be posted soon in this mailing thread >> and submit their application by April 3, 2017. >> We don't know the number of slots attributed by Google to Pharo org, >> but the more students proposal we will receive, the more slots will be >> attributed to us. >> >> We remind you about the mentor responsibilities: >> >> ... to your Org Admins >> >> - Communicate availability and interaction expectations >> - Inform when mentoring capacity will be reduced, as early as possible >> (e.g., family, health, vacation) >> - Inform when there is an issue with a student >> - Lacking communication, activity, visibility (MIA), or progress >> - Participant Agreement violations (e.g., plagiarism, harassment, fraud) >> - Bad fit or stepping down >> - Formally evaluate student participation. >> - Communicate with admin and student before failing >> >> ... to your Students >> >> - Help and/or teach the student >> - how to be a part of your community >> - communicate more effectively and in the open >> - work with your orgâs preferred communication channel (IRC, Slack, etc) >> - use your orgâs version control system >> - ask good questions and get answers to their questions >> - provide convincing technical argument and constructive discussion >> - be independently motivated and productive >> - solve difficult technical problems >> - Keep track of their progress, keep student informed as to their status >> - Communicate on a regular basis, once a week or better (for GSoC) >> - Give constructive feedback, be patient, and be respectful >> - Respond to questions within 24 hours (occasionally under 36 hours is ok) >> - Establish realistic work objectives and timeline expectations >> - Re-evaluate scope with student when significantly ahead of or behind >> expectations >> - Work with devs and community to facilitate acceptance of student work >> >> Read more about responsibilities here: >> https://developers.google.com/open-source/gsoc/help/responsibilities >> >> Looking forward to a great guided summer by the talented mentors of >> our organisation. >> >> Warm Regards >> Pharo Organisation Admins >> (Alexandre Bergel, Jigyasa Grover, Serge Stinckwich & Yuriy Tymchuk) >> > > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

March 1, 2017