Better Code Completion
Locked
12
12
 
|
In fact NOC is the code of romain robbes (we took the best version
that he described in his phd)
Now the code needs some love. Stef Le 6/10/15 15:53, Nicolai Hess a
écrit :
|
|
|
In reply to this post by stepharo
> (did you know, that there is a shortcut to jump from one message send argument to another (not related to completion, but very helpful). Sadly this is gone or I couldn't find it in rubrics shortcut handling). maybe this is related to Settings > Code Browsing > AST navigation? (I've never actually tried to use this.) On Tue, Oct 6, 2015 at 8:00 PM, stepharo <[hidden email]> wrote: About an alternative way to do code completion: |
|
Well I tried to understand how NECompletion works , after a month of reading and rereading code still could not figure out how it works. I understood the basics, but the details were so difficult to really track down. Its very spagetified, a usual pharo issue, and of course undocumented. I decided to move to things that I could be more productive with. This is an area that requires the touch of a Pharo expert. On Tue, Oct 6, 2015 at 10:21 PM Peter Uhnák <[hidden email]> wrote:
|
|
|
In reply to this post by Peter Uhnak
We never used it as we could not use a good key-combination (ctr-arrow keys) due to the VM… Now I think it is not in the new editor. We should revisit that: I still like the idea to do navigation by AST structure instead of text. Marcus |
|
|
In reply to this post by kilon.alios
just fwiw, i looked at http://www.squeaksource.com/OCompletion/ and
there was a paper about ocompletion mentioned, but the access to this paper was forbidden - at least for me. but at http://users.dcc.uchile.cl/~rrobbes/p/JASE-completion.pdf there is a paper about ocompletion by the same author that explains ocompletion and with that paper ocompletion is easily understandable. werner |
|
|
On Wed, Oct 7, 2015 at 2:49 PM, Werner Kassens <[hidden email]> wrote: just fwiw, i looked at http://www.squeaksource.com/OCompletion/ and there was a paper about ocompletion mentioned, but the access to this paper was forbidden - at least for me. but at http://users.dcc.uchile.cl/~rrobbes/p/JASE-completion.pdf there is a paper about ocompletion by the same author that explains ocompletion and with that paper ocompletion is easily understandable. This is different paper, I've posted accessible link earlier: On Mon, Oct 5, 2015 at 9:59 PM, Peter Uhnák <[hidden email]> wrote:
But your link provides access to the other (paywalled) paper. :) Peter |
|
|
thanks Peter
werner On 10/07/2015 05:28 PM, Peter Uhnák wrote: > This is different paper, I've posted accessible link earlier: > > On Mon, Oct 5, 2015 at 9:59 PM, Peter Uhnák <[hidden email] > <mailto:[hidden email]>> wrote: > > > I'm currently going through > http://users.dcc.uchile.cl/~rrobbes/p/ASE2008-completion.pdf and > http://link.springer.com/article/10.1007/s10515-010-0064-x (dunno if > there's non-paywalled link) to get better idea of how it works... > and I can already see why there's limited progress :) > > > But your link provides access to the other (paywalled) paper. :) > > Peter > > |
|
|
In reply to this post by Peter Uhnak
Hi Peter,
the difference between the paper i mentioned (JASE-completion) and ASE2008-completion (both accessible) is, i think, that in the first one also the class-level code completion of ocompletion is explained. (i think that part was later added to ocompletion or so) werner |
|
|
the code should be in the image :)
Le 7/10/15 18:31, Werner Kassens a écrit : > Hi Peter, > the difference between the paper i mentioned (JASE-completion) and > ASE2008-completion (both accessible) is, i think, that in the first > one also the class-level code completion of ocompletion is explained. > (i think that part was later added to ocompletion or so) > werner > > > |
|
|
On 10/10/2015 09:50 AM, stepharo wrote:
> the code should be in the image :) Hi Stephane, of course. but sometimes i only discover some nice pharo code by reading a paper. i discovered ocompletion in the image only after having read that paper mentioned by Peter, and - thinking "yes, that should work" - after trying out ocompletion i noticed that it is indeed better than the default setting <g>. werner |
|
|
But we should improve.
It would be good to have someone taking that challenge because he would impact our all lives :) Le 10/10/15 12:22, Werner Kassens a écrit : > On 10/10/2015 09:50 AM, stepharo wrote: >> the code should be in the image :) > > Hi Stephane, > of course. but sometimes i only discover some nice pharo code by > reading a paper. i discovered ocompletion in the image only after > having read that paper mentioned by Peter, and - thinking "yes, that > should work" - after trying out ocompletion i noticed that it is > indeed better than the default setting <g>. > werner > > |
«
Return to Pharo Smalltalk Users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |