This repository has been archived by the owner on Jun 16, 2024. It is now read-only.
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.
Summary
This PR implements a new layout similar to i3's (and sway's) behavior. If you don't know i3, the main difference with bismuth is that i3 doesn't have predefined layouts. You compose your layout as you go by splitting your screen in vertical and horizontal containers.
This is not a full implementation, more like an early draft to get your opinion. I tried implementing the change in the least intrusive way, but I had to make a few changes in the generic Engine code too.
To implement this layout, I had to keep track of windows in the layout itself. So there are two different states with the list of the windows: the WindowsStore, and the layout's list. This introduce some complexity, and potentially bugs if those states desync. I'm wondering if this really is the right approach, I'm starting to think we should aim for a bigger change in the core of bismuth to implement nested layouts (#93) to have more robust code and more features (the nesting itself). Feedback is welcome :)
Things left to implement
Breaking Changes
The first commit changes the behavior of bismuth regarding new windows. Instead of adding them at the end of the list, new windows are now added just next to the current one.
UI Changes
Test Plan
Not planned yet
Related Issues
Closes #182