#ewmh — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #ewmh, aggregated by home.social.
-
CW: Layers!
It has come to my attention that many people are under the impression that your window manager, desktop environment, and operating system installation are all closely interlinked so that the only practical way of switching one of these is to re-install.
This is not the case.
A desktop environment is a set of applications that use a particular set of libraries to achieve a more or less unified look-and-feel. One of those applications is usually a window manager.
Window managers are largely interchangeable with each other thanks to the invention of Extended Window Manager Hints about 20 years ago.
The only partial truth of this impression of unity is that installing and running more desktop environments and more window managers will incur a larger cost in disk space (to store them) and RAM (when loading multiple libraries). Back when a nice desktop machine had 128MB of RAM and a 2 GB disk, that could be concerning.
A Raspberry Pi now comes with up to 8GB of RAM (64x more) and a 128GB microSD card or a 1 TB SSD. Space is no longer a concern on that scale.
Go forth and experiment. Install multiple desktops simultaneously, choose between them when you start your X11 session, and figure out what you like.
-
CW: Layers!
It has come to my attention that many people are under the impression that your window manager, desktop environment, and operating system installation are all closely interlinked so that the only practical way of switching one of these is to re-install.
This is not the case.
A desktop environment is a set of applications that use a particular set of libraries to achieve a more or less unified look-and-feel. One of those applications is usually a window manager.
Window managers are largely interchangeable with each other thanks to the invention of Extended Window Manager Hints about 20 years ago.
The only partial truth of this impression of unity is that installing and running more desktop environments and more window managers will incur a larger cost in disk space (to store them) and RAM (when loading multiple libraries). Back when a nice desktop machine had 128MB of RAM and a 2 GB disk, that could be concerning.
A Raspberry Pi now comes with up to 8GB of RAM (64x more) and a 128GB microSD card or a 1 TB SSD. Space is no longer a concern on that scale.
Go forth and experiment. Install multiple desktops simultaneously, choose between them when you start your X11 session, and figure out what you like.
-
CW: Layers!
It has come to my attention that many people are under the impression that your window manager, desktop environment, and operating system installation are all closely interlinked so that the only practical way of switching one of these is to re-install.
This is not the case.
A desktop environment is a set of applications that use a particular set of libraries to achieve a more or less unified look-and-feel. One of those applications is usually a window manager.
Window managers are largely interchangeable with each other thanks to the invention of Extended Window Manager Hints about 20 years ago.
The only partial truth of this impression of unity is that installing and running more desktop environments and more window managers will incur a larger cost in disk space (to store them) and RAM (when loading multiple libraries). Back when a nice desktop machine had 128MB of RAM and a 2 GB disk, that could be concerning.
A Raspberry Pi now comes with up to 8GB of RAM (64x more) and a 128GB microSD card or a 1 TB SSD. Space is no longer a concern on that scale.
Go forth and experiment. Install multiple desktops simultaneously, choose between them when you start your X11 session, and figure out what you like.
-
CW: Layers!
It has come to my attention that many people are under the impression that your window manager, desktop environment, and operating system installation are all closely interlinked so that the only practical way of switching one of these is to re-install.
This is not the case.
A desktop environment is a set of applications that use a particular set of libraries to achieve a more or less unified look-and-feel. One of those applications is usually a window manager.
Window managers are largely interchangeable with each other thanks to the invention of Extended Window Manager Hints about 20 years ago.
The only partial truth of this impression of unity is that installing and running more desktop environments and more window managers will incur a larger cost in disk space (to store them) and RAM (when loading multiple libraries). Back when a nice desktop machine had 128MB of RAM and a 2 GB disk, that could be concerning.
A Raspberry Pi now comes with up to 8GB of RAM (64x more) and a 128GB microSD card or a 1 TB SSD. Space is no longer a concern on that scale.
Go forth and experiment. Install multiple desktops simultaneously, choose between them when you start your X11 session, and figure out what you like.
-
CW: Layers!
It has come to my attention that many people are under the impression that your window manager, desktop environment, and operating system installation are all closely interlinked so that the only practical way of switching one of these is to re-install.
This is not the case.
A desktop environment is a set of applications that use a particular set of libraries to achieve a more or less unified look-and-feel. One of those applications is usually a window manager.
Window managers are largely interchangeable with each other thanks to the invention of Extended Window Manager Hints about 20 years ago.
The only partial truth of this impression of unity is that installing and running more desktop environments and more window managers will incur a larger cost in disk space (to store them) and RAM (when loading multiple libraries). Back when a nice desktop machine had 128MB of RAM and a 2 GB disk, that could be concerning.
A Raspberry Pi now comes with up to 8GB of RAM (64x more) and a 128GB microSD card or a 1 TB SSD. Space is no longer a concern on that scale.
Go forth and experiment. Install multiple desktops simultaneously, choose between them when you start your X11 session, and figure out what you like.
-
Guess I *did* enter "shady areas" writing commit messages like this:
https://github.com/Zirias/qxmoji/commit/2a404cd195619265559f9cced21f89ce3d129f40
In theory, all #EWMH window managers should behave the same, I thought ... 😂🙈
-
Guess I *did* enter "shady areas" writing commit messages like this:
https://github.com/Zirias/qxmoji/commit/2a404cd195619265559f9cced21f89ce3d129f40
In theory, all #EWMH window managers should behave the same, I thought ... 😂🙈
-
Guess I *did* enter "shady areas" writing commit messages like this:
https://github.com/Zirias/qxmoji/commit/2a404cd195619265559f9cced21f89ce3d129f40
In theory, all #EWMH window managers should behave the same, I thought ... 😂🙈
-
Guess I *did* enter "shady areas" writing commit messages like this:
https://github.com/Zirias/qxmoji/commit/2a404cd195619265559f9cced21f89ce3d129f40
In theory, all #EWMH window managers should behave the same, I thought ... 😂🙈
-
Guess I *did* enter "shady areas" writing commit messages like this:
https://github.com/Zirias/qxmoji/commit/2a404cd195619265559f9cced21f89ce3d129f40
In theory, all #EWMH window managers should behave the same, I thought ... 😂🙈
-
Deep down the #X11 (#xcb) rabbit hole now.
I decided to add a tray icon. I want it optional, with configurable behavior (minimize-to-tray, close-to-tray, no-tray).
Adding this thing was super simple with Qt. Getting anything other than the default behavior ... not so much. Doing lots of things with plain #xcb now.
I'm stuck at hiding the tool from a taskbar. #EWMH has _NET_WM_STATE_SKIP_TASKBAR. In #fvwm (#fvwm3), this works when setting it before the window gets mapped. Sending it as a "client message" when the window is already mapped seems to be just ignored 😠
I then tried #KDE (#kwin). Hm well, doesn't even honor the _NET_WM_STATE property set on the window before mapping it, IOW, it's *always* shown in the taskbar.
WTF? 😖❓
-
Deep down the #X11 (#xcb) rabbit hole now.
I decided to add a tray icon. I want it optional, with configurable behavior (minimize-to-tray, close-to-tray, no-tray).
Adding this thing was super simple with Qt. Getting anything other than the default behavior ... not so much. Doing lots of things with plain #xcb now.
I'm stuck at hiding the tool from a taskbar. #EWMH has _NET_WM_STATE_SKIP_TASKBAR. In #fvwm (#fvwm3), this works when setting it before the window gets mapped. Sending it as a "client message" when the window is already mapped seems to be just ignored 😠
I then tried #KDE (#kwin). Hm well, doesn't even honor the _NET_WM_STATE property set on the window before mapping it, IOW, it's *always* shown in the taskbar.
WTF? 😖❓
-
Deep down the #X11 (#xcb) rabbit hole now.
I decided to add a tray icon. I want it optional, with configurable behavior (minimize-to-tray, close-to-tray, no-tray).
Adding this thing was super simple with Qt. Getting anything other than the default behavior ... not so much. Doing lots of things with plain #xcb now.
I'm stuck at hiding the tool from a taskbar. #EWMH has _NET_WM_STATE_SKIP_TASKBAR. In #fvwm (#fvwm3), this works when setting it before the window gets mapped. Sending it as a "client message" when the window is already mapped seems to be just ignored 😠
I then tried #KDE (#kwin). Hm well, doesn't even honor the _NET_WM_STATE property set on the window before mapping it, IOW, it's *always* shown in the taskbar.
WTF? 😖❓
-
Deep down the #X11 (#xcb) rabbit hole now.
I decided to add a tray icon. I want it optional, with configurable behavior (minimize-to-tray, close-to-tray, no-tray).
Adding this thing was super simple with Qt. Getting anything other than the default behavior ... not so much. Doing lots of things with plain #xcb now.
I'm stuck at hiding the tool from a taskbar. #EWMH has _NET_WM_STATE_SKIP_TASKBAR. In #fvwm (#fvwm3), this works when setting it before the window gets mapped. Sending it as a "client message" when the window is already mapped seems to be just ignored 😠
I then tried #KDE (#kwin). Hm well, doesn't even honor the _NET_WM_STATE property set on the window before mapping it, IOW, it's *always* shown in the taskbar.
WTF? 😖❓
-
Deep down the #X11 (#xcb) rabbit hole now.
I decided to add a tray icon. I want it optional, with configurable behavior (minimize-to-tray, close-to-tray, no-tray).
Adding this thing was super simple with Qt. Getting anything other than the default behavior ... not so much. Doing lots of things with plain #xcb now.
I'm stuck at hiding the tool from a taskbar. #EWMH has _NET_WM_STATE_SKIP_TASKBAR. In #fvwm (#fvwm3), this works when setting it before the window gets mapped. Sending it as a "client message" when the window is already mapped seems to be just ignored 😠
I then tried #KDE (#kwin). Hm well, doesn't even honor the _NET_WM_STATE property set on the window before mapping it, IOW, it's *always* shown in the taskbar.
WTF? 😖❓
-
So it appears to me that under #wayland, #portals are the reimplementation of the #ewmh spec under #xorg. The sad thing here is I’m not observing any oversight and governance to these protocols.
When I last mentioned this about mini icon support, that discussion went south very quickly. Without proper governance, as there was with the EWMH, such discussions become a free-for-all with people giving their opinion about something they don’t understand.
Given that #wayland comes from former #xorg devs who probably know about EWMH, I’d expect better. This lack of governance is appalling and needs to change. #portals need better governance than random ignorant people proposing extensions.
-
So it appears to me that under #wayland, #portals are the reimplementation of the #ewmh spec under #xorg. The sad thing here is I’m not observing any oversight and governance to these protocols.
When I last mentioned this about mini icon support, that discussion went south very quickly. Without proper governance, as there was with the EWMH, such discussions become a free-for-all with people giving their opinion about something they don’t understand.
Given that #wayland comes from former #xorg devs who probably know about EWMH, I’d expect better. This lack of governance is appalling and needs to change. #portals need better governance than random ignorant people proposing extensions.
-
So it appears to me that under #wayland, #portals are the reimplementation of the #ewmh spec under #xorg. The sad thing here is I’m not observing any oversight and governance to these protocols.
When I last mentioned this about mini icon support, that discussion went south very quickly. Without proper governance, as there was with the EWMH, such discussions become a free-for-all with people giving their opinion about something they don’t understand.
Given that #wayland comes from former #xorg devs who probably know about EWMH, I’d expect better. This lack of governance is appalling and needs to change. #portals need better governance than random ignorant people proposing extensions.
-
So it appears to me that under #wayland, #portals are the reimplementation of the #ewmh spec under #xorg. The sad thing here is I’m not observing any oversight and governance to these protocols.
When I last mentioned this about mini icon support, that discussion went south very quickly. Without proper governance, as there was with the EWMH, such discussions become a free-for-all with people giving their opinion about something they don’t understand.
Given that #wayland comes from former #xorg devs who probably know about EWMH, I’d expect better. This lack of governance is appalling and needs to change. #portals need better governance than random ignorant people proposing extensions.
-
So it appears to me that under #wayland, #portals are the reimplementation of the #ewmh spec under #xorg. The sad thing here is I’m not observing any oversight and governance to these protocols.
When I last mentioned this about mini icon support, that discussion went south very quickly. Without proper governance, as there was with the EWMH, such discussions become a free-for-all with people giving their opinion about something they don’t understand.
Given that #wayland comes from former #xorg devs who probably know about EWMH, I’d expect better. This lack of governance is appalling and needs to change. #portals need better governance than random ignorant people proposing extensions.