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. :(

Ary Borenszweig wrote:
> Hi!
> 
> I just uploaded a new version of Descent that implements the "Open Type Hierarchy" funcionality. You can see a video of it here:
> 
> http://www.youtube.com/watch?v=d2rR53hUrG8
> 
> Enjoy :-)
> Ary
> 
> P.S.: replies about YouTube being a crap are not accepted :-P
> P.S.2: although missing in the video, pressing ctrl+t on a type opens the quick-type-hiearchy view, just like in JDT. It's a popup window like the outline, but shows the hierarchy and quickly allows to navigate it.
> P.S.3: performance of this is good, as you can see in the video, but can be further optimized
> P.S.4: from minute 1:39 to 1:53 you can perpare youself a coffee

Thanks for the great and excellent work on the plug-in!
- Clay

The Anh Tran wrote:
> Minor suggestion:
> 
> import tango.text.Regex;
> int main()
> {
>     // tango.text.Regex.
>     return 0;
> }
> 
> When i type "tango.text.Regex", then '.', Descent should list only elements inside module/namespace tango.text.Regex.

You are right, it wasn't working well. I've fixed this, there's a new version.

The new version also changed the "Open Type" dialog to "Open Declaration" dialog. So now you can quickly jump to any top-level function, alias, typedef or varaible you declared. :)

Reply to Robert,

> 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.
> 

(I'll admit I don't know much about how the auto-compleat works in descent because I've never gotten it to work correctly at all)

>> (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?

Sort based on how close to the start of the name the match is: prefix matches end up at the top, suffix matches just above non matches.

> 
> 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.
> 

will it find it if I ask out of order? Say, QDL?

>> 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.
> 

Only kind of. I've never seen VS reorder entries in the drop down, so it can only places the start location on the most recent item. I'd want that one at the top of the list and then the rest sorted based on how recently I used them and how often I've used them in the last few hours or days.

BCS wrote:
> will it find it if I ask out of order? Say, QDL?

No... what's the use case there?

JDT does have auto-corrections for misspellings of variables, though (I think based on Levishien distance, so it's dictionary-independent)... this might be intersting to add to autocomplete. So if you try to autocomplete "f*ei*ldN" it will suggest "f*ie*ldName". Also in an ideal world it would be capitalization-independent.

Reply to Robert,

> BCS wrote:
> 
>> will it find it if I ask out of order? Say, QDL?
>> 
> No... what's the use case there?
> 

While working with an API I'm not used to, I'd like the autocomplete to work even if I get the word order wrong.

BCS wrote:
> Reply to Robert,
> 
>> BCS wrote:
>>
>>> will it find it if I ask out of order? Say, QDL?
>>>
>> No... what's the use case there?
>>
> 
> While working with an API I'm not used to, I'd like the autocomplete to work even if I get the word order wrong.

What you want is the matrix helmet. :)

Robert Fraser escribió:
> BCS wrote:
>> Major suggestion:
>> 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.

Descent also has it, I just tried it. :)

Hi Again,

A small feature request to code formatter:
the brace position after "unittest"-keyword is not configurable. Is it
simple to make it configurable?

Thanks in advance
Qian Xu

Qian Xu escribió:
> Hi Again,
> 
> A small feature request to code formatter:
> the brace position after "unittest"-keyword is not configurable. Is it
> simple to make it configurable?
> 
> Thanks in advance
> Qian Xu

Ni hao!

Yes, it should be easy. I'll see if I have a little time to do it today. I already started, but the list of options is now huge and doesn't fit in the screen. I'll have to put a scroll somewhere...