This is about dragging a tab out of or into a browser window, and letting the compositor know about it, so it can move and place the window accordingly. Apps don’t get to place windows themselves.
I used to do apps with QT (as well as with Java) and when creating a window, I only needed to say, “new window of that preferred size please”, then the engine would make the window of that size if possible.
Now, maybe QT did things more in depth behind the scene, I don’t know.
In those cases, I agree.
But for a tiling window manager like w3m, I don’t see the application having a say in position and location.
Hence I didn’t think that the app has so much to do with creating windows. Just my thought.
I don’t understand what is the point of this. Isn’t it the job of the WM to position windows and stuff? Apps have to do it themself now?
This is about dragging a tab out of or into a browser window, and letting the compositor know about it, so it can move and place the window accordingly. Apps don’t get to place windows themselves.
How can a window manager position things if the program doesn’t communicate with it correctly?
I used to do apps with QT (as well as with Java) and when creating a window, I only needed to say, “new window of that preferred size please”, then the engine would make the window of that size if possible. Now, maybe QT did things more in depth behind the scene, I don’t know.
I kind of think that’s QTs whole deal right? An abstraction layer that allows for devs to not get stuck in the weeds implementing it all manually.
If Qt or Java is doing it, then that’s still your program and not the WM, though?
In those cases, I agree. But for a tiling window manager like w3m, I don’t see the application having a say in position and location. Hence I didn’t think that the app has so much to do with creating windows. Just my thought.