emmamai / makron Goto Github PK

Consider ICCCM/EWMH, start implementing it, decide it sucks, scrap all code related, write a new and completely incompatible spec, start trying to implement it, realize you didn't quite think this through, scrap the spec, reconsider ICCCM/EWMH, and then make this thing compliant.

Make it so that dragging by the borders resizes the window.
Best way would likely be to make this and the movement code one and the same, since this code will already have to deal with both movement and resizing. Maybe create an enum of different resizing modes (eg: top edge, bottom right corner, move) and have the pointer motion handler resize/move the window as appropriate based on the mode. Or possibly have a mask instead, tracking which edges to move.

Monitor for newly created windows. When one is found, make a frame, and reparent the new window to the frame.

Action:

Run toolwm, and perform any actions that generate X events.

Expected result:

Toolwm handles events properly and does not leak memory.

Actual result:

Toolwm does not handle events properly and leaks memory because it doesn't free them.

Figure out how apps expect the window manager to let them know the close button was pressed. Then make this do that.

Expand the border by 1px to the right and 1px down, use the Shape extension to cut off the top right and bottom left corners, and paint the resulting additional space black, regardless of whether the window is active.

We should try to raise and focus windows whenever any part of the window is clicked (With respect to ICCCM's WM_TAKE_FOCUS), rather than just when the frame is clicked.

= Action:
Start toolwm while X is not running.
= Expected result:
Toolwm exits gracefully, letting the user know that X needs to be running to run toolwm.
= Obtained result:
Toolwm segfaults.

Make the windows look pretty.

Do whatever it is that needs to be done to make X recognize the app as a window manager. If there's already one running, exit gracefully.

Set the WM_STATE property appropriately as specified in the ICCCM, section 4.1.3. On mapping a window, the state should always be set to normal. If shading, minimizing, iconifying, or any similar mechanism is implemented, then upon any one of these occurring, the WM_STATE should be set to iconic. Windows should start out in the withdrawm state, and only change when mapped by the client. Windows may only re-enter the withdrawn state if the client requests the window to be unmapped.

If the titlebar area of the frame is grabbed and dragged, move the window around accordingly.

Set the root background to a lightgray/darkgrey checkerboard pattern on startup