Re: Descent, now with Open Type Hierarchy
Ary Borenszweig wrote: I've uploaded a new version with this feature. ;-) Great and 1 ton of thanks ^^)
Re: Descent, now with Open Type Hierarchy
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...
Re: Descent, now with Open Type Hierarchy
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
Re: Descent, now with Open Type Hierarchy
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. :)
Re: Descent, now with Open Type Hierarchy
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. :(
Re: Descent, now with Open Type Hierarchy
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
Re: Descent, now with Open Type Hierarchy
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.
Re: Descent, now with Open Type Hierarchy
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.
Re: Descent, now with Open Type Hierarchy
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. :)
Re: Descent, now with Open Type Hierarchy
Qian Xu escribió:
Ary Borenszweig wrote:
Enjoy :-)
Great work.
BTW: Is there any plan to make a Organize Imports feature? It would be
very helpful.
Well... now that I've looked at some of JDT's code about this, seems a
pretty hard thing to implement (to translate from Java to D, actually).
But I'll try to do it, little by little.
One question about this. Imagine you have:
void foo() {
auto name = readln();
writefln(Hello %s!, name);
}
When requesting Organize Imports, which one would you prefer?
1.
import std.stdio;
void foo() {
auto name = readln();
writefln(Hello %s!, name);
}
2.
import std.stdio: readln, writefln;
void foo() {
auto name = readln();
writefln(Hello %s!, name);
}
I think the second one is better because it's easier to understand the
code, but the list of names might get very long. But I remember there
were bugs related to selective imports, and I can't remember which were
them. (and maybe it's also harder to implement)
Re: Descent, now with Open Type Hierarchy
2 is very nice towards the namespace
how will you do regex.find vs string.find?
Ary Borenszweig a...@esperanto.org.ar wrote in message
news:h4pcpc$2ef...@digitalmars.com...
Qian Xu escribió:
Ary Borenszweig wrote:
Enjoy :-)
Great work.
BTW: Is there any plan to make a Organize Imports feature? It would be
very helpful.
Well... now that I've looked at some of JDT's code about this, seems a
pretty hard thing to implement (to translate from Java to D, actually).
But I'll try to do it, little by little.
One question about this. Imagine you have:
void foo() {
auto name = readln();
writefln(Hello %s!, name);
}
When requesting Organize Imports, which one would you prefer?
1.
import std.stdio;
void foo() {
auto name = readln();
writefln(Hello %s!, name);
}
2.
import std.stdio: readln, writefln;
void foo() {
auto name = readln();
writefln(Hello %s!, name);
}
I think the second one is better because it's easier to understand the
code, but the list of names might get very long. But I remember there were
bugs related to selective imports, and I can't remember which were them.
(and maybe it's also harder to implement)
Re: Descent, now with Open Type Hierarchy
Saaa escribió: 2 is very nice towards the namespace how will you do regex.find vs string.find? Just what JDT does: show you the matches of find and allow you to choose one of them.
Re: Descent, now with Open Type Hierarchy
2 is very nice towards the namespace how will you do regex.find vs string.find? Just what JDT does: show you the matches of find and allow you to choose one of them. never used JDT for anything but your descent :) but I should have known this is handled nicely already
Re: Descent, now with Open Type Hierarchy
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.
Thanks.
Re: Descent, now with Open Type Hierarchy
Also the hover feature/Open Declaration sometimes behaves incorrectly. Unfortunately I couldn't really track down its cause yet :( Usually when hovering over a function call the ddoc output is correct. Then holding shift to see the source suddenly shows another function. F3 also jumps to that false one then. Sometimes Open Declaration makes eclipse get stuck (where sometimes that extra window operation pending or whatever it was reading is opened, sometimes not)
Re: Descent, now with Open Type Hierarchy
Ary Borenszweig schrieb: Please report these things into the bug tracket: http://www.dsource.org/projects/descent/newticket I'd have done that, if I had managed to narrow down the problem.
Re: Descent, now with Open Type Hierarchy
Qian Xu escribió: Ary Borenszweig wrote: Enjoy :-) Great work. :) BTW: Is there any plan to make a Organize Imports feature? It would be very helpful. I'll give it a try. But maybe some imports are removed that are unused by the current debug/version/static-if conditions. But I think that's not a big deal. I'll start by using normal imports, maybe later I'll do selective imports (but I remember them being buggy).
Re: Descent, now with Open Type Hierarchy
Descent seems to have some problems with multiline `` comments though.
void foo()
{
writefln(`
`);
version(Windows)
{
}
}
everything following the 2nd ` is highlighted incorrectly.
Or is it some configuration mistake?
Re: Descent, now with Open Type Hierarchy
Trass3r escribió:
Descent seems to have some problems with multiline `` comments though.
void foo()
{
writefln(`
`);
version(Windows)
{
}
}
everything following the 2nd ` is highlighted incorrectly.
Or is it some configuration mistake?
True. This will be fixed in the next release.
Re: Descent, now with Open Type Hierarchy
Just updated, this is such a great feature :) Since a couple of versions ago, Descent seems much more stable too, fortunately. You made my day, thanks so much!
Re: Descent, now with Open Type Hierarchy
Ary Borenszweig schrieb: I just uploaded a new version of Descent that implements the Open Type Hierarchy funcionality. You can see a video of it here: Works like a charm, thanks!
Re: Descent, now with Open Type Hierarchy
btw, would be very cool if the code formatter would also format pasted code! VisualAssistX has this feature and it's a pleasure to use it, esp. if you use some code written by other guys with strange code style. I just cut the whole file, paste it again and voila it's nicely formatted ;)
Re: Descent, now with Open Type Hierarchy
Ary Borenszweig escribió: Hi! I just uploaded a new version of Descent that implements the Open Type Hierarchy funcionality. And now that type hierarchy funcionality is in place, I implemented the override indicators, and override method proposals, just like in the Java plugin for Eclipse. I uploaded a new version. Here's a video about it: http://www.youtube.com/watch?v=E_CUTimf9jE
Re: Descent, now with Open Type Hierarchy
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 Descent just keeps getting better and better! I do have one question though, is there and special set up needed that isn't mentioned on the wiki? I finally got around to having a play with it, and import statements weren't automatically written out for me. I also guess there's a key combo to suggest the type as shown in the first few seconds of that video, as I was wondering why that wasn't working. Thanks!
Re: Descent, now with Open Type Hierarchy
Ary Borenszweig pisze: Hi! I just uploaded a new version of Descent that implements the Open Type Hierarchy funcionality. You can see a video of it here: Looks nice. But I get this error during installation: Cannot complete the install because one or more required items could not be found. Software currently installed: Descent 0.5.6.20090725 (descent.ui.feature.group 0.5.6.20090725) Missing requirement: Descent UI Plug-in 0.5.6.20090725 (descent.ui 0.5.6.20090725) requires 'bundle org.eclipse.jdt.core 0.0.0' but it could not be found Cannot satisfy dependency: From: AST View Plug-in 0.5.6.20090722 (descent.astview 0.5.6.20090722) To: bundle descent.ui 0.0.0 Cannot satisfy dependency: From: Descent 0.5.6.20090725 (descent.ui.feature.group 0.5.6.20090725) To: descent.astview [0.5.6.20090722] BTW. I'm impressed by your work on Descent. Cheers Piotrek
Re: Descent, now with Open Type Hierarchy
Ary Borenszweig pisze: I removed that dependency and uploaded a new version. Thanks. Now it works. Cheers Piotrek
