rework RxPaired main UI modules concept - #35
Merged
Merged
Conversation
I was lately adding performance-related metrics to RxPaired and the result annoyed me: there was too many "modules" on the screen, options to placement were unclear etc. So I looked at how we use the tool in general, and tried to rework the UI so it can make sense: - Many people are only looking at the logs, and modules are often linking to specific logs. You also time-travel by selecting a specific log, and have many filters options only applying to log. Thus logs are basically the central aspect of RxPaired. Before that display of logs could be moved alongside the other modules but it had no real point and brought a lot of complexities in module movement, which modules could be "closed" (logs could not) and so on. So I took the decision to remove logs from the UI "module" concept (the debugging units that can be moved, closed, reduced etc.). - Logs is always to the left, modules are always to the right. This makes placement of modules just a up-down thing, thus making the placement aspect for once usable without doing too much work. - The "tutorial" was before a module by itself. "Clever" but I think confusing UI-wise. I made it a simple detail element on top. - Modules and logs have their own scroll areas. Once you look at the result, it makes sense why and seems more natural. - The separation between the left (logs) and right (modules) part of the screen is configurable by dragging the mouse. It feels like it could still be improved on by a lot, especially around module discovery/selection and placement, but I do feel it's still a very big improvement over what we had before.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I was lately adding performance-related metrics to RxPaired and the result annoyed me: there was too many "modules" on the screen, options to placement were unclear etc.
So I looked at how we use the tool in general, and tried to rework the UI so it can make sense:
2026-09-21.14-29-22-under-10MB.mp4
Many people are only looking at the logs, and modules are often linking to specific logs. You also time-travel by selecting a specific log, and have many filters options only applying to log.
Thus logs are basically the central aspect of RxPaired.
Before that display of logs could be moved alongside the other modules but it had no real point and brought a lot of complexities in module movement, which modules could be "closed" (logs could not) and so on.
So I took the decision to remove logs from the UI "module" concept (the debugging units that can be moved, closed, reduced etc.).
Logs is always to the left, modules are always to the right. This makes placement of modules just a up-down thing, thus making the placement aspect for once usable without doing too much work.
The "tutorial" was before a module by itself. "Clever" but I think confusing UI-wise. I made it a simple detail element on top.
Modules and logs have their own scroll areas. Once you look at the result, it makes sense why and seems more natural.
The separation between the left (logs) and right (modules) part of the screen is configurable by dragging the mouse.
It feels like it could still be improved on by a lot, especially around module discovery/selection and placement, but I do feel it's still a very big improvement over what we had before.