|Leon Plickat a0297755a0 Changed README||1 year ago|
|contrib||2 years ago|
|include||1 year ago|
|protocols||2 years ago|
|.gitignore||2 years ago|
|LICENSE||2 years ago|
|README.md||1 year ago|
|input.c||1 year ago|
|layers.c||2 years ago|
|main.c||1 year ago|
|meson.build||2 years ago|
|output.c||1 year ago|
|view.c||1 year ago|
This a fork of the wio wayland compositor. I forked it to include features which would not be accepted into the upstream codebase. Please also check out the original.
For me, usability and practicality (especially on laptops) is more important than staying close to Plan9's rio. Rio is without a doubt nice and definitely one of the very few mouse driven windowing systems that are actually efficient, but I believe it was not in active development long enough to see a lot of useful features added.
I use this project as a platform to experiment with Wayland compositors. It is not suitable for production environments, as I will push unstable, unportable, experimental code with hard-coded values. (I push more refined revisions of some patches upstream, if they fit the projects intentions.)
Furthermore, because the output drawing is not damage based, it is highly inefficient, another reason against using it seriously.
If you want to contribute, seriously think about contributing to the upstream project instead.
Since I started to write (and experiment with) my own compositor, I rarely work on this project.
These are the differences between wio and wio+.
Superwill open the menu and can be pressed instead of the mouse buttons for all menu actions
This is what I want to implement. (Anything that would be accepted into upstream will be contributed there.)
This fork obviously has the same license as upstream: 3 Clause BSD.
Please report bugs in wio+ to me, not to upstream.