-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove "dynamic" TWM #137
Comments
No opinion on manual/dynamic, I'll let @stapelberg decide but regarding your blog post, the preferred way to do most of your red squares in i3 is with the IPC interface. For example, the "next workspace" is quite trivial: i3/i3#6147 |
On other points:
i3 is not involved with drawing window contents. xcb is just a library implementing the same protocol Xlib is. That shouldn't be noticeable by windows at all. |
Hello @orestisfl !
I am not the author, |
Prove it. You accuse someone of lying with absolutely zero proof. The blog post has no proof either, it's just stating that they think it's not dynamic, without any proof. Honestly your tone is so bad that I would just close this issue for good. If you do have a point, proofs and can say it without insinuating that the maintainers are lying then make another issue. Your link even says that xmonad is dynamic, but you need to recompile it to change any settings, how it that dynamic ? It's the opposite of dynamic. |
Hello @simlevesque ! :
See
This was indeed a possibility I asked that:
i3 offers some flexibility in window management but still fundamentally operates on a manual basis by requiring direct user input for window layouts / behavior. A dynamic tiling window manager usually automatically adjust window sizes and positions based on available screen space and set user preferences Users must manually specify how windows are arranged (horizontal, vertical split, stacked, etc...) using keyboard shortcuts or configuration files; Dynamic TWM also usually can use algorithms to anticipate user needs and automatically adjust window arrangements
Sorry about that, it was not my intention
With all due respect, are you a member of i3 ?
This does not contradict the meaning of a "Dynamic" tiling window manager |
Of course we’re not lying on purpose, and that’s a pretty disrespectful accusation to just throw around. I recommend you assume good faith in future interactions. i3 clearly isn’t dynamic in the sense that there is a fully automated window placement algorithm, but it also isn’t manual in the sense of TWM or ion3, where you had to select a destination for each new window, or in the sense of stacking window managers where windows just pop up whereever. Faced between the two extremes of manual and dynamic, I classified i3 more on the dynamic side than the manual side. I can see that this classification is not entirely satisfying, but if we do anything about it, I would prefer to just get rid of the terms “manual” and “dynamic” entirely, as I don’t think they really help anyone. People should watch a video or try out i3 (or any other window manager, FWIW) to really get an impression of how it looks and behaves. |
Hello @stapelberg !
It could sound offensive and aggressive, but I do not see marketing lie as such really, so no worries
Understandable
That would indeed be better, reflecting it in #136 asap Edit : Done
Agreed |
I just edited #137 (comment), it should be more appropriate and descriptive, now |
This issue is global to the organization, not specific to that repository
Problem
Currently, in the i3 organization, there are mention about i3 being a "dynamic" tiling window manager
I think it should be removed because that does not correspond to what a "dynamic" tiling window manager is
Solution
Removing the mentions about i3 being a "dynamic" tiling window manager
Cross-repositories Pull Requests
The text was updated successfully, but these errors were encountered: