On Jul 11, 9:40 pm, Nicolas Hatier <[email protected]> wrote: > On 2010-07-11 23:38, John J Barton wrote: > > > > > On Jul 11, 7:38 pm, Nicolas Hatier<[email protected]> wrote: > >> On 2010-07-07 10:39, John J Barton wrote: > > ... > >>> In 1.6a17 the preselected completion list candidate will be the > >>> shortest one among those offered. That way if you hit enter in the > >>> case above you will get "win". If you want "window" you will have to > >>> either type "d' or cycle the completions. > >> Sorry for chiming in four days later, but I think that issue could be > >> avoided by NOT starting the autocomplete mode before a specific action > >> is posed. I understand the issue about the old autocompletion not being > >> noticed, but consider that sequence: > > >> - type "win" > >> - autocompletion list pops up (but NONE is selected, only "win" can be > >> read in the command line) > > In my version, the list does not pop-up. The command line reads > > "window" with win typed and "dow" selected as the completion. > > Well, it pops-up for "w" but disappears shortly after as there is no > other candidates. So let's change the example with "resize". > This sequence is not what I currently get with autocomplete, but what I > humbly think I SHOULD get. > > Let me rewrite that sequence correctly. a) is what I currently get, and > b) is what I think I should get > > Type "resize". > a) a pop-up is displayed, "resizeTo" is selected in the pop-up and the > "missing letters" ("To") are added, to the command line (inline > autocomplete) > b) a pop-up is displayed, but no entry selected, and no inline > autocomplete is shown > > Type Enter > a) "resize" is used and eval()'d
I get resizeTo completed and eval()'d > b) Same > > (back to previous step, "resize") > Type Up, Down > a) "resizeBy" is selected and inline autocomplete is shown > b) "resizeTo" is selected (as there was no selection before) and inline > autocomplete is NOT shown Ok this is helpful. I gather that you are suggesting that the autocomplete logic kinda "back-off" by one level, so that you have to type up or down before any completion will happen? Other users disagree, BTW. > > Type Escape > a) pop-up is hidden, inline autocomplete is removed > a) pop-up is hidden. inline autocomplete was not visible > > (back to previous step, "resizeTo") > Type one of Enter, dot, space, probably any non-word character key > a) Enter: evals "resize". Other character: gives "resize" + that character Again my version is different: resize with To selected: Enter: evals resizeTo dot: enters dot, no completions now. space: removes "To", adds space. > b) Command line becomes "resizeTo" and cursor is placed at the right of > the word. If it makes sense (like when a dot is pressed), pop-up menu is > shown with new candidate list but no selection. > > In short, no inline autocomplete, only by pop-up. You don't need to > display two times the same info (selection in pop-up and inline > autocomplete is the same info). And there's no selection in pop-up until > you press up or down (add Tab to that list if you think it makes sense). In my version the popup never shows if there is a single completion, but the inline completion shows it. Let's start again with 1.6a17. I'm not against removing the inline completion, but other users did not what to use the arrow keys to complete. jjb > > With that behavior, autocomplete is not in the way, and behaves > intuitively (well, this is relative, but this is the behavior I'm used to). > > Then, removing the Tab key from the autocomplete cycle list would make > it available back to the accessibility features to navigate from field > to field. > > Nicolas > > >> - you type enter -> "win". > > In my version you type Enter, the completion is window, and the > > command is evaluated as window. > > >> - or, you press up or down to begin the autocomplete cycle > >> - you type enter, dot, space, right key, tab? (probably any non-word > >> character in fact, not sure) -> the currently selected word is used. If > >> you pressed dot, the autocompletion list pops up with the new > >> possibilities, but still no entry selected > >> - or you type escape, the autocomplete mode stops and the list is hidden. > > >> For me, autocomplete is very useful, but you have to decide if you want > >> to implement inline autocomplete (no pop-up menu, candidate being > >> written in selected text as we type) or pop-up autocomplete (pop-up > >> menu, no post-cursor selected text). Now you have both at once, and it > >> causes various usability problems. > > >> Maybe adding a firebug option to disable autocomplete alltogether would > >> also be salutary for the rare use cases where it gets in the way. > > I don't want to have to support the option. The current options in > > Firebug are a huge headache for me. Bug triage becomes a game of 20 > > questions by email. We need to work on the autocomplete algorithm > > until it works well or we should just remove it altogether. > > > jjb > > >> Nicolas -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
