Glimpse VS barrier

glimpse fork have already died :`( https://github.com/glimpse-editor/Glimpse/wiki/Development-Priorities

Remember the fork of GIMP because people were offended by the name?

https://github.com/glimpse-editor/Glimpse

https://glimpse-editor.org/posts/a-project-on-hiatus/

> What if the name of the software was CripplePhoto

Argumentum ad absurdum.

> I mean, no professional uses Gimp for photo editing

Perhaps because the lack of CMYK, the limited architecture for plugin, or the outdated UI have more to do than the name?

If the name was the real bottleneck for adoption, you can be sure that you'd see someone creating a fork with different branding and being widely successful. Oh, wait. It has been tried already! [0]

[0] https://github.com/glimpse-editor/Glimpse

There is a bunch of folks who forked Gimp because they find the name offensive. Since they still have to refer to it they use euphemisms (such a "upstream") or call it "GNU Imp".

Glimps is a good one. It has pressure sensitivity support for drawing tablets. If you want something closer to Illustrator, Inkscape is your best shot.

They're named by committee. No committee would have come up with "GIMP" (also forked as "Glimpse").

I've been enjoying the Glimpse fork a lot more these days.

(cc u/krapht) check out glimpse! it’s a fork of GIMP that’s a bit more modern. also an nx version coming soon which will be geared toward beginners

For software KVM you can use https://github.com/debauchee/barrier

I use it between a Windows PC & a Macbookpro (Linux version available but I don't have Linux)

libei looks useful. But IDK why libei is necessary to run Barrier with Wayland?

For client systems, couldn't there just be a virtual /dev/inputXYZ that Barrier forwards events through

And for host systems, it looks like xev only logs input events when the window is focused.

Is xeyes still broken on Wayland, and how to fix it so that it would work with Barrier?

With Barrier, when the mouse cursor reaches a screen boundary, the keyboard and mouse input are then passed to a different X session on another box until the cursor again crosses a screen boundary rule.

Barrier is a fork of Synergy's open core: https://github.com/debauchee/barrier

libei:

I have a similar gaming/WFH setup (2 monitors at 1440p 144hz) and I’ve been using Barrier instead of a physical kvm, and it works really well. Not sure if you’re open to a software kvm but if you are, I’m happy to answer any questions about it if you have any.

Have you tried Barrier? I casually used it to swap between my main rig and my MBP. Took a minute to get it setup but once I sorted it all out it worked pretty well. It has some settings and tweaks built in to address some of the layout issues you mentioned...

Barrier appears to handle PC switching only for the keyboard and mouse.

Sorry, probably not entirely on topic and can't answer anything reliable about the multimonitor stuff, but a tip regarding the 2 mice and 2 keyboards for the 2 different computers: use this: https://github.com/debauchee/barrier It's oss multi-os software that lets you use one mouse and keyboard (server) on several PCs (clients) easily over your LAN.

Barrier is a free and open source alternative.