wdisplays
Electron
Our great sponsors
wdisplays | Electron | |
---|---|---|
12 | 236 | |
172 | 111,957 | |
- | 1.2% | |
5.0 | 9.8 | |
6 months ago | 4 days ago | |
C | C++ | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wdisplays
-
What do you guys use to manage monitors?
For an arandr replacement, https://github.com/swaywm/sway/wiki/i3-Migration-Guide recommends wdisplays.
- How to connect a Sway session to a projector?
-
How to use projector on sway?
But, Sway also supports a Wayland protocol which allows other applications to configure the displays instead. You can read it here if you want the gritty details. My preferred application to configure Sway's outputs is wdisplays.
-
Tiling WM where adding/removing external monitors is easy.
Sway with wdisplays?
-
Are there Wayland equivalents of xrandr and xinput?
You could have a look at wdisplays. Uses wlroots.
-
Three monitor configuration
I run 3 monitors in a similar config manually configured with negative x values for the left most monitor, it worked ok, but now I use https://github.com/artizirk/wdisplays for an easy life
-
(WIP) Working on a GUI for configuring displays
wdisplays comes to mind.
-
Tell HN: Gnome on Wayland Is Amazing
sway laptop user here (for almost 2 years I think?).
I spent a little while on this, but I migrated from i3, so I just ported every little section of my config bit by bit.
In terms of battery bar and other "bar" type things, I use waybar[0] which basically does all the things you'd expect by default (just install and it "works").
For multi-monitor, config, I initially setup with wdisplays[1] (think arandr for wayland) and then manually copied the positions into my sway config. Monitor positioning was the only thing I needed to setup (and telling it that one monitor was HDPI) and then all of the scaling and everything worked perfectly. This was my biggest selling point for wayland, I now get nice crisp fonts and application scaling works nicely (which was not the case with X).
volume control from the keyboard took no time, just a couple of extra lines.
There was some stuff to do with the clipboard (wl-clipboard[2]) and screenshots (grim[3] + slurp[4]) that required some setup, but again, just a few lines, and didn't take much mental load.
Oh and I needed to change my notifications daemon(dunst[5]), and chose to change my program launcher to one with a nicer interface and cleaner fonts (wofi[6]).
I think that's all the tweaking that I did. Oh, and I needed to do something with pipewire to sort out screensharing at the start, don't remember that too well though...
[0] https://github.com/Alexays/Waybar
[1] https://github.com/artizirk/wdisplays
[2] https://github.com/bugaevc/wl-clipboard
[3] https://github.com/emersion/grim
[4] https://github.com/emersion/slurp
[5] https://github.com/dunst-project/dunst
[6] https://hg.sr.ht/~scoopta/wofi
- Arch users belike
-
Setting resolution on Wayland
Try wdisplays.
Electron
-
Release Radar • February 2024 Edition
The team at Electron have been faithfully shipping new releases almost every single month. I think they had Christmas off 🤔. This popular framework has developers writing cross-platform desktop applications using JavaScript, HTML and CSS. The latest update depreciates some process events, and added new modules, APIs, methods, and more. Read into all the changes in the Electron release notes. This month, Electron also introduced a new formal RFC process.
-
The IDEs we had 30 years ago and we lost
VS Code has been crashing at launch in Wayland since more than eight months ago:
https://github.com/electron/electron/issues/37531
-
Design Systems with Web Components
So we talked a lot about the Atomic Design Principle, but you could just use that in any system and start creating. You could have Angular components, React Components, and Vue Components. But if you notice these don't easily work Everwhere. So the solution is to use Web Components because the modern browser can already understand these, and any Front-End framework can then utilize these components. You can use Electron for desktop (Slack, VSCode), PWA for both Android and iOS, and across all browsers Can I Use.
- Settings · Rulesets · electron/electron
-
How I got Wayland, Vulkan, and hardware acceleration working with Figma on Fedora 39.
I'm noticing a significant boost in performance, crisper text, and better power savings. The only shortcoming is that the window which Figma will run on will lose its shadow. This is due to a technical limitation with frameless windows on Linux.
-
Building Apps with Tauri and Elixir
For the longest time, building desktop apps was a daunting task to web developers. That is, until technologies like Electron made creating these apps more approachable to a wider audience. Today, we’ve got a wide array of native applications built with solutions like Electron, Tauri, Capacitor, and many more. While these are great solutions, sometimes configuration can be tricky and the applications we create can become somewhat bloated in terms of memory usage.
-
MS Teams & Electron libwebp 0-Day Vulnerability
Electron patch for version 27: https://github.com/electron/electron/pull/39823
-
CVE-2023-4863: Heap buffer overflow in WebP (Chrome)
It does, see [0]. Fun fact: Signal desktop, which uses Electron under the hood, is running without sandbox on Linux [1][2].
[0] https://github.com/electron/electron/pull/39824
[1] https://github.com/signalapp/Signal-Desktop/issues/5195
[2] https://github.com/signalapp/Signal-Desktop/pull/4381
-
Capturing at Speed of Thought
Turns out, there is an issue with the electron window not returning focus correctly on mac - https://github.com/electron/electron/issues/5495. The trick to solving is to treat quick capture as a screensaver. When closing, you hide it by setting the opacity to 0 and sending hide: command to the first responder.
-
$Home, Not So Sweet $Home
Open since 2016! https://github.com/electron/electron/issues/8124
What are some alternatives?
wdisplays - GUI display configurator for wlroots compositors
tauri - Build smaller, faster, and more secure desktop applications with a web frontend.
sway - i3-compatible Wayland compositor
dotenv - Loads environment variables from .env for nodejs projects.
linux-tkg - linux-tkg custom kernels
Eel - A little Python library for making simple Electron-like HTML/JS GUI apps
grim - Grab images from a Wayland compositor
puppeteer - Node.js API for Chrome
kanshi - Dynamic display configuration (mirror)
react-native - A framework for building native applications using React
wl-mirror - a simple Wayland output mirror client
cheerio - The fast, flexible, and elegant library for parsing and manipulating HTML and XML.