+1 - Adding to @TomjNorthIdaho’s point… it really does help operationally to quickly spot troubles. i.e. if you see a lot of red when scrolling logs, in just couple seconds… you know there is an issue.
On “colorization needs”, I’d add:
-
Log should parse ANSI color codes. I know Terminal ANSI support well, since my $PIANO script renders very nice in WinBox4. But WinBox3 never parsed ANSI code in logs… and some container end up with ANSI colors in log since “logs” often wired to stdout. This can sometimes be disabled, but it actually be better if WinBox4 actually support ANSI in log message.
-
This one may be more controversial. Fonts always are. Perhaps the script/code editboxes (/system/script/source etc.) should use y’all standard JetBrain Mono font. I know winbox has historically used proportional fonts, but I don’t think that’s very easy to read. While the proportionally-spaced “Manrope” used for scripts does have same nifty → ligature – which is a nice subtle touch – that however does not make it more readable for script code. I want monospaced font in those editboxes.
-
Beyond fonts, but same /system/script (and similar) “code editbox”… While CLI “/system/script/edit script source” has supported colors – even with error-checking shown in reverse red when script is wrong – winbox has not ever. Given scripting has a learning curve & most new users likely use WinBox4’s UI, than the Terminal — it’s actually /system/script UI dialog where the colors and realtime error-checking be useful. Perhaps just a button to launch Terminal with current one show in Script dialog box opened be helpful. Anyway, the /system/script/edit is actually pretty useful to spot errors in scripts – but you get no help with that in any winbox today.