-
Notifications
You must be signed in to change notification settings - Fork 3
Feature: Developer Console tabs #1794
Copy link
Copy link
Open
Labels
Priority 3: MediumSomething that should be attempted/looked at for the next release, and done if possible.Something that should be attempted/looked at for the next release, and done if possible.Size 3: MediumSomething that will take a couple days to a week to do.Something that will take a couple days to a week to do.Type: EnhancementThis is something that improves upon an already existing thing.This is something that improves upon an already existing thing.Type: FeatureThis is something completely new that will be added.This is something completely new that will be added.What: UIUI-related issuesUI-related issues
Description
Metadata
Metadata
Assignees
Labels
Priority 3: MediumSomething that should be attempted/looked at for the next release, and done if possible.Something that should be attempted/looked at for the next release, and done if possible.Size 3: MediumSomething that will take a couple days to a week to do.Something that will take a couple days to a week to do.Type: EnhancementThis is something that improves upon an already existing thing.This is something that improves upon an already existing thing.Type: FeatureThis is something completely new that will be added.This is something completely new that will be added.What: UIUI-related issuesUI-related issues
Which component should be improved?
UI/UX
Describe your feature suggestion in more detail
Currently, we have a generally quite cloudy and saturated developer console. A lot of messages are completely useless to players (things like engine messages or failed achievements loading), and the messages that are useful (like errors in scripts or missing materials) get buried. Not to mention the console has a hard limit on how many messages it can display, meaning a lot of information gets actively removed in favor of more recent ones. Yes, logging the console to a file helps, but it's neither ideal nor convenient.
My proposal is a tabbing system. By default, all messages in the console can be aggregated in a single tab like normal, but users can add "tabs" for specific types of messages. For example: one tab exclusively for AngelScript (scriptsys) messages; one tab exclusively for materials messages; one tab exclusively for panorama messages; etc. Additionally, if possible, a tab exclusively for writing commands and getting their outputs would be great.
These tabs should have their own history (so as to not get prematurely capped by the general console hard limit), get cleared on their own if the user runs
clear, and should also be saved with the user's preferences, so they don't have to reopen/reselect those tabs every time. Moreover, I propose tabs rather than filters because it allows for multiple modes of interaction without having to change filters or increase the messages limit.I believe this is a relatively high priority because as more time passes, more and more different messages from different sources are pushed into the console, which makes debugging incredibly difficult for modders and devs.