#fvwm3 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #fvwm3, aggregated by home.social.
-
More from me!
This time, icons...
With this change, icons are now more of a first-class citizen in CoW.
It's possible to assign icons (either SVG or PNG) to windows, via the `decor` command.
The cow(!) man page has a dedicated icon section so you can see how to do that.
By default, cow ships with an icon which mimics what MWM has.
Icons can now be moved around the desktop, and windows remember their icon position.
The new icon-reset command will put icons back to their default position, which is managed by cow. This is similar to the `PlaceAgain icon` command from #fvwm and #fvwm3
Enjoy!
-
More from me!
This time, icons...
With this change, icons are now more of a first-class citizen in CoW.
It's possible to assign icons (either SVG or PNG) to windows, via the `decor` command.
The cow(!) man page has a dedicated icon section so you can see how to do that.
By default, cow ships with an icon which mimics what MWM has.
Icons can now be moved around the desktop, and windows remember their icon position.
The new icon-reset command will put icons back to their default position, which is managed by cow. This is similar to the `PlaceAgain icon` command from #fvwm and #fvwm3
Enjoy!
-
Hello all,
fvwm3-1.1.5 has been released.
See:
https://github.com/fvwmorg/fvwm3/releases/tag/1.1.5
This is mostly a bug-fix release. FvwmPrompt has been simplified which I hope eases issues with downstream maintainers.
FvwmConsole has now gone -- use FvwmCommand or FvwmPrompt.
Enjoy!
-
Hello all,
fvwm3-1.1.5 has been released.
See:
https://github.com/fvwmorg/fvwm3/releases/tag/1.1.5
This is mostly a bug-fix release. FvwmPrompt has been simplified which I hope eases issues with downstream maintainers.
FvwmConsole has now gone -- use FvwmCommand or FvwmPrompt.
Enjoy!
-
CoW has now gained a new "module" -- cowident.
The image below shows what it does. When you run it, it will force you to select a window to then report properties on.
It's analogous to FvwmIdent from #fvwm3
Not the sexiest thing in the world, I know, but maybe useful both for those tweaking their config, and for diagnostic purposes.
That's why #FvwmIdent was created -- to allow for diagnostics.
-
CoW has now gained a new "module" -- cowident.
The image below shows what it does. When you run it, it will force you to select a window to then report properties on.
It's analogous to FvwmIdent from #fvwm3
Not the sexiest thing in the world, I know, but maybe useful both for those tweaking their config, and for diagnostic purposes.
That's why #FvwmIdent was created -- to allow for diagnostics.
-
Let's play spot the difference!
One, both, or none of two screenshots are from fvwm3.
Can you guess which?
If not, could you maybe guess is one of the screenshots is based on wayland? ;)
In all seriousness, I'm trying to emulate the fvwm/mwm look in #hikari -- and I think the results are impressive, especially if you can't tell which image is from which #wm.
-
#fvwm3 #autotools #meson #buildsystems
A little over six months ago, I said the following:
https://bsd.network/web/@thomasadam/113340194570527011
Since six months has passed, I've now pushed to `main` a PR which does just that -- removes autotools from #fvwm3 and replaces it with meson:
https://github.com/fvwmorg/fvwm3/pull/1191
So this has been your warning.
When I release fvwm3-1.1.3, it will be using meson only.
Any questions, please do let me know. I hope downstream packagers have made the transition. :)
-
#fvwm3 #autotools #meson #buildsystems
A little over six months ago, I said the following:
https://bsd.network/web/@thomasadam/113340194570527011
Since six months has passed, I've now pushed to `main` a PR which does just that -- removes autotools from #fvwm3 and replaces it with meson:
https://github.com/fvwmorg/fvwm3/pull/1191
So this has been your warning.
When I release fvwm3-1.1.3, it will be using meson only.
Any questions, please do let me know. I hope downstream packagers have made the transition. :)
-
#fvwm3 #autotools #meson #muon #buildsystem
Hey all! Please note that although fvwm3-1.1.1 is close to being relesaed, there's still a few more things left to do.
Before that point, I'd like to take the opportunity to mention that as of fvwm3-1.1.1 fvwm3 is officially using meson/muon as the buildsystem of choice.
Autotools has been a tremendous help over the years. Heck, fvwm as a project started long before autotools existed.
But as technology changes, newer buildsystem alternatives have come along making better use of hardware, compilation speeds, etc.
Indeed, because of fvwm's age -- there's a tonne of custom m4 macros -- some of which are to work around issues long since gone. With autotools recently deprecating many of these, maintaining this was becoming difficult. Hence the change.
A six-month window exists once fvwm3-1.1.1 is released for downstream packagers to make the move from autotools to meson.
The `main` branch in the fvwm3 repository contains both buildsystems. Please give meson some testing!
A huge thanks goes to Kanjie (Matt Jolly) -- without whom none of this work would have been possible. Thanks, Matt!
For more specific details. please see: https://github.com/fvwmorg/fvwm3/discussions/1068
Questions? I'm here...
-
#fvwm3 #autotools #meson #muon #buildsystem
Hey all! Please note that although fvwm3-1.1.1 is close to being relesaed, there's still a few more things left to do.
Before that point, I'd like to take the opportunity to mention that as of fvwm3-1.1.1 fvwm3 is officially using meson/muon as the buildsystem of choice.
Autotools has been a tremendous help over the years. Heck, fvwm as a project started long before autotools existed.
But as technology changes, newer buildsystem alternatives have come along making better use of hardware, compilation speeds, etc.
Indeed, because of fvwm's age -- there's a tonne of custom m4 macros -- some of which are to work around issues long since gone. With autotools recently deprecating many of these, maintaining this was becoming difficult. Hence the change.
A six-month window exists once fvwm3-1.1.1 is released for downstream packagers to make the move from autotools to meson.
The `main` branch in the fvwm3 repository contains both buildsystems. Please give meson some testing!
A huge thanks goes to Kanjie (Matt Jolly) -- without whom none of this work would have been possible. Thanks, Matt!
For more specific details. please see: https://github.com/fvwmorg/fvwm3/discussions/1068
Questions? I'm here...
-
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? 😖❓