Basically, the cited problem (see the screenshot there) also exists in the SQ web interface. When fonts are large, putting frames within frames within frames within frames… just shrinks the ACTUAL USEFUL CONTENT to uselessness. The old version of SQ was done intelligently – things like “why is this an issue” were links within the issue box. Now they’re separate tabs and just eat up more space, so that the actual code is down to just a few lines, roughly 5-10% of actual screen area. (My screen isn’t quite as horrible as the screenshot in the other thread, but it’s close.) That makes it hard to see the issue in context.
Maybe some people with perfect vision and giant monitors like all the extra frames and tabs. If so, you should accommodate both groups with some kind of global setting, a “low-res” setting that tries to preserve the area for the actual content.
This illustrates the change. The white box is the browser window dedicated to SQ (not counting URL, tabs etc.). This is the standard issue view. The green box shows what used to be the area showing actual code, excluding the box with the name of the rule etc. The red box shows what we get now.
This is the same whether we browse issues through the web portal or we follow a script-generated link with the URL UUU/project/issues?id=PPP&issues=XXX&open=XXX
where UUU is the server, PPP is the project key, and XXX is the issue key. But if there’s a way to tweak the latter to waste less of the screen area in the browser, that would be helpful.
I’ve run into this too, and the newer layout definitely feels like it prioritizes UI elements over the code itself. When you’re trying to understand an issue in context, losing most of the screen to nested panels and tabs is frustrating. A compact or low-resolution layout option would make a lot of sense.
Yes, that sums it up quite well! All that nesting seems to be driven by the same thinking that said having ten or more levels in your Java code hierarchy (each level having only one child) is a good idea!
I wish UI designers would get out of the habit of thinking, “my particular setup (choice of browser, monitor, window size, font size, color scheme, etc.) is the only one that anyone will ever use.”
Yes, thank you for the feedback. This frustration is also shared internally .
We’re currently working on a new layout for the issues page. It will ship shortly on SonarQube Cloud and will be included in the upcoming SonarQube Server release in October. Stay tuned!
.