Open RafalSkolasinski opened 4 years ago
Aha, apologies - I'll see if I can sort this out quickly later today. I've not been using i3 for a little while now, but it'd be great if this tool works for others still!
Awesome! Lemme know if you need something to be tested!
Abusing a bit purpose of this issue, do you mind if I ask two minor questions about the code? I wonder about the scenario with two monitors: a) are all outputs coupled, it is if you move down a workspace it moves down on all monitors? b) what happens if you move a workspace to a different monitor? Does it add it at the end and add more workspaces?
for a) is there an option to configure it maybe?
So, i3x3 is a pretty opinionated tool - I had something very specific in mind that I wanted and just made it exactly like that. With that in mind:
a) Outputs are not coupled, they're separate (and sadly, there's no way to configure this currently) b) i3x3 controls which workspaces are on certain displays, so if you were to move a workspace to a different monitor, i3x3 would move it back to the one it expects it to be on. This is fleshed out a little more in the README, but it was so I could make it so that it was just some maths used to move workspace - and if a workspace didn't already exist, it would create it and put it on the right display for you, etc.
Sort of sadly I'm using a Mac these days - but I do still have my desktop with Arch on it, I just haven't used it since I got my MacBook.
Thanks for the reply.
Opinionated is fine ; - ). I am now exploring different solutions out there to see how they are built to probably at some point get my own opinionated "gridded workspace" solution.
I do love how i3
is handling windows on single workspace but I much more preferred how KDE was handling multiple workspaces in gridded manner.
But oh man, before giving it more thought I didn't expect that simple subject of moving workspaces around in geometrical context maybe such complicated subjects. I don't mean math but all the design decisions how it should behave with more monitors etc. ; - )
Anyway, looking forward to trying out your solution!
Alright, I've updated those references of SeerUK now to seeruk. Let me know if you have any more issues installing.
One other thing that springs to mind is that I think you might also need dep installed, and I'm not sure the README mentions anything to do with it. Once you've got dep, install the third-party code with:
$ dep ensure -v -vendor-only
From there, as long as you have the GTK libraries on your system, I think the go build should work just like normal.
Thanks @seeruk, installation now succeeded.
I had however to do go install github.com/seeruk/i3x3/cmd/i3x3d
additionally.
Something may not be fully right for my though as I do not see any GTK-based overlay GUI when switching workspaces. The switching however seems to work fine ; - ).
Cannot install due to
:(