[Pharo-project] Completion
I don't particularly like the current completion mechanism in pharo: - the OCompletion (or what it is called) only displays a limited number of selectors - the second completion (which is complete!) using CMD-Q is in many cases more helpful Could we combine these two? Simply concatenate the two lists and we're done! Where is the place to look for that? best cami
please go :) NEController and NOController would be the place On Aug 3, 2012, at 6:21 PM, Camillo Bruni <camillobruni@gmail.com> wrote:
I don't particularly like the current completion mechanism in pharo:
- the OCompletion (or what it is called) only displays a limited number of selectors - the second completion (which is complete!) using CMD-Q is in many cases more helpful
Could we combine these two? Simply concatenate the two lists and we're done! Where is the place to look for that?
best cami
When using OCompletion, if you scroll to the bottom of the list (with keydown), you should get the ECompletion list. Cheers, Doru On 3 Aug 2012, at 18:42, Esteban Lorenzano wrote:
please go :)
NEController and NOController would be the place
On Aug 3, 2012, at 6:21 PM, Camillo Bruni <camillobruni@gmail.com> wrote:
I don't particularly like the current completion mechanism in pharo:
- the OCompletion (or what it is called) only displays a limited number of selectors - the second completion (which is complete!) using CMD-Q is in many cases more helpful
Could we combine these two? Simply concatenate the two lists and we're done! Where is the place to look for that?
best cami
-- www.tudorgirba.com "No matter how many recipes we know, we still value a chef."
yep we just figured that out... so now we will only have one list which displays all the matches. the first 6 are by priority, the rest sorted alphabetically. this will hopefully be much more productive On 2012-08-03, at 21:54, Tudor Girba <tudor@tudorgirba.com> wrote:
When using OCompletion, if you scroll to the bottom of the list (with keydown), you should get the ECompletion list.
Cheers, Doru
On 3 Aug 2012, at 18:42, Esteban Lorenzano wrote:
please go :)
NEController and NOController would be the place
On Aug 3, 2012, at 6:21 PM, Camillo Bruni <camillobruni@gmail.com> wrote:
I don't particularly like the current completion mechanism in pharo:
- the OCompletion (or what it is called) only displays a limited number of selectors - the second completion (which is complete!) using CMD-Q is in many cases more helpful
Could we combine these two? Simply concatenate the two lists and we're done! Where is the place to look for that?
best cami
-- www.tudorgirba.com
"No matter how many recipes we know, we still value a chef."
Please keep in mind that the reason for showing only the OCompletion list at first was speed. If you are using both at the same time, you might get a performance penalty. Cheers, Doru On 3 Aug 2012, at 21:55, Camillo Bruni wrote:
yep we just figured that out... so now we will only have one list which displays all the matches. the first 6 are by priority, the rest sorted alphabetically.
this will hopefully be much more productive
On 2012-08-03, at 21:54, Tudor Girba <tudor@tudorgirba.com> wrote:
When using OCompletion, if you scroll to the bottom of the list (with keydown), you should get the ECompletion list.
Cheers, Doru
On 3 Aug 2012, at 18:42, Esteban Lorenzano wrote:
please go :)
NEController and NOController would be the place
On Aug 3, 2012, at 6:21 PM, Camillo Bruni <camillobruni@gmail.com> wrote:
I don't particularly like the current completion mechanism in pharo:
- the OCompletion (or what it is called) only displays a limited number of selectors - the second completion (which is complete!) using CMD-Q is in many cases more helpful
Could we combine these two? Simply concatenate the two lists and we're done! Where is the place to look for that?
best cami
-- www.tudorgirba.com
"No matter how many recipes we know, we still value a chef."
-- www.tudorgirba.com "Speaking louder won't make the point worthier."
On 2012-08-03, at 22:12, Tudor Girba <tudor@tudorgirba.com> wrote:
Please keep in mind that the reason for showing only the OCompletion list at first was speed. If you are using both at the same time, you might get a performance penalty.
so far it works reasonably fast. and looking at the code I see that the complete list is calculated each time anyway. not showing the complete list IMO renders the completion utterly useless.
The main issue as to me is not the logic how ocompletion works (i find it pretty ok btw), but paramount of mess in event handling. I don't mind having multiple kinds/styles of autocompletion in system (so users can choose to their taste).. but what i don't understand is why we need different shortcuts and different ui displaying completion list(s), spreading over multiple places in system. On 3 August 2012 22:19, Camillo Bruni <camillobruni@gmail.com> wrote:
On 2012-08-03, at 22:12, Tudor Girba <tudor@tudorgirba.com> wrote:
Please keep in mind that the reason for showing only the OCompletion list at first was speed. If you are using both at the same time, you might get a performance penalty.
so far it works reasonably fast. and looking at the code I see that the complete list is calculated each time anyway.
not showing the complete list IMO renders the completion utterly useless.
-- Best regards, Igor Stasenko.
participants (4)
-
Camillo Bruni -
Esteban Lorenzano -
Igor Stasenko -
Tudor Girba