- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Issue Tracker] Problem with Spam

by Sven Van Caekenberghe

I guess these are anonymous submissions ? Can't this (for now at least) not be restricted to actual users that need to authenticate first ? > On 26 Jan 2018, at 10:09, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > Since some days we get ~20 spam cases per day on the issue tracker. > > -> I have asked on the Forums what we can do > -> As long as there is no solution, I am closing them the morning. > > Marcus >

Jan. 26, 2018

[Issue Tracker] Problem with Spam

by Marcus Denker

Hi, Since some days we get ~20 spam cases per day on the issue tracker. -> I have asked on the Forums what we can do -> As long as there is no solution, I am closing them the morning. Marcus

Jan. 26, 2018

Re: [Pharo-dev] Iceberg Loading issue

by Alistair Grant

Hi Vincent, Every time I've seen this question asked, the answer has been to checkout the branch that you want and then "Reload All" from the list of packages. Cheers, Alistair On 26 January 2018 at 00:42, <Vincent.Blondeau(a)lamresearch.com> wrote: > Hi, > > I am encountering some problems with Iceberg on the latest version. > > I want to load the commits I just made on a branch on my Pharo fork, let's say "21124". I set the local repo to the current version of my Pharo image, i.e. the development branch (commit 0dbf86). > Thanks to the iceberg interface, I change the current branch to "21124", there are 12 commits that are incoming. > Then, I then do "Pull incoming commit" to load them. > But after a few moment, instead of loading only the delta between the development branch and the "21124" one, iceberg goes further in the commit history and wants to load 174 commits... Including one that does not load. > > By debugging, it seems that there is a problem with LGitRepository>>fastForward:, the result of "self lookup: 'FETCH_HEAD'" gives not the good commit i.e. the one of the development branch (commit 0dbf86), but instead the one of "I do not what". > > Does this issue is known? And how can I bypass it or solve it? > > Thanks, > > Vincent

Jan. 26, 2018

Re: [Pharo-dev] Code Completion

by Tudor Girba

Excellent summary! Doru > On Jan 26, 2018, at 8:51 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi Myroslava, > > some infos: > > Initially for Squeak there was "eCompletion" written by Ruben Bakker. According to the package "eCompletion is code > completion inspired by eclipse", it required MCInstaller, Shout 4 and RoelTyper. > http://uncomplex.net/ecompletion/ > > Back in Squeak "Shout" was used to have syntax highlighting as you type. > RoelTyper is a fast type reconstructor for Smalltalk (name comes from its Author Roel Wuyts) > https://roelwuyts.be/roeltyper/index.html > https://www.youtube.com/watch?v=CvKTCSv7s8s > > Later oCompletion followed - "OCompletion builds on ECompletion and improves its accuracy." > http://www.squeaksource.com/OCompletion/ > http://www.inf.unisi.ch/phd/robbes/papers/ASE2008-completion.pdf > OCompletion uses (based on recent activity) considerably improves the accuracy of code completion. That is, > the actual selector you want to insert is usually in the top 3 matches OCompletion proposes. > https://news.squeak.org/tag/ocompletion/ > > A paper you should read is > https://users.dcc.uchile.cl/~rrobbes/p/JASE-completion.pdf > OCompletion is a re-working of the venerable eCompletion package, based on research done by Romain Robbes and Michele Lanza. > > OCompletion is in Pharo since Pharo 2.0 > There already was a discussion about better completion back in 2015 > https://www.mail-archive.com/pharo-users@lists.pharo.org/msg14835.html based on the need for pluggability > (https://pharo.fogbugz.com/f/cases/13124/NECContext-needs-plugin-design) and basing it on AST instead of Shout > https://pharo.fogbugz.com/f/cases/10219/Completion-enter-on-accept-awkwardn… > > So NECController is the old code and NOCController (there was a setting to change from one to the other) > ECompletion was just a list of matching classes/selectors. OCompletion added some candy like showing first last typed entries > (with some other heuristic). > > http://www.jarober.com/blog/blogView?showComments=true&title=ST+4U+46%3A+Au… > > > What I always liked in Eclipse compared to Pharo is that you can code complete an expression and > the parameters are visualized with a rectangle and by "tabbing" you can fill each of them: > > https://www.youtube.com/watch?v=OMbVQcZ0gV8 > > Also one can do own code templates who are used in the completion then: > https://help.eclipse.org/mars/index.jsp?topic=%2Forg.eclipse.cdt.doc.user%2… > > > Some other alternatives: CACHECA is a cache language model based code suggestion tool (https://github.com/christinef/CACHECA) for Eclipse > which could be seen in https://www.youtube.com/watch?v=3INk0N3JNtc > > RubyMine code completion for Ruby > https://www.jetbrains.com/help/ruby/auto-completing-code.html > > > Thanks > T. > > Gesendet: Donnerstag, 25. Januar 2018 um 22:52 Uhr > Von: "Myroslava Romaniuk" <romaniuk(a)ucu.edu.ua> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: [Pharo-dev] Code Completion > > Hi, I'm Myroslava > > Some of you might remember how last year I did GSoC and worked on Renraku / Quality Assistant with Yuriy. > > This year Stephane suggested several projects I could work on, and one of them is improving code completion in Pharo, in particular ecompletion. Could you recommend any resources that would help me better understand how it works? I'd also like to know what's the difference between ecompletion and ocompletion, and what's NOC and NEC completion, as it doesn't seem very clear to me so far? > > If any of you worked on it and can help me get started, I would really appreciate it. > > Thanks > -- www.tudorgirba.com www.feenk.com "It's not how it is, it is how we see it."

Jan. 26, 2018

Re: [Pharo-dev] Code Completion

by Torsten Bergmann

Hi Myroslava, some infos: Â Initially for Squeak there was "eCompletion" written by Ruben Bakker. According to the package "eCompletion is code completion inspired by eclipse", it required MCInstaller, Shout 4 and RoelTyper. http://uncomplex.net/ecompletion/ Back in Squeak "Shout" was used to have syntax highlighting as you type. RoelTyper is a fast type reconstructor for Smalltalk (name comes from its Author Roel Wuyts) https://roelwuyts.be/roeltyper/index.html https://www.youtube.com/watch?v=CvKTCSv7s8s Later oCompletion followed - "OCompletion builds on ECompletion and improves its accuracy." http://www.squeaksource.com/OCompletion/ http://www.inf.unisi.ch/phd/robbes/papers/ASE2008-completion.pdf OCompletion uses (based on recent activity) considerably improves the accuracy of code completion. That is, the actual selector you want to insert is usually in the top 3 matches OCompletion proposes. https://news.squeak.org/tag/ocompletion/ A paper you should read is https://users.dcc.uchile.cl/~rrobbes/p/JASE-completion.pdf OCompletion is a re-working of the venerable eCompletion package, based on research done by Romain Robbes and Michele Lanza. OCompletion is in Pharo since Pharo 2.0 There already was a discussion about better completion back in 2015 https://www.mail-archive.com/pharo-users@lists.pharo.org/msg14835.html based on the need for pluggability (https://pharo.fogbugz.com/f/cases/13124/NECContext-needs-plugin-design) and basing it on AST instead of Shout https://pharo.fogbugz.com/f/cases/10219/Completion-enter-on-accept-awkwardn… So NECController is the old code and NOCController (there was a setting to change from one to the other) ECompletion was just a list of matching classes/selectors. OCompletion added some candy like showing first last typed entries (with some other heuristic). http://www.jarober.com/blog/blogView?showComments=true&title=ST+4U+46%3A+Au… What I always liked in Eclipse compared to Pharo is that you can code complete an expression and the parameters are visualized with a rectangle and by "tabbing" you can fill each of them: https://www.youtube.com/watch?v=OMbVQcZ0gV8 Also one can do own code templates who are used in the completion then: https://help.eclipse.org/mars/index.jsp?topic=%2Forg.eclipse.cdt.doc.user%2… Some other alternatives: CACHECA is a cache language model based code suggestion tool (https://github.com/christinef/CACHECA) for Eclipse which could be seen in https://www.youtube.com/watch?v=3INk0N3JNtc RubyMine code completion for Ruby https://www.jetbrains.com/help/ruby/auto-completing-code.html Thanks T. Gesendet:Â Donnerstag, 25. Januar 2018 um 22:52 Uhr Von:Â "Myroslava Romaniuk" <romaniuk(a)ucu.edu.ua> An:Â "Pharo Development List" <pharo-dev(a)lists.pharo.org> Betreff:Â [Pharo-dev] Code Completion Hi, I'm Myroslava Â Some of you might remember how last year I did GSoC and worked on Renraku / Quality Assistant with Yuriy. Â This year Stephane suggested several projects I could work on, and one of them is improving code completion in Pharo, in particular ecompletion. Could you recommend any resources that would help me better understand how it works? I'd also like to know what's the difference between ecompletion and ocompletion, and what's NOC and NEC completion, as it doesn't seem very clear to me so far? Â If any of you worked on it and can help me get started, I would really appreciate it. Â Thanks

Jan. 26, 2018

Re: [Pharo-dev] How to get rid of empty XML nodes?

by monty

See #removeAllFormattingNodes and its comment in the latest version. And instances of SAXHandler and subclasses are meant to be created with #on: (or another "instance creation" message), _not #new_, otherwise they won't be properly initialized. The class comment is clear about this, but I should have overridden #new to raise an error like Stream does. Your misuse was helpful in bringing this to my attention, and I added a Stream-like #new implementation to SAXHandler. > Sent: Friday, December 08, 2017 at 9:21 AM > From: "Stephane Ducasse" <stepharo.self(a)gmail.com> > To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Subject: Re: [Pharo-dev] How to get rid of empty XML nodes? > > Hi monty > > > On Fri, Dec 8, 2017 at 9:03 AM, monty <monty2(a)programmer.net> wrote: > > By "empty XML nodes," do you mean whitespace-only string nodes? > > Yes > > > Those are included because all in-element whitespace is assumed significant by the spec: https://www.w3.org/TR/xml/#sec-white-space > > I know. There was a discussion a while ago. I just lost a couple of > hours understanding that :( > > But this is a super super super annoying practices. > We had to test each nodes to see if it is a empty nodes so it makes > everything a lot more complex without real justification > beside the fact that these standardizers probably never implemented > some real cases. > This standard is a really out of reality from that perspective. > > > The exception is if the element is declared in the DTD as only having element children ("element content"): https://www.w3.org/TR/xml/#dt-elemcontent > > Well the XML files that I had (I did not choose XML because I would > have prefer JSON :) ), had no DTD :( > > So at the end of the day, this wonderful standard puts all the stress > and burden to people. > > > > > For example, if you declare an element like this: > > > > <!ELEMENT one (two,three*,four?)> > > > > Any whitespace around a "two," "three," or "four" element child of a "one" element is insignificant and ignored (unless #preservesIgnorableWhitespace: is true). Other parsers, like LibXML2 and Xerces, behave the same way. > > > > I'll see if I can come up with some easier way to deal with this, like an optional parser setting, new enumeration methods, or maybe a tree transformation. > > It would be A HUGE PLUS!!!!!!!!!!!!!!!!!! > > > Because reality is that people have XML files with just nodes and no > empty nodes and they are forced to > Let me know because I could try. > > I was showing how to use Pharo to import code to pharo learners and > this was a big drag. > > Stef > > > I tried to set some values in the parser but it did not work. > BTW I saw that the configuration logic forces to write the following > > | parser doc visitor | > parser := XMLDOMParser new > on: self xmlContents; > preservesIgnorableWhitespace: true. > > and not > > | parser doc visitor | > parser := XMLDOMParser new > preservesIgnorableWhitespace: true. > on: self xmlContents; > > > > > >> Sent: Tuesday, December 05, 2017 at 8:29 AM > >> From: "Stephane Ducasse" <stepharo.self(a)gmail.com> > >> To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > >> Subject: [Pharo-dev] How to get rid of empty XML nodes? > >> > >> )Hi > >> > >> we are manipulating an XML document and I would like to get rid of the > >> spurious empty string. > >> We saw that the gt panes are doing it. > >> > >> (aNodeWithElements isStringNode > >> and: [aNodeWithElements isEmpty > >> or: [aNodeWithElements isWhitespace]] > >> > >> Is there a way not to produce empty nodes? > >> Is there a simple way not to have to handle them > >> > >> Now each time we are dealing with a node with have to check. > >> > >> Stef > >> > >> > > > >

Jan. 26, 2018

Re: [Pharo-dev] Iceberg Loading issue

by Vincent BLONDEAU

Hi Max, Yes, I tried that too: pulling the branch outside Pharo, set it to the 21124 branch head, then launch Pharo and run the pull of incoming commits from Pharo. Also, loading one commit at the time works, but you cannot do it for a lot of commits, the list of commits is very slow to refresh (at least under Windows). Cheers, Vincent From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Max Leske Sent: jeudi 25 janvier 2018 22:15 To: Pharo Development List Subject: Re: [Pharo-dev] Iceberg Loading issue Hi Vincent, Possibly a problem with updating FETCH_HEAD. Does it work when you perform only the pull operation from Pharo (i.e., check out the branch on the command line)? Cheers, Max On 26 January 2018 at 00:43:40, vincent.blondeau(a)lamresearch.com <mailto:vincent.blondeau@lamresearch.com> (vincent.blondeau(a)lamresearch.com <mailto:vincent.blondeau@lamresearch.com> ) wrote: Hi, I am encountering some problems with Iceberg on the latest version. I want to load the commits I just made on a branch on my Pharo fork, let's say "21124". I set the local repo to the current version of my Pharo image, i.e. the development branch (commit 0dbf86). Thanks to the iceberg interface, I change the current branch to "21124", there are 12 commits that are incoming. Then, I then do "Pull incoming commit" to load them. But after a few moment, instead of loading only the delta between the development branch and the "21124" one, iceberg goes further in the commit history and wants to load 174 commits... Including one that does not load. By debugging, it seems that there is a problem with LGitRepository>>fastForward:, the result of "self lookup: 'FETCH_HEAD'" gives not the good commit i.e. the one of the development branch (commit 0dbf86), but instead the one of "I do not what". Does this issue is known? And how can I bypass it or solve it? Thanks, Vincent

Jan. 26, 2018

Re: [Pharo-dev] Iceberg Loading issue

by Max Leske

Hi Vincent, Possibly a problem with updating FETCH_HEAD. Does it work when you perform only the pull operation from Pharo (i.e., check out the branch on the command line)? Cheers, Max On 26 January 2018 at 00:43:40, vincent.blondeau(a)lamresearch.com ( vincent.blondeau(a)lamresearch.com) wrote: Hi, I am encountering some problems with Iceberg on the latest version. I want to load the commits I just made on a branch on my Pharo fork, let's say "21124". I set the local repo to the current version of my Pharo image, i.e. the development branch (commit 0dbf86). Thanks to the iceberg interface, I change the current branch to "21124", there are 12 commits that are incoming. Then, I then do "Pull incoming commit" to load them. But after a few moment, instead of loading only the delta between the development branch and the "21124" one, iceberg goes further in the commit history and wants to load 174 commits... Including one that does not load. By debugging, it seems that there is a problem with LGitRepository>>fastForward:, the result of "self lookup: 'FETCH_HEAD'" gives not the good commit i.e. the one of the development branch (commit 0dbf86), but instead the one of "I do not what". Does this issue is known? And how can I bypass it or solve it? Thanks, Vincent

Jan. 26, 2018

Iceberg Loading issue

by Vincent.Blondeau＠lamresearch.com

Hi, I am encountering some problems with Iceberg on the latest version. I want to load the commits I just made on a branch on my Pharo fork, let's say "21124". I set the local repo to the current version of my Pharo image, i.e. the development branch (commit 0dbf86). Thanks to the iceberg interface, I change the current branch to "21124", there are 12 commits that are incoming. Then, I then do "Pull incoming commit" to load them. But after a few moment, instead of loading only the delta between the development branch and the "21124" one, iceberg goes further in the commit history and wants to load 174 commits... Including one that does not load. By debugging, it seems that there is a problem with LGitRepository>>fastForward:, the result of "self lookup: 'FETCH_HEAD'" gives not the good commit i.e. the one of the development branch (commit 0dbf86), but instead the one of "I do not what". Does this issue is known? And how can I bypass it or solve it? Thanks, Vincent

Jan. 25, 2018

Code Completion

by Myroslava Romaniuk

Hi, I'm Myroslava Some of you might remember how last year I did GSoC and worked on Renraku / Quality Assistant with Yuriy. This year Stephane suggested several projects I could work on, and one of them is improving code completion in Pharo, in particular ecompletion. Could you recommend any resources that would help me better understand how it works? I'd also like to know what's the difference between ecompletion and ocompletion, and what's NOC and NEC completion, as it doesn't seem very clear to me so far? If any of you worked on it and can help me get started, I would really appreciate it. Thanks

Jan. 25, 2018