I had some suggestions for visual D for visual studio 2019

1. make "Show expansion when" select "+ writing an identifier" the default setting

2. color code things, make only relevant descriptions visible and allow filtering of types.
here is a comparison of the differences (top C#, bottom D).
https://imgur.com/NNW5ldv
https://imgur.com/s8ZnE4L

3. allow optional C# icons
see above images.

4. gui based package manager for dub modules.
this would be similar to nuget package manager.
see this.. https://forum.dlang.org/thread/mugnqxsksjqrdrjeffie@forum.dlang.org

5. change project and .d file icons to something more fitting for visual studio
see this.. https://forum.dlang.org/post/rugqlhyigfqyrtxxnpko@forum.dlang.org

6. remove legacy d projects and encourage the use of d/c++ projects..

7. separate and create more project types...
static  library,
dynamic library,
winform app (with designer),
console app

the winforms app could probably be replaced with some sort of native looking cross platform alternative. just make sure to make a designer eventually. :P

On 19/09/2019 02:09, Shadowblitz16 wrote:
> I had some suggestions for visual D for visual studio 2019
> 
> 1. make "Show expansion when" select "+ writing an identifier" the default setting
> 
> 2. color code things, make only relevant descriptions visible and allow
> filtering of types.
> here is a comparison of the differences (top C#, bottom D).
> https://imgur.com/NNW5ldv
> https://imgur.com/s8ZnE4L

I've recently worked on colored tool tips a bit, but it's not so easy because it needs integration with a framework completely different than what's accessible from native code.

> 
> 3. allow optional C# icons
> see above images.
> 

Currently the C++ icons are used, and I don't think we need a another set of images.

> 4. gui based package manager for dub modules.
> this would be similar to nuget package manager.
> see this..
> https://forum.dlang.org/thread/mugnqxsksjqrdrjeffie@forum.dlang.org

dub doesn't generate great Visual D project files and integration isn't easy because the build systems are different. Would be a great project for someone to pick up, though ;-)

> 5. change project and .d file icons to something more fitting for visual
> studio
> see this..
> https://forum.dlang.org/post/rugqlhyigfqyrtxxnpko@forum.dlang.org
> 
> 6. remove legacy d projects and encourage the use of d/c++ projects..

Removing would be a bit harsh, but I'll consider marking them legacy.

> 
> 7. separate and create more project types...
> static  library,
> dynamic library,
> winform app (with designer),
> console app
> 
> the winforms app could probably be replaced with some sort of native looking cross platform alternative. just make sure to make a designer eventually. :P

There is currently no standard UI library that I'm aware of that everybody prefers. Maybe it would be good to just pick one and add a couple of examples.

I'd also like to do add vibe.d examples. As it and most other projects rely on dub for their build process, having some build and dependency support would make the integration much easier and seamless.