From 539e8d84c74f2cb1fef23988ec2574f0a6867e0b Mon Sep 17 00:00:00 2001 From: MadcowOG Date: Wed, 22 Feb 2023 22:41:40 -0800 Subject: [PATCH] Readme change and removed unneeded protocol --- README.md | 7 +- protocols/dwl-bar-ipc-unstable-v1.xml | 141 -------------------------- 2 files changed, 3 insertions(+), 145 deletions(-) delete mode 100644 protocols/dwl-bar-ipc-unstable-v1.xml diff --git a/README.md b/README.md index b5e2507..d9b576b 100644 --- a/README.md +++ b/README.md @@ -3,20 +3,19 @@ dwm-like bar for dwl I believe dwl-bar provides a more dwm-like experience out of the box than other bars like somebar. -Still in development. But should compile. - ## Dependencies I'm not sure what the package names will be for your distrobution, so just make sure these are generally what you have. + + make + pango + cairo + wayland + wayland-protocols ## Compile -Compile with this command `gcc ./src/*.c -o ./bar $(pkg-config --cflags --libs wayland-client wayland-cursor pangocairo)`. +Compile with `make`, install with `make install`, uninstall `make uninstall`. ## Configuration -Like most suckless-like software, configuration is done through `src/config.def.h` modify it to your heart's content. +Like most suckless-like software, configuration is done through `src/config.def.h` modify it to your heart's content. dwl-bar is compatible with [someblocks](https://sr.ht/~raphi/someblocks/) for status. ## Thanks Thanks to raphi for somebar this project is largely just somebar but in C and a few tweaks to make it similar to dwm. The ipc protocol is also just the ipc patch in somebar's `contrib/`. diff --git a/protocols/dwl-bar-ipc-unstable-v1.xml b/protocols/dwl-bar-ipc-unstable-v1.xml deleted file mode 100644 index c2d0674..0000000 --- a/protocols/dwl-bar-ipc-unstable-v1.xml +++ /dev/null @@ -1,141 +0,0 @@ - - - - - This protocol allows clients to get updates from dwl and vice versa. - - Warning! This protocol is experimental and may make backward incompatible changes. - - - - - This interface is exposed as a global in wl_registry. - - Clients can use this interface to get a dwl_output. - After binding the client will revieve dwl_manager.tag and dwl_manager.layout events. - The dwl_manager.tag and dwl_manager.layout events expose tags and layouts to the client. - - - - - Indicates that the client will not the dwl_manager object anymore. - Objects created through this instance are not affected. - - - - - - Get a dwl_output for the specified wl_output. - - - - - - - - This event is sent after binding. - A roundtrip after binding guarantees the client recieved all tags. - - - - - - - This event is sent after binding. - A roundtrip after binding guarantees the client recieved all layouts. - - - - - - - - Observe and control a dwl output. - - Events are double-buffered: - Clients should cache events and redraw when a dwl_output.done event is sent. - - Request are not double-buffered: - The compositor will update immediately upon request. - - - - - - - - - - - Indicates to that the client no longer needs this dwl_output. - - - - - - Indicates the client should hide or show themselves. - If the client is visible then hide, if hidden then show. - - - - - - Indicates if the output is active. Zero is invalid, nonzero is valid. - - - - - - - Indicates that a tag has been updated. - - - - - - - - - - Indicates a new layout is selected. - - - - - - - Indicates the title has changed. - - - - - - - Indicates that a sequence of status updates have finished and the client should redraw. - - - - - - - - - - - - - - - - - The tags are updated as follows: - new_tags = (current_tags AND and_tags) XOR xor_tags - - - - - -