On 2010-07-12 10:17, John J Barton wrote:
On Jul 11, 9:40 pm, Nicolas Hatier<[email protected]> wrote:
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
I run 1.6a16. I don't know why we don't get the same thing.
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.
Exact. My autocomplete model is the one implemented in Visual Studio,
which I find very pleasant to use.
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.
My opinion is that inline completion should disappear completely. I find
this annoying, and this is duplicate information in the UI. But this is
just my opinion.
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.
And why not? Command-line-type people are used to use Tab for
completion. Cmd, bash and other shells never do completion before a
specific key is typed. Visual Studio autocomplete requires up or down.
Firefox and IE's address bar, as well as google autosuggest requires
up/down before using any of the candidate. The model is available and
quite widespread. Why reinventing it if it ain't broke?
Nicolas
jjb
--
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.
