Replies: 5 comments 2 replies
-
Hi @mato, I'll be glad to help, for now except the labwc thing. The shell will remain sway-centered until we have a true and real team of developers. The playerctl module crashes for you while trying to import the BTW: dunno what |
Beta Was this translation helpful? Give feedback.
-
Hi Piotr,
Sure. My first goal is to get it running at all, in a reproducible way. I can use sway, just prefer very much not to, having been using Openbox for the last 15 years or so.
Got it, thanks. Installing It now complains about
I used to use setup.py years ago when working on Python 2 code. When I tried that now, I got a ton of exceptions and deprecation warnings sternly telling me not to, so I went looking and found this: https://packaging.python.org/en/latest/tutorials/installing-packages/#installing-from-a-local-src-tree. The It seems that |
Beta Was this translation helpful? Give feedback.
-
Your choice, dependencies and installation method remain on packager's side. From the code point of view, it doesn't matter which way you make the python module available. E.g. I don't use packages at all on my development machine, but only while testing. |
Beta Was this translation helpful? Give feedback.
-
labwc will outright fail to even run anything in this project which currently depends on Sway/i3 IPC socket functionality. This includes nwg-shell-config when it hits the output enumeration, and also the process list tool. The most that will work is things using protocols such as foreign toplevel. (I don't really want to have to use Sway, because I hate the very organization of having to throw all my windows into a tiled grid.) |
Beta Was this translation helpful? Give feedback.
-
On the 'split' branch there are 2 different nwg-shell-config versions: aimed at sway, depending on i3ipc, and aimed at Hyprland, reading from their socket and socket2. Labwc would require a 3rd config app. Also the dock would need to be written in a 3rd version. For now we have nwg-dock and nwg-dock-hyprland. The rest should work well, apart from the fact, that nwg-panel has no labwc-specific modules. |
Beta Was this translation helpful? Give feedback.
-
Hi Piotr,
this is related to #18. I'd like to try and get nwg-shell working on Debian with sway, and once that works, try to improve it to work with the labwc stacking compositor, since coming from Openbox I much prefer that to sway.
I'm fairly familiar with Go, but haven't used Python much recently and am missing a "recipe" to get the Python components working, starting with nwg-panel. In order to understand how things fit together I don't want to run anything via an installer, or indeed install any components system-wide yet. So, I'm looking for a way to run the components "in place" for development.
For nwg-panel, so far I have the following:
python3 python3-pip python3-psutil python3-cairo libgtk-layer-shell-dev
.pip install -e .
$HOME/.local/bin/nwg-panel
.(To be clear, this is on a machine running Debian testing/bookworm. I'm not even going to try with stable, as the various Wayland components are too old.)
However, this fails with the exception:
I can't figure out why it can't load the
Playerctl
module. What am I doing wrong?Beta Was this translation helpful? Give feedback.
All reactions