Feature #7020
closedScale content in accordance with screen sizes
Added by Ilja Zakharov about 8 years ago. Updated about 7 years ago.
100%
Description
I have my monitor in a vertical position and a page with a component log does not scale to the bottom of the page and 2/3 of my screen is white unused space. It would be nice to have log longer in the case to be able not to scroll it each time.
Find my screen shot in an attachment.
This is applicable for other pages suffering from that as well.
Files
| empty space (197 KB) empty space | Ilja Zakharov, 04/05/2016 11:53 AM |
Updated by Vladimir Gratinskiy about 8 years ago
- Due date set to 04/06/2016
- % Done changed from 0 to 50
Done for unknown problem description and safe proof (branch "feature_7020"). But I think we need to do this for all pages. The only question is will it be new feature, or extension of this one?
Updated by Evgeny Novikov about 8 years ago
- Subject changed from Scale log to the bottom of the web page to Scale content in accordance with screen sizes
- Description updated (diff)
- Priority changed from Normal to High
Feel free to do this for all pages.
Updated by Evgeny Novikov almost 8 years ago
This feature was partially implemented a long ago but wasn't completed still.
Updated by Evgeny Novikov over 7 years ago
- Priority changed from High to Urgent
It has sense to finish this issue at last. Please, see discussion what to do.
Updated by Vladimir Gratinskiy about 7 years ago
- Due date changed from 04/06/2016 to 02/15/2017
- Status changed from New to Resolved
- % Done changed from 50 to 100
Implemented in branch "feature_7164".
Updated by Evgeny Novikov about 7 years ago
- Status changed from Resolved to Open
You forgot to scale problem descriptions. In addition I suggest to arrange elements at the Unknown page in the same way as at the Unsafe page. For Safes we likely don't have proofs now, but it would be also nice if you arrange elements at the Safe page like at the Unsafe page and scale proofs.
Updated by Vladimir Gratinskiy about 7 years ago
- Status changed from Open to Resolved
Evgeny Novikov wrote:
You forgot to scale problem descriptions. In addition I suggest to arrange elements at the Unknown page in the same way as at the Unsafe page. For Safes we likely don't have proofs now, but it would be also nice if you arrange elements at the Safe page like at the Unsafe page and scale proofs.
Fixed for problem description and other windows I found.
Arrangement of elements on Unknown/Safe is good enough. Unsafe page has two windows with text (error trace and source code), but unknown - only problem description. It would be ugly to stretch error description to full width of screen. Now these pages are handy.
Updated by Evgeny Novikov about 7 years ago
- Status changed from Resolved to Open
Vladimir Gratinskiy wrote:
Evgeny Novikov wrote:
You forgot to scale problem descriptions. In addition I suggest to arrange elements at the Unknown page in the same way as at the Unsafe page. For Safes we likely don't have proofs now, but it would be also nice if you arrange elements at the Safe page like at the Unsafe page and scale proofs.
Fixed for problem description and other windows I found.
Arrangement of elements on Unknown/Safe is good enough. Unsafe page has two windows with text (error trace and source code), but unknown - only problem description. It would be ugly to stretch error description to full width of screen. Now these pages are handy.
I didn't notice any positive changes in scaling. I disagree that stretching error descriptions to the whole screen will be ugly. Please, see various error descriptions, e.g. here, and you will soon understand that many of them, say, from Weaver or CPAchecker are quite wide. Indeed error traces can be also very wide - to meet this issue we even introduced artificial "threads" that required extremely much efforts for full support but allows to very considerably reduce error traces width and to increase their readability.
Updated by Vladimir Gratinskiy about 7 years ago
Evgeny Novikov wrote:
I didn't notice any positive changes in scaling.
But it exists. Problem description window is 70% of browser height for unknown page and 80% for creating unknown mark page.
I disagree that stretching error descriptions to the whole screen will be ugly.
Fixed. Unknown and safe pages are the same as unsafe.
Updated by Evgeny Novikov about 7 years ago
- Status changed from Open to Resolved
Vladimir Gratinskiy wrote:
Evgeny Novikov wrote:
I didn't notice any positive changes in scaling.
But it exists. Problem description window is 70% of browser height for unknown page and 80% for creating unknown mark page.
It also depends on actual problem description heights in contrast to error traces, so likely I didn't notice this because of I opened a too small problem description.
I disagree that stretching error descriptions to the whole screen will be ugly.
Fixed. Unknown and safe pages are the same as unsafe.
Perfect!
Updated by Evgeny Novikov about 7 years ago
- Status changed from Resolved to Closed
I merged the branch to master in 54ec67d. Error traces and problem descriptions can be analyzed more easily now.