Thomas Adam @thomasadam@bsd.network

#xwinman #wm #des

Hi all,

I've had a few instances of people contacting me about the site of xwinman.org

When I mirrored it, I did say as just that -- a mirror of the information, which is found here:

https://xteddy.org/xwinman/

I've no intention of letting that go.

But, it seems there's a few people who are disputing the legality of these pages. and/or, wishing to clone the content for themselves and "modernise the CSS".

This seems odd to me. and should not happen.

To this end, I've added the mirrored files of xwinman.org here:

https://codeberg.org/thomasadam/xwinman

... and want anyone to know that these are the official files from the original mirror.

#vt320 #tty #cables

Hey all,

I'm wondering if there's anyone out there who can point me in the eight direction.

I have a VT320 terminal I want to use, but am lacking the MMJ cable -- this is quite common.

I'm not in a position to create one myself, and even then, likely won't be able to connect to a computer without a USB to serial converter anyway.

I'm curious if there's anyone in the UK/Europe who makes these cables, in which case I'm happy to pay for that -- I just don't want to try making this myself, as I don't have the time.

Any help much appreciated.

#fvwm #cow #wayland

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:

https://codeberg.org/thomasadam/cow

#cow #wayland #fvwm

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:

https://codeberg.org/thomasadam/cow

#fvwm #cow #wayland

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.

4. Install a signal handler (USR1/HUP) -- this would make restarting the window manager trivial, and keeps river running - which is already tracking the windows available to it.

#river #wayland

Some tips I've learned from writing #cow...

1. Nested River (on #wayland/#x11) is your friend. This makes it very easy to run a nested WM instance on whatever one is using to test features. The inner-WM will need separate bindings from the "host" because that takes priority.

2. Remotely with wayvnc. Because #river is built on wlroots, #wayvnc is a great alternative if you want to do remote testing/development.

3. As with point 2., you can set the environment variable WL_HEADLESS_OUTPUTS=n, where "n" represents number of screens. This can be used with some VNC clients to allow "multi-monitor" support. This can be made even better with #wayvnc version 0.10 as this can render multiple outputs appropriately.

I'm sure there's more, but this is a practical start to some of the things I've been using with #cow.

#cow #fvwm #wayland

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.

https://codeberg.org/thomasadam/cow

#cow #fvwm #wayland

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:

https://codeberg.org/thomasadam/cow