Re: hcwm
Posted: Fri Feb 07, 2014 7:44 am
While certainly ready in its own right (it has no flaws, only features), I run it in tandem with cwm...because they have the ability to switch back and forth in a live setting without closing the Xserver. That was actually my main reason to ever start working on it, because I like stacking...but when I really get down to opening and closing a lot of windows at once (such as this project), I prefer tiling. This is my solution to needing tmux in a floating terminal emulator window...and by "my solution," I mean I stole everything I could from suckless while removing things I didn't really need and adding things I wanted.
So, if you're going to release it, I'd send it packaged with cwm. They like each other:
C^M^w in cwm allows you to spawn a different wm, where you can select this one.
S^M^w in my stock config.h spawns a session of cwm. You could technically tie it any other wm, but I never do.
Edit: Also, it's totally keyboard-driven. I have vi-like binds (M^j cycles through windows forward, M^h resizes the stack to the left, etc.) The mouse is only taken into consideration by the program being ran inside of the wm...the wm does not care for mice. The name (heavily-commented window manager) should imply exactly how I think that modifications and changes should be made. I WANT it to be a jumping-off point for C-hackers to modify to suit their needs. I have no intention for long term support, but rather that it should be in the hands of the user to make into whatever they want.
So, if you're going to release it, I'd send it packaged with cwm. They like each other:
C^M^w in cwm allows you to spawn a different wm, where you can select this one.
S^M^w in my stock config.h spawns a session of cwm. You could technically tie it any other wm, but I never do.
Edit: Also, it's totally keyboard-driven. I have vi-like binds (M^j cycles through windows forward, M^h resizes the stack to the left, etc.) The mouse is only taken into consideration by the program being ran inside of the wm...the wm does not care for mice. The name (heavily-commented window manager) should imply exactly how I think that modifications and changes should be made. I WANT it to be a jumping-off point for C-hackers to modify to suit their needs. I have no intention for long term support, but rather that it should be in the hands of the user to make into whatever they want.