Robert Fraser escribió:
BCS wrote:
Major suggestion:
The auto compleat drop down is very un-aggressive. I'd love to see it
be Google style sort based rather than ordered-list/browse based.
JDT definitely has this and Descent has some.
Yes, but maybe in Descent it is not fine-tuned. So if you have a case
where you'd like Descent to sort things in another way (not based on
history), report an enchancement feature.
The kind of thing I'm thinking of is having a live sort of the options
based on (among other things) what you have typed and the current
context. For instance, pull things to the top of the list that are of
the correct type for this context
Already (sorta) does this.
Yes. See this:
http://www.youtube.com/watch?v=ZCcedd9EfHI
Starting from minute 1:30 it'll show you how the order of the options
change depending on the expected type of the expression.
(or to a lesser extent, if they have members that are of the correct
type), and do infix matches rather than just prefix matches.
Infix matches would be cool, but... where should they be presented in
the list?
There is a feature in the Open Type dialog where you can type acronyms,
i.e. "DQL" and get "DatabaseQueryListener" as a suggestion. Not sure how
practical/useful this would be to implement in autocomplete.
Autocompletion already works like that (I just tested it, couldn't
remember if it worked like that or not :-P). So for example if you have
a function named "someLongMethod", when you type any sequence of
prefixes of those words (some, long, method, with correct capitals), for
example "sLM", "soLoMet" or "someLoM", etc., it'll show you
"someLongMethod" to autocomplete.
Also nice would be history based sorting (the more often I use
something, the higher up it is).
VS has this & it's a nice feature.
I agree, it's a really nice feature. But to make it work in Descent is
harder because it's based in JDT, and JDT doesn't work like that. :(
