updates to the logging view

[devoncarew]

• misc general improvements to the logging view
• allow for asynchronously calculated log entry details (for when we need to query the VM for more details)
• add a clear all button to the log view
• when logging stdout text, delay 1ms to see if we get the newline associated with the current stdout message
• make sure the log kind column doesn't become too wide

@DanTup

[devoncarew]

[DanTup]

What's the reason for these replacements? Won't replacing characters like this (for ex.) make an actual newline and the literal characters \n in the users log render the same in this view? This might complicate debugging, for ex. if your app showing a literal \n where you expected a newline?

[devoncarew]

That's a good point - it would be hard to differentiate between a newline and a sequence of two \n chars.

Without this however, you won't know if you have whitespace chars in your output - they won't show in the rendering.

I'm not sure if there's a solution that covers both situations; if no, we likely want to make the whitespace chars visible.

[DanTup]

Without this however, you won't know if you have whitespace chars in your output - they won't show in the rendering

Do you mean because they collapse in HTML? If so, don't the pre/whitespace settings help with that?

My concern here was that any manipulation of the data here could lose data - it'd be better to keep the raw string and deal with anything like this in the rendering as-appropriate? Fox ex. It might be important that the user can copy/paste an item from the log and have it as was printed verbatim?

[devoncarew]

Do you mean because they collapse in HTML? If so, don't the pre/whitespace settings help with that?

It would with the formatting aspect, but not w/ knowing whether it was a tab, several spaces, ...

I can remove this part and we can re-assess if this ever comes up as an issue.

[DanTup]

but not w/ knowing whether it was a tab, several spaces

Oh, gotcha! I guess this is no different to when the user prints and sees it written anywhere else so probably people are used to selecting/inspecting/copy&pasting to review, but we could consider a button that toggles rendering whitespace in the details?

[devoncarew]

we could consider a button that toggles rendering whitespace in the details

That sounds great - a good solution. It could be a raw data vs a rendering option, esp. for some log entries where we interpret the data (frame events, gc events, ...).

[DanTup]

👍 I added a note to the doc so this doesn't get forgotten (though we can start using issues here if you think makes more sense).

[devoncarew]

We should likely move the work we think we're likely to do from the doc into the issue tracker.