Open unknowledgeable opened 4 years ago
I've added the flutter.toggleOutline
command and the flutter.outlineWidth
setting. I think these solve the problem.
I know vim is generally a mouse free zone but what if when you clicked on a node in the tree it took you to the corresponding line in the code?
Or better yet, h
to fold widgets (hide children but display a ...
or something), j
/k
for up/down and l
to go to line. What do you think?
Let me know if my recommendations are getting too much haha!
E: toggle and outlinewidth are perfect btw!
@unknowledgeable Now you can press "enter" in the outline buffer to go to the corresponding location in the source file.
Regarding folding, I do think that folding is really useful, but I'm yet to figure out a fast way to persist the outline tree folding state when a new outline tree gets passed from the language server. I'll have to keep experimenting.
Awesome! Do you want me to continue with the suggestions as I think of them?
Yes, please! I might not implement all of them as quickly but I’ll work on them when I have time. I’ll also be posting stuff that I think might be useful in github issues so feel free to discuss in those.
I've now set up a mapping for the flutter.outline command and I think it would be great if you could toggle it on and off with the same mapping as coc-explorer can (I know I keep going on about coc-explorer it but it seems like a very similar type of window right?).
Another thing I've noticed is that the widget window doesn't keep it's original size when other window splits are made/removed. Would be nice to have it stay at a defined size much like you can with coc-explorer (again!) when you set
in coc-settings.json
Also, don't know if you use which-key but I've started populating my config file with some mappings if that's of any interest to you:
I've left most of the debug stuff out because I think I want to nest it but it's a start!