#fvwm — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #fvwm, aggregated by home.social.
-
#cow has a webs(h)ite:
https://thomasadam.codeberg.page/cow/
It's meant to be a bit of fun (inspired from fvwm.org), but also useful.
Even without JS enabled, this site should still be functional.
One of the key things here is that the man pages are now generated when the website is -- including at the point of releases, which means, those who like HTML docs can now view that.
I am NOT a web person -- I hate frontend with a passion, and up until quite recently used to type <HTML> like that -- in upper case as that's what I recall being taught in the 1990s.
Anyway -- have fun!
-
#cow has a webs(h)ite:
https://thomasadam.codeberg.page/cow/
It's meant to be a bit of fun (inspired from fvwm.org), but also useful.
Even without JS enabled, this site should still be functional.
One of the key things here is that the man pages are now generated when the website is -- including at the point of releases, which means, those who like HTML docs can now view that.
I am NOT a web person -- I hate frontend with a passion, and up until quite recently used to type <HTML> like that -- in upper case as that's what I recall being taught in the 1990s.
Anyway -- have fun!
-
#cow has a webs(h)ite:
https://thomasadam.codeberg.page/cow/
It's meant to be a bit of fun (inspired from fvwm.org), but also useful.
Even without JS enabled, this site should still be functional.
One of the key things here is that the man pages are now generated when the website is -- including at the point of releases, which means, those who like HTML docs can now view that.
I am NOT a web person -- I hate frontend with a passion, and up until quite recently used to type <HTML> like that -- in upper case as that's what I recall being taught in the 1990s.
Anyway -- have fun!
-
#cow has a webs(h)ite:
https://thomasadam.codeberg.page/cow/
It's meant to be a bit of fun (inspired from fvwm.org), but also useful.
Even without JS enabled, this site should still be functional.
One of the key things here is that the man pages are now generated when the website is -- including at the point of releases, which means, those who like HTML docs can now view that.
I am NOT a web person -- I hate frontend with a passion, and up until quite recently used to type <HTML> like that -- in upper case as that's what I recall being taught in the 1990s.
Anyway -- have fun!
-
#cow has a webs(h)ite:
https://thomasadam.codeberg.page/cow/
It's meant to be a bit of fun (inspired from fvwm.org), but also useful.
Even without JS enabled, this site should still be functional.
One of the key things here is that the man pages are now generated when the website is -- including at the point of releases, which means, those who like HTML docs can now view that.
I am NOT a web person -- I hate frontend with a passion, and up until quite recently used to type <HTML> like that -- in upper case as that's what I recall being taught in the 1990s.
Anyway -- have fun!
-
Rather cheekily, I've just added a theme to CoW to emulate what the canoe WM provides:
https://github.com/roblillack/canoe
If anything it's an honour as this look-and-feel is excellent. I've attached a screenshot of the result in CoW.
The theme can be found in CoW's repository.
Thank you, Canoe!
-
Rather cheekily, I've just added a theme to CoW to emulate what the canoe WM provides:
https://github.com/roblillack/canoe
If anything it's an honour as this look-and-feel is excellent. I've attached a screenshot of the result in CoW.
The theme can be found in CoW's repository.
Thank you, Canoe!
-
Rather cheekily, I've just added a theme to CoW to emulate what the canoe WM provides:
https://github.com/roblillack/canoe
If anything it's an honour as this look-and-feel is excellent. I've attached a screenshot of the result in CoW.
The theme can be found in CoW's repository.
Thank you, Canoe!
-
Rather cheekily, I've just added a theme to CoW to emulate what the canoe WM provides:
https://github.com/roblillack/canoe
If anything it's an honour as this look-and-feel is excellent. I've attached a screenshot of the result in CoW.
The theme can be found in CoW's repository.
Thank you, Canoe!
-
Rather cheekily, I've just added a theme to CoW to emulate what the canoe WM provides:
https://github.com/roblillack/canoe
If anything it's an honour as this look-and-feel is excellent. I've attached a screenshot of the result in CoW.
The theme can be found in CoW's repository.
Thank you, Canoe!
-
-
-
-
-
-
CoW's first release -- v0.1 is live.
After many months of hard work, bug fixes, and feature requests, I've decided to release the first version of CoW:
You can download it here:
https://codeberg.org/thomasadam/cow/releases/tag/0.1
I still expect it to be full of bugs, etc., so do keep those coming in.
Thanks to @justine, @lgsl, and others for their help!
What is CoW? It's a window manager running in on top of the River compositor. See:
-
CoW's first release -- v0.1 is live.
After many months of hard work, bug fixes, and feature requests, I've decided to release the first version of CoW:
You can download it here:
https://codeberg.org/thomasadam/cow/releases/tag/0.1
I still expect it to be full of bugs, etc., so do keep those coming in.
Thanks to @justine, @lgsl, and others for their help!
What is CoW? It's a window manager running in on top of the River compositor. See:
-
CoW's first release -- v0.1 is live.
After many months of hard work, bug fixes, and feature requests, I've decided to release the first version of CoW:
You can download it here:
https://codeberg.org/thomasadam/cow/releases/tag/0.1
I still expect it to be full of bugs, etc., so do keep those coming in.
Thanks to @justine, @lgsl, and others for their help!
What is CoW? It's a window manager running in on top of the River compositor. See:
-
CoW's first release -- v0.1 is live.
After many months of hard work, bug fixes, and feature requests, I've decided to release the first version of CoW:
You can download it here:
https://codeberg.org/thomasadam/cow/releases/tag/0.1
I still expect it to be full of bugs, etc., so do keep those coming in.
Thanks to @justine, @lgsl, and others for their help!
What is CoW? It's a window manager running in on top of the River compositor. See:
-
CoW's first release -- v0.1 is live.
After many months of hard work, bug fixes, and feature requests, I've decided to release the first version of CoW:
You can download it here:
https://codeberg.org/thomasadam/cow/releases/tag/0.1
I still expect it to be full of bugs, etc., so do keep those coming in.
Thanks to @justine, @lgsl, and others for their help!
What is CoW? It's a window manager running in on top of the River compositor. See:
-
Based on the image renderer code already in CoW, I've now written an XPM3-compatible parser to support XPM images.
I was in two minds about this, but I also didn't want to depend on libxpm for this.
What I have works, and will be mostly useful for menu icons, application icons, etc. The "wm-icons" package still produces XPM files, and I'm already using some of those in cow.
What is cow? It's a window manager for Linux/*BSD written on top of the #river wayland compositor:
-
Based on the image renderer code already in CoW, I've now written an XPM3-compatible parser to support XPM images.
I was in two minds about this, but I also didn't want to depend on libxpm for this.
What I have works, and will be mostly useful for menu icons, application icons, etc. The "wm-icons" package still produces XPM files, and I'm already using some of those in cow.
What is cow? It's a window manager for Linux/*BSD written on top of the #river wayland compositor:
-
Based on the image renderer code already in CoW, I've now written an XPM3-compatible parser to support XPM images.
I was in two minds about this, but I also didn't want to depend on libxpm for this.
What I have works, and will be mostly useful for menu icons, application icons, etc. The "wm-icons" package still produces XPM files, and I'm already using some of those in cow.
What is cow? It's a window manager for Linux/*BSD written on top of the #river wayland compositor:
-
Based on the image renderer code already in CoW, I've now written an XPM3-compatible parser to support XPM images.
I was in two minds about this, but I also didn't want to depend on libxpm for this.
What I have works, and will be mostly useful for menu icons, application icons, etc. The "wm-icons" package still produces XPM files, and I'm already using some of those in cow.
What is cow? It's a window manager for Linux/*BSD written on top of the #river wayland compositor:
-
Based on the image renderer code already in CoW, I've now written an XPM3-compatible parser to support XPM images.
I was in two minds about this, but I also didn't want to depend on libxpm for this.
What I have works, and will be mostly useful for menu icons, application icons, etc. The "wm-icons" package still produces XPM files, and I'm already using some of those in cow.
What is cow? It's a window manager for Linux/*BSD written on top of the #river wayland compositor:
-
It's now possible to define icons in menus.
There's two configurable options:
menu-style icon.path ~/.config/cow/icons:/usr/local/share/icons
This tells CoW where to look for icons.
menu-style icon.size 16
This sets the size.
In practice, it's therefore possible to, say:
menu-add -I foo.png "Foo"
Screenshot attached,
Thanks to @justine for all her hard work in testing this, and coming up with the proposal in the first place.
-
It's now possible to define icons in menus.
There's two configurable options:
menu-style icon.path ~/.config/cow/icons:/usr/local/share/icons
This tells CoW where to look for icons.
menu-style icon.size 16
This sets the size.
In practice, it's therefore possible to, say:
menu-add -I foo.png "Foo"
Screenshot attached,
Thanks to @justine for all her hard work in testing this, and coming up with the proposal in the first place.
-
It's now possible to define icons in menus.
There's two configurable options:
menu-style icon.path ~/.config/cow/icons:/usr/local/share/icons
This tells CoW where to look for icons.
menu-style icon.size 16
This sets the size.
In practice, it's therefore possible to, say:
menu-add -I foo.png "Foo"
Screenshot attached,
Thanks to @justine for all her hard work in testing this, and coming up with the proposal in the first place.
-
It's now possible to define icons in menus.
There's two configurable options:
menu-style icon.path ~/.config/cow/icons:/usr/local/share/icons
This tells CoW where to look for icons.
menu-style icon.size 16
This sets the size.
In practice, it's therefore possible to, say:
menu-add -I foo.png "Foo"
Screenshot attached,
Thanks to @justine for all her hard work in testing this, and coming up with the proposal in the first place.
-
It's now possible to define icons in menus.
There's two configurable options:
menu-style icon.path ~/.config/cow/icons:/usr/local/share/icons
This tells CoW where to look for icons.
menu-style icon.size 16
This sets the size.
In practice, it's therefore possible to, say:
menu-add -I foo.png "Foo"
Screenshot attached,
Thanks to @justine for all her hard work in testing this, and coming up with the proposal in the first place.
-
Context bindings.
It's now possible in #cow to bind mouse actions to different parts of a window border -- all four sides, and all four corners. Additionally, one can now bind actions to icons and the root window.
For example:
```
mouse I:0+right "menu-show WindowOps"
```Pops up a menu to perform window operations, when the right mouse button is pressed on an icon. Actions defined in that menu will run in context of the non-iconified window (as opposed to the icon itself).
Key bindings are supported, too, but they can only be bound to titlebar buttons.
This is similar to what #fvwm used to allow.
Cc: @stuartl
CoW, is a window manager on top of the River compositor.
-
Context bindings.
It's now possible in #cow to bind mouse actions to different parts of a window border -- all four sides, and all four corners. Additionally, one can now bind actions to icons and the root window.
For example:
```
mouse I:0+right "menu-show WindowOps"
```Pops up a menu to perform window operations, when the right mouse button is pressed on an icon. Actions defined in that menu will run in context of the non-iconified window (as opposed to the icon itself).
Key bindings are supported, too, but they can only be bound to titlebar buttons.
This is similar to what #fvwm used to allow.
Cc: @stuartl
CoW, is a window manager on top of the River compositor.
-
Context bindings.
It's now possible in #cow to bind mouse actions to different parts of a window border -- all four sides, and all four corners. Additionally, one can now bind actions to icons and the root window.
For example:
```
mouse I:0+right "menu-show WindowOps"
```Pops up a menu to perform window operations, when the right mouse button is pressed on an icon. Actions defined in that menu will run in context of the non-iconified window (as opposed to the icon itself).
Key bindings are supported, too, but they can only be bound to titlebar buttons.
This is similar to what #fvwm used to allow.
Cc: @stuartl
CoW, is a window manager on top of the River compositor.
-
Context bindings.
It's now possible in #cow to bind mouse actions to different parts of a window border -- all four sides, and all four corners. Additionally, one can now bind actions to icons and the root window.
For example:
```
mouse I:0+right "menu-show WindowOps"
```Pops up a menu to perform window operations, when the right mouse button is pressed on an icon. Actions defined in that menu will run in context of the non-iconified window (as opposed to the icon itself).
Key bindings are supported, too, but they can only be bound to titlebar buttons.
This is similar to what #fvwm used to allow.
Cc: @stuartl
CoW, is a window manager on top of the River compositor.
-
Context bindings.
It's now possible in #cow to bind mouse actions to different parts of a window border -- all four sides, and all four corners. Additionally, one can now bind actions to icons and the root window.
For example:
```
mouse I:0+right "menu-show WindowOps"
```Pops up a menu to perform window operations, when the right mouse button is pressed on an icon. Actions defined in that menu will run in context of the non-iconified window (as opposed to the icon itself).
Key bindings are supported, too, but they can only be bound to titlebar buttons.
This is similar to what #fvwm used to allow.
Cc: @stuartl
CoW, is a window manager on top of the River compositor.
-
I'm still playing around with this, but I suspect I'll merge it later.
You can now style menus individually via the `menu-style` command.
See screenshot attached.
CoW is a stacking window manager running on top of River:
-
I'm still playing around with this, but I suspect I'll merge it later.
You can now style menus individually via the `menu-style` command.
See screenshot attached.
CoW is a stacking window manager running on top of River:
-
I'm still playing around with this, but I suspect I'll merge it later.
You can now style menus individually via the `menu-style` command.
See screenshot attached.
CoW is a stacking window manager running on top of River:
-
I'm still playing around with this, but I suspect I'll merge it later.
You can now style menus individually via the `menu-style` command.
See screenshot attached.
CoW is a stacking window manager running on top of River:
-
I'm still playing around with this, but I suspect I'll merge it later.
You can now style menus individually via the `menu-style` command.
See screenshot attached.
CoW is a stacking window manager running on top of River:
-
@stuartl Hi Stuart. Re point 2., I now have an open PR which implements a PR for a `window-list` command.
See the `ta/window-list` branch. It can be filtered and sorted, and there's also a -F for filtering, too.
There's also typeahead.
It was a lot of fun to implement -- I might tweak it in the future, bit how it works now is how I intend it to work.
Let me know how you get on.
-
@stuartl Hi Stuart. Re point 2., I now have an open PR which implements a PR for a `window-list` command.
See the `ta/window-list` branch. It can be filtered and sorted, and there's also a -F for filtering, too.
There's also typeahead.
It was a lot of fun to implement -- I might tweak it in the future, bit how it works now is how I intend it to work.
Let me know how you get on.
-
@stuartl Hi Stuart. Re point 2., I now have an open PR which implements a PR for a `window-list` command.
See the `ta/window-list` branch. It can be filtered and sorted, and there's also a -F for filtering, too.
There's also typeahead.
It was a lot of fun to implement -- I might tweak it in the future, bit how it works now is how I intend it to work.
Let me know how you get on.
-
@stuartl Hi Stuart. Re point 2., I now have an open PR which implements a PR for a `window-list` command.
See the `ta/window-list` branch. It can be filtered and sorted, and there's also a -F for filtering, too.
There's also typeahead.
It was a lot of fun to implement -- I might tweak it in the future, bit how it works now is how I intend it to work.
Let me know how you get on.
-
@stuartl Hi Stuart. Re point 2., I now have an open PR which implements a PR for a `window-list` command.
See the `ta/window-list` branch. It can be filtered and sorted, and there's also a -F for filtering, too.
There's also typeahead.
It was a lot of fun to implement -- I might tweak it in the future, bit how it works now is how I intend it to work.
Let me know how you get on.
-
@stuartl re point 3 -- I do not know if Wayland has anything akin to xdd-menus. I don't think it does. I think the preferred way is to use `rofi` or one of the many typeahead applications to launch what you want. We might be back to the days of defining your own menus!
Currently, there is no way in CoW to PipeRead menus, or indeed anything like the DynamicMenu command. This is deliberate as it adds a lot of complexity and overhead I'm not sure I want to support. I will if the demand is there though. That said, there's nothing stopping you creating menus via `moocow`.
-
@stuartl re point 3 -- I do not know if Wayland has anything akin to xdd-menus. I don't think it does. I think the preferred way is to use `rofi` or one of the many typeahead applications to launch what you want. We might be back to the days of defining your own menus!
Currently, there is no way in CoW to PipeRead menus, or indeed anything like the DynamicMenu command. This is deliberate as it adds a lot of complexity and overhead I'm not sure I want to support. I will if the demand is there though. That said, there's nothing stopping you creating menus via `moocow`.
-
@stuartl re point 3 -- I do not know if Wayland has anything akin to xdd-menus. I don't think it does. I think the preferred way is to use `rofi` or one of the many typeahead applications to launch what you want. We might be back to the days of defining your own menus!
Currently, there is no way in CoW to PipeRead menus, or indeed anything like the DynamicMenu command. This is deliberate as it adds a lot of complexity and overhead I'm not sure I want to support. I will if the demand is there though. That said, there's nothing stopping you creating menus via `moocow`.
-
@stuartl re point 3 -- I do not know if Wayland has anything akin to xdd-menus. I don't think it does. I think the preferred way is to use `rofi` or one of the many typeahead applications to launch what you want. We might be back to the days of defining your own menus!
Currently, there is no way in CoW to PipeRead menus, or indeed anything like the DynamicMenu command. This is deliberate as it adds a lot of complexity and overhead I'm not sure I want to support. I will if the demand is there though. That said, there's nothing stopping you creating menus via `moocow`.
-
@stuartl re point 3 -- I do not know if Wayland has anything akin to xdd-menus. I don't think it does. I think the preferred way is to use `rofi` or one of the many typeahead applications to launch what you want. We might be back to the days of defining your own menus!
Currently, there is no way in CoW to PipeRead menus, or indeed anything like the DynamicMenu command. This is deliberate as it adds a lot of complexity and overhead I'm not sure I want to support. I will if the demand is there though. That said, there's nothing stopping you creating menus via `moocow`.
-
@stuartl Hi, Stuart.
I'm slowly working my way through this list, as I think it's valuable.
In terms of your first point about moving/resizing windows to fit the different dimensions of your screen, see:
https://codeberg.org/thomasadam/cow/pulls/204
I think this is what you were after. You can checkout the `ta/vp-geometry` branch. Note the examples in the PR description as well.
I'm also working on the windowlist menu. I had hoped to defer this to external applications, but a lot of that depends on which wayland protocol is used to enumerate that information. So having it builtin is probably the better option for simple tasks.
-
@stuartl Hi, Stuart.
I'm slowly working my way through this list, as I think it's valuable.
In terms of your first point about moving/resizing windows to fit the different dimensions of your screen, see:
https://codeberg.org/thomasadam/cow/pulls/204
I think this is what you were after. You can checkout the `ta/vp-geometry` branch. Note the examples in the PR description as well.
I'm also working on the windowlist menu. I had hoped to defer this to external applications, but a lot of that depends on which wayland protocol is used to enumerate that information. So having it builtin is probably the better option for simple tasks.
-
@stuartl Hi, Stuart.
I'm slowly working my way through this list, as I think it's valuable.
In terms of your first point about moving/resizing windows to fit the different dimensions of your screen, see:
https://codeberg.org/thomasadam/cow/pulls/204
I think this is what you were after. You can checkout the `ta/vp-geometry` branch. Note the examples in the PR description as well.
I'm also working on the windowlist menu. I had hoped to defer this to external applications, but a lot of that depends on which wayland protocol is used to enumerate that information. So having it builtin is probably the better option for simple tasks.
-
@stuartl Hi, Stuart.
I'm slowly working my way through this list, as I think it's valuable.
In terms of your first point about moving/resizing windows to fit the different dimensions of your screen, see:
https://codeberg.org/thomasadam/cow/pulls/204
I think this is what you were after. You can checkout the `ta/vp-geometry` branch. Note the examples in the PR description as well.
I'm also working on the windowlist menu. I had hoped to defer this to external applications, but a lot of that depends on which wayland protocol is used to enumerate that information. So having it builtin is probably the better option for simple tasks.
-
@stuartl Hi, Stuart.
I'm slowly working my way through this list, as I think it's valuable.
In terms of your first point about moving/resizing windows to fit the different dimensions of your screen, see:
https://codeberg.org/thomasadam/cow/pulls/204
I think this is what you were after. You can checkout the `ta/vp-geometry` branch. Note the examples in the PR description as well.
I'm also working on the windowlist menu. I had hoped to defer this to external applications, but a lot of that depends on which wayland protocol is used to enumerate that information. So having it builtin is probably the better option for simple tasks.