FortuneN / FineCodeCoverage

Visualize unit test code coverage easily for free in Visual Studio Community Edition (and other editions too)
https://marketplace.visualstudio.com/items?itemName=FortuneNgwenya.FineCodeCoverage
Other
516 stars 39 forks source link

Request: Reduce vertical space taken up by header in Coverage Report #341

Open ogiesen opened 1 year ago

ogiesen commented 1 year ago

Installed product versions

Description

I typically have FCC docked to the bottom of my VS window. Unfortunately, I can hardly see anything in there a lot of the time as the top 156 pixels are taken up by the tab row and lots of blank space in the grouping/filter header. I'd prefer if this could be massively reduced so I could see more (/any) entries in the report without first having to drag the horizontal splitter up each time.

It'd be great if you could move everything from the grouping header up into the tab row - if necessary, add a hamburger menu - just don't waste all that vertical space, please!

ygoe commented 2 months ago

I guess you are referring to this:

grafik

I agree that there's a lot of space wasting here. Besides other UI issues like missing arrows in all scrollbars and intense colours (table row hover inversion, darkblue tabs, bold border around the filter textbox, unintuitive grouping slider) my idea would be to move all of that stuff into the almost empty toolbar.

There's a toolbar that only has 2 icons and the rest is empty. There's plenty of space to put all the other controls in there:

Also, the space around the coverage table could be reduced and should be more similar to the rest of Visual Studio's UI. The whole UI feels like it doesn't belong there. Everything is different than anything else.

I'm not sure how to proceed with the other links (rate & review; log issue/suggestion; buy me a coffee), they usually don't belong in a UI. Maybe a menu would be okay?

Don't get me wrong, I like the extension so far, it serves the purpose and I can see where my tests need improvement. And I'm aware that good devs aren't necessarily good UI designers. It's just that this aspect shouldn't be neglected if you want the user to feel good about the extension. Improving the UI layout here would already make a great difference I'd say. The other panels like "Output", "Errors" or "Exception settings" give good guidance here.