# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 23
# self = https://watcher.sour.is/conv/3mtkrua
The name Waysome implies that this is a Wayland compositor similar to awesome. I never gave it a try and it appears to be abandoned.
awesome was a great X11 window manager. It handled all the dirty stuff and allowed you to write your window management functions in Lua. (I only stopped using awesome because I wanted to learn more about X11 window management.)
Should I write an awesome-like Wayland compositor? It would allow you to write your own custom window management *logic*. That’s so much better than just offering *configuration*. I don’t know if there’s any demand for this in the community, but it is what I would like to use.
It’s just *so much* work … 😮💨
The name Waysome implies that this is a Wayland compositor similar to awesome. I never gave it a try and it appears to be abandoned.
awesome was a great X11 window manager. It handled all the dirty stuff and allowed you to write your window management functions in Lua. (I only stopped using awesome because I wanted to learn more about X11 window management.)
Should I write an awesome-like Wayland compositor? It would allow you to write your own custom window management *logic*. That’s so much better than just offering *configuration*. I don’t know if there’s any demand for this in the community, but it is what I would like to use.
It’s just *so much* work … 😮💨
The name Waysome implies that this is a Wayland compositor similar to awesome. I never gave it a try and it appears to be abandoned.
awesome was a great X11 window manager. It handled all the dirty stuff and allowed you to write your window management functions in Lua. (I only stopped using awesome because I wanted to learn more about X11 window management.)
Should I write an awesome-like Wayland compositor? It would allow you to write your own custom window management *logic*. That’s so much better than just offering *configuration*. I don’t know if there’s any demand for this in the community, but it is what I would like to use.
It’s just *so much* work … 😮💨
@movq I switched to cwm from tiling window managers.
So many window managers! I think configuring, tweaking, and trying and testing window managers has to be a hobby, for sure. Writing one is probably the pinnacle on such hobby, so I would say, go for it @movq! :-D
So many window managers! I think configuring, tweaking, and trying as testing window managers has to be a hobby, for sure. Writing one is probably the pinnacle on such hobby, so I would say, go for it @movq! :-D
@david Been there, done that. 😅
I don’t really want to repeat that for Wayland, though. Especially not since you have to implement an entire “display server”, not just a window manager. (You’d have to implement the equivalent of “X11 server + window manager + compositor”.) There is a library to help you with that (https://gitlab.freedesktop.org/wlroots/wlroots/), but it’s still a ton of work.
I don’t want to do it. But there’s no software out there that does what I want. 😩 So I’ll either write my own thing or live with a shoddy suboptimal solution.
Or I’ll have to come up with something else entirely.
(For now, it’s easy to just keep ignoring Wayland.)
@david Been there, done that. 😅
I don’t really want to repeat that for Wayland, though. Especially not since you have to implement an entire “display server”, not just a window manager. (You’d have to implement the equivalent of “X11 server + window manager + compositor”.) There is a library to help you with that (https://gitlab.freedesktop.org/wlroots/wlroots/), but it’s still a ton of work.
I don’t want to do it. But there’s no software out there that does what I want. 😩 So I’ll either write my own thing or live with a shoddy suboptimal solution.
Or I’ll have to come up with something else entirely.
(For now, it’s easy to just keep ignoring Wayland.)
@david Been there, done that. 😅
I don’t really want to repeat that for Wayland, though. Especially not since you have to implement an entire “display server”, not just a window manager. (You’d have to implement the equivalent of “X11 server + window manager + compositor”.) There is a library to help you with that (https://gitlab.freedesktop.org/wlroots/wlroots/), but it’s still a ton of work.
I don’t want to do it. But there’s no software out there that does what I want. 😩 So I’ll either write my own thing or live with a shoddy suboptimal solution.
Or I’ll have to come up with something else entirely.
(For now, it’s easy to just keep ignoring Wayland.)
@movq wow, katriawm looks really good! Are the "motif" like windows part of it? I truly like their look; they bring back many very fond memories of CDE. As for the job involved as you describe it… hmm, I think I agree, it would be a lot of work. Now, think about the fulfilment that will bring. 😅
@david You mean the status bars? That’s another project, bevelbar. But yeah, both bevelbar and katria’s borders were loosely modeled after CDE. 🥳
I never used CDE myself, other than some quick tests in 2012, after it had been open sourced. Wow, that’s already 10 years ago …
@david You mean the status bars? That’s another project, bevelbar. But yeah, both bevelbar and katria’s borders were loosely modeled after CDE. 🥳
I never used CDE myself, other than some quick tests in 2012, after it had been open sourced. Wow, that’s already 10 years ago …
@david You mean the status bars? That’s another project, bevelbar. But yeah, both bevelbar and katria’s borders were loosely modeled after CDE. 🥳
I never used CDE myself, other than some quick tests in 2012, after it had been open sourced. Wow, that’s already 10 years ago …
After KDE 3.5 (best KDE in my opinion) and then 4 back in the days I switched to wmii and finally setteled on i3. Can't remember the reason to trade wmii for i3. But tiling window managers are the absolute holy grail. I can't work with the others anymore. They're just making for an awful experience. So what exactly do you have in mind for your new window manager, @movq?
@lyse The goal would be to have the compositor (= “the WM”) provide a Lua API, a bit like it was in awesomewm. All the actual window *management* (and not input handling, monitor management, clipboard and all the other junk that you have to implement in Wayland) would then be implemented in Lua. And, if you don’t like the defaults, you can supply your own Lua scripts.
I don’t know if this works in practice. I’d have to try. 🤷
If I were to write another WM for X11, I’d do the same thing. (Or I’d go back to awesomewm.)=
@lyse The goal would be to have the compositor (= “the WM”) provide a Lua API, a bit like it was in awesomewm. All the actual window *management* (and not input handling, monitor management, clipboard and all the other junk that you have to implement in Wayland) would then be implemented in Lua. And, if you don’t like the defaults, you can supply your own Lua scripts.
I don’t know if this works in practice. I’d have to try. 🤷
If I were to write another WM for X11, I’d do the same thing. (Or I’d go back to awesomewm.)=
@lyse The goal would be to have the compositor (= “the WM”) provide a Lua API, a bit like it was in awesomewm. All the actual window *management* (and not input handling, monitor management, clipboard and all the other junk that you have to implement in Wayland) would then be implemented in Lua. And, if you don’t like the defaults, you can supply your own Lua scripts.
I don’t know if this works in practice. I’d have to try. 🤷
If I were to write another WM for X11, I’d do the same thing. (Or I’d go back to awesomewm.)=
@movq Ah, okay. Well then, happy hacking in the next decades. ;-)
@vain
> River is a dynamic tiling Wayland compositor with flexible runtime configuration.
👉 river
@ionores Gave it a shot, froze my machine. 🙈 Maybe I’ll try again in the future.
@ionores Gave it a shot, froze my machine. 🙈 Maybe I’ll try again in the future.
@ionores Gave it a shot, froze my machine. 🙈 Maybe I’ll try again in the future.