- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] Better Code Completion

by Yuriy Tymchuk

> On 05 Oct 2015, at 22:23, stepharo <stepharo(a)free.fr> wrote: > > marcus this is about completion not syntax hilighting and the logic can be tricky. > The student that was planning to work on it used a statistcal model that shows that it was much better than the default eclipse one. > Now he just left. He was from Delft :). The idea to rely on sat can help you to understand whether you are typing a parameter (variable, literal) or a message, and whether it is the beginning of a new message or a continuation of a keyword one. Uko P.S. Iâm not AST expert, but this is how I understand some things > > Stef > > Le 5/10/15 09:25, Marcus Denker a Ã©crit : >>> On 05 Oct 2015, at 08:39, Stephan Eggermont <stephan(a)stack.nl> wrote: >>> >>> On 04/10/15 23:53, Peter UhnÃ¡k wrote: >>>> This is both rant and list of questions/notes/observations... >>>> >>>> ...but first of all: >>>> do Smalltalkers not like code completion? Because the one in Pharo is >>>> really poor and not only that nobody is doing anything about it, *but >>>> also nobody is complaining*; this leads me to believe that you either >>>> >>>> a) don't have the manpower (this is true pretty much always, so no >>>> complaints here) >>> Definitely. >>> The issue tracker has lots of interesting completion related issues, like https://pharo.fogbugz.com/f/cases/13124/NECContext-needs-plugin-design >>> >> Yes, and we need to change it to use the AST instead of Shoutâ¦ that could simplify it a lot. >> >> Marcus >> >> >> > >

Oct. 5, 2015

Re: [Pharo-dev] [Pharo-users] Better Code Completion

by stepharo

marcus this is about completion not syntax hilighting and the logic can be tricky. The student that was planning to work on it used a statistcal model that shows that it was much better than the default eclipse one. Now he just left. Stef Le 5/10/15 09:25, Marcus Denker a Ã©crit : >> On 05 Oct 2015, at 08:39, Stephan Eggermont <stephan(a)stack.nl> wrote: >> >> On 04/10/15 23:53, Peter UhnÃ¡k wrote: >>> This is both rant and list of questions/notes/observations... >>> >>> ...but first of all: >>> do Smalltalkers not like code completion? Because the one in Pharo is >>> really poor and not only that nobody is doing anything about it, *but >>> also nobody is complaining*; this leads me to believe that you either >>> >>> a) don't have the manpower (this is true pretty much always, so no >>> complaints here) >> Definitely. >> The issue tracker has lots of interesting completion related issues, like https://pharo.fogbugz.com/f/cases/13124/NECContext-needs-plugin-design >> > Yes, and we need to change it to use the AST instead of Shoutâ¦ that could simplify it a lot. > > Marcus > > >

Oct. 5, 2015

Re: [Pharo-dev] Better Code Completion

by Peter UhnÃ¡k

> > > Yes, and we need to change it to use the AST instead of Shoutâ¦ that > could simplify it a lot. > Which also means that I have to finally learn the AST... I found this https://marcusdenker.de/publications/Bera13a-OpalIWST.pdf or do we have something dedicated specifically to the AST? (Some nice overview.)

Oct. 5, 2015

Re: [Pharo-dev] Better Code Completion

by Peter UhnÃ¡k

> it does not help me much because itâs case sensitive. add to your startup settings NECPreferences caseSensitive: false (or Settings > Code Completion > Case Sensitive) > just ignore middle word suggestions. so Dict would match "Identity<Dict>ionary", but not "interdiction"? That sounds good. > I think that there are many limitations because you are editing a text and not ast. Would be nice to have a placeholders like in xCode that allow you to enter parameters one by one after youâve autocompleted multi-parameter message. The highlighter currently uses AST even as I type (if I am not mistaken), so it should be available there, but it surely requires investigation. I'm not familiar with xCode/Objective-C, but the syntax seem that they wrap methods in brackets [] so you always knows the context of the parameter, no? > I see a lots of potential doing precise code completion in the debugger/inspector/workspace based on the runtime information available. Yes, this is a good idea (although iterating on the result of the method can leave you blind again...). > Once I started digging into NECCompletion (or something like this) but its inner behavior wasn't that trivial to me. 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 :) > Yes, and we need to change it to use the AST instead of Shoutâ¦ that could simplify it a lot. Which makes me wonder whether it would make sense to start something small from scratch instead of trying to force AST into the current one. But we'll see... Peter On Mon, Oct 5, 2015 at 3:35 PM, Attila Magyar <m.magyar3(a)gmail.com> wrote: > > > do Smalltalkers not like code completion? Because the one in Pharo is > > really poor and not only that nobody is doing anything about it, but also > > nobody is complaining > > Agree, and this can be improved significantly. I see a lots of potential > doing precise code completion in the debugger/inspector/workspace based on > the runtime information available. > > > http://forum.world.st/Customised-auto-completion-to-give-priority-to-specif… > > Once I started digging into NECCompletion (or something like this) but its > inner behavior wasn't that trivial to me. > > > > -- > View this message in context: > http://forum.world.st/Better-Code-Completion-tp4853548p4853703.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Oct. 5, 2015

Re: [Pharo-dev] [Reflectivity] A small Demo: Execution Metalink Demo Plugin for Nautilus

by Alexandre Bergel

Cool!!!! Go go go! Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Oct 5, 2015, at 12:27 PM, Miguel Campusano <mcampusa(a)dcc.uchile.cl> wrote: > > Now I'm making some progress with annotating the unused temp var ;)<Screen Shot 2015-10-05 at 17.27.03.png> > > On Sun, Oct 4, 2015 at 10:58 AM Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: > >> On 04 Oct 2015, at 10:47, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >> >> >>> On 04 Oct 2015, at 10:46, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >>> >>> >>>> On 04 Oct 2015, at 08:30, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >>>> >>>> >>>>> On 03 Oct 2015, at 14:16, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >>>>> >>>>> Hi, >>>>> >>>>> With Miguel Campusano we build a small demo. >>>>> >>>> >>>> Another thing we worked onâ¦ but it needs some more work to be integratable. Visualising >>>> links using the side-icon feature of the new editor: >>> >>> would be cool to put this also to quality assistance :) >> >> and of course breakpoints ;) > > Yes! > > Marcus

Oct. 5, 2015

Re: [Pharo-dev] [Reflectivity] A small Demo: Execution Metalink Demo Plugin for Nautilus

by Miguel Campusano

Now I'm making some progress with annotating the unused temp var ;)[image: Screen Shot 2015-10-05 at 17.27.03.png] On Sun, Oct 4, 2015 at 10:58 AM Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 04 Oct 2015, at 10:47, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > On 04 Oct 2015, at 10:46, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > On 04 Oct 2015, at 08:30, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > On 03 Oct 2015, at 14:16, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > With Miguel Campusano we build a small demo. > > > Another thing we worked onâ¦ but it needs some more work to be > integratable. Visualising > links using the side-icon feature of the new editor: > > > would be cool to put this also to quality assistance :) > > > and of course breakpoints ;) > > > Yes! > > Marcus >

Oct. 5, 2015

Re: [Pharo-dev] Better Code Completion

by Attila Magyar

> do Smalltalkers not like code completion? Because the one in Pharo is > really poor and not only that nobody is doing anything about it, but also > nobody is complaining Agree, and this can be improved significantly. I see a lots of potential doing precise code completion in the debugger/inspector/workspace based on the runtime information available. http://forum.world.st/Customised-auto-completion-to-give-priority-to-specif… Once I started digging into NECCompletion (or something like this) but its inner behavior wasn't that trivial to me. -- View this message in context: http://forum.world.st/Better-Code-Completion-tp4853548p4853703.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 5, 2015

Re: [Pharo-dev] Comment of BlockClosure>>sourceNode

by Damien Cassou

Thierry Goubier <thierry.goubier(a)gmail.com> writes: > 2015-10-05 14:53 GMT+02:00 Damien Cassou <damien.cassou(a)inria.fr>: > >> The comment of the following method seems to be more an explanation of >> the implementation than of the expected behavior. Should we change that >> to something like: "Return an instance of RBBlockNode representing the >> receiver's AST." >> >> Which would completely hide the reason for going backward one step in the > bytecode. > > I'd vote for adding to the current comment. the existing comment is useful, I agree. https://pharo.fogbugz.com/f/cases/16721/Comment-of-BlockClosure-sourceNode-… -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Oct. 5, 2015

Re: [Pharo-dev] Comment of BlockClosure>>sourceNode

by Marcus Denker

> On 05 Oct 2015, at 14:58, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > > 2015-10-05 14:53 GMT+02:00 Damien Cassou <damien.cassou(a)inria.fr <mailto:damien.cassou@inria.fr>>: > The comment of the following method seems to be more an explanation of > the implementation than of the expected behavior. Should we change that > to something like: "Return an instance of RBBlockNode representing the > receiver's AST." > > Which would completely hide the reason for going backward one step in the bytecode. > > I'd vote for adding to the current comment. > Yes, add to it. the implementation comment is important: âWhy the heck -1â... Marcus

Oct. 5, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50362 Home: https://github.com/pharo-project/pharo-core

Oct. 5, 2015