Skip to content

Display program_err in multiple columns - #3584

Open
vmcj wants to merge 1 commit into
DOMjudge:mainfrom
vmcj:program_output
Open

Display program_err in multiple columns#3584
vmcj wants to merge 1 commit into
DOMjudge:mainfrom
vmcj:program_output

Conversation

@vmcj

@vmcj vmcj commented Mar 22, 2026

Copy link
Copy Markdown
Member

Most of those lines are short so we can use the extra horizontal space.

image

For the rest of the output the user gets a horizontal scrollbar, I think that is easy enough to follow the program without taking up the whole page.

Just as a pitch, if we want this I can apply it to the other outputs also.

@meisterT

Copy link
Copy Markdown
Member

How does this look like if you have your window width is small (e.g. tiled to the left half of the screen)?

@vmcj

vmcj commented Mar 22, 2026

Copy link
Copy Markdown
Member Author

How does this look like if you have your window width is small (e.g. tiled to the left half of the screen)?

Not worse than before. if we tweak it would work the same but CSS will render the "old view" when the window doesn't have enough width.

@meisterT

Copy link
Copy Markdown
Member

Not worse than before.

So you don't have to horizontally scroll and it starts going to the old view automatically?

@vmcj

vmcj commented Jul 11, 2026

Copy link
Copy Markdown
Member Author

Not worse than before.

So you don't have to horizontally scroll and it starts going to the old view automatically?

if we wouldn't set the height it would yes. I now set the height as I would prefer the horizontal scroll in case I'm on my phone and want to scroll the page. It looks like you want the opposite of it.

@vmcj
vmcj force-pushed the program_output branch from 15ab28e to 134d5ab Compare July 11, 2026 14:42
@vmcj
vmcj requested a review from meisterT July 11, 2026 14:42
…zontal area

Before messages would be short and on a wide monitor there would be a lot of wasted space,
Now we calculate the longest line and display that in full and try to fit similar sized columns.

On smaller monitors this would just result in less columns and never in a horizantal bar,
if/when we want that we should set the `height`.
@meisterT

Copy link
Copy Markdown
Member

For me there is no visual distinction between columns, e.g. this looks confusing:

image

We might want to consider not breaking it up into multiple cols if all/most lines have the same width for these maze like outputs.

Also, perhaps it should be a toggle? Not sure whether local or global.


One way to make this less confusing (more code though), is to do something like this:

image

@vmcj

vmcj commented Jul 12, 2026

Copy link
Copy Markdown
Member Author

For me there is no visual distinction between columns, e.g. this looks confusing:

If you zoom in you see a line there, I can make it thicker though.

We might want to consider not breaking it up into multiple cols if all/most lines have the same width for these maze like outputs.

I had it for a submission where I had a lot output of the same width so, my preference was to have it for specifically output with almost the same width. We could do some fancy detection but that also makes it harder.

Also, perhaps it should be a toggle? Not sure whether local or global.

I think that requires knowing it, will either not be used a lot. So in that case I would prefer it to be on by default and that it can be turned off per problem for all users? As I think it's best to compress as much as possible and leave it up to the user how such mazes should be displayed.

One way to make this less confusing (more code though), is to do something like this:
image

Great for a follow up, but more work than I want to do for now. I do think this is better than we had before.

@meisterT

meisterT commented Jul 12, 2026

Copy link
Copy Markdown
Member

If you zoom in you see a line there, I can make it thicker though.

I must be blind, because I am seeing nothing.

I do think this is better than we had before.

As user, I would want a way to turn it off in the current version, because there is no (or perhaps minimal) distinction between columns.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants