Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Wayfire 0.8

wayfire.org

Post reply on HN
Print view View original

31–40 of 73 posts

Re: Wayfire 0.8

#31

Post by taeric »

ammen99 wrote: post #8
toastal wrote: post #4

Earlier quoted context omitted.

Oof. That is not an acceptable way to treat the issue. It’s one thing to say you don’t the time & cycles, but it’s another to WONTFIX it twice with a clear usability problem.

As the maintainer of Wayfire, I would like to say why I don't consider this a critical issue: the current system allows you to bind actions to a particular physical key. So, no matter what physical keyboard layout and actual layout in software, with the current system, you can bind the action to the desired physical key. Or do people actually want their keybindings to change when they change their layouts?

I definitely think of keys per my layout, not what is on the cap. I'd expect that to be the norm for touch typists.

Re: Wayfire 0.8

#32

Post by phkahler »

tmtvl wrote: post #2

I gave Wayfire a shot a bit earlier in the year, but as I am a Dvorak typist and https://github.com/WayfireWM/wayfire/issues/1601 > is marked as "wontfix", I decided to stick to Awesome for the time being. It did run like a dream, though, even on my ancient potato, so if the keybinding issue does get fixed at some point I may well switch over.

>> It did run like a dream, though, even on my ancient potato

I believe this is the compositor they're going to run on Raspberry Pi 4 and 5 with the next OS release, so it makes sense it will run on more limited hardware.

Re: Wayfire 0.8

#33

Post by OJFord »

OsrsNeedsf2P wrote: post #20

> The purpose of workspace sets is to have a dedicated set of normal workspaces for different activities the user does on their computer. For example, I have one workspace set (containing a 2x2 workspace grid) dedicated to Wayfire, where I have Wayfire’s source code, GitHub issues, wlroots, etc. There is another workspace set dedicated to a project I am working on for university, and so on. Of course, a similar effec…

> I've wanted this for 7 years

Is there a good story behind how specific that is?

Re: Wayfire 0.8

#34

Post by Congeec »

theorknfnfn wrote: post #3

Anyone using it daily? I'd love to hear about what makes the cool animations.. well, cool. My desktop is pretty boring right now.

As an average user, wayfire has been pretty reliable since 0.7.5. It is just its ecosystem needs more work.

Re: Wayfire 0.8

#35

Post by charcircuit »

>IPC socket

This IPC is a custom built IPC that has no security. This means that any program can do stuff like steal focus or drive other window manager policy if the plugin is there. There is also a plugin that exposes the ability to send key or mouse events.

Applications should just use DBus instead of creating their own custom IPC protocols just because they feel like it.

Re: Wayfire 0.8

#36

Post by nickstinemates »

charcircuit wrote: post #35

>IPC socket This IPC is a custom built IPC that has no security. This means that any program can do stuff like steal focus or drive other window manager policy if the plugin is there. There is also a plugin that exposes the ability to send key or mouse events. Applications should just use DBus instead of creating their own custom IPC protocols just because they feel like it.

Isn't dbus a pretty heavy dependency to bring in to a project?

Re: Wayfire 0.8

#37

Post by ForkMeOnTinder »

ammen99 wrote: post #16
jraph wrote: post #14

Earlier quoted context omitted.

> Or do people actually want their keybindings to change when they change their layouts? That's what actually happens everywhere. For instance undo is usually CTRL+Z. On QWERTY that will be CTRL + the key at the left side of the X, and on AZERTY that will be CTRL+the key at the left side of the E. Therefore, that's the behavior people expect and it has advantages. Having to write KEY_Z to actually have KEY_W is also…

I am mostly trying to understand what people actually use. I hate exactly this thing in most applications: ctrl-z doesn't work when I use the german layout (usually I use qwerty/us), and assumed most people would dislike it as well...

I personally like the flexibility of i3's keybinding config.[1] For each binding it lets you choose either:

- a keysym (the letter Z, wherever it happens to be in your current layout)

- or a keycode/scancode (the physical button under your pinky, no matter the current layout)

I use both methods for different bindings. For example I've bound the vim keys (hjkl) by scancode, and the layout keys ("S"tack, "F"ullscreen, "R"esize, etc) by symbol.

[1]: https://i3wm.org/docs/userguide.html#keybindings

Re: Wayfire 0.8

#38

Post by charcircuit »

nickstinemates wrote: post #36
charcircuit wrote: post #35

>IPC socket This IPC is a custom built IPC that has no security. This means that any program can do stuff like steal focus or drive other window manager policy if the plugin is there. There is also a plugin that exposes the ability to send key or mouse events. Applications should just use DBus instead of creating their own custom IPC protocols just because they feel like it.

Isn't dbus a pretty heavy dependency to bring in to a project?

If a program is targeting the Linux desktop (freedesktop) then it should be assumed that dbus exists.

Re: Wayfire 0.8

#39

Post by ammen99 »

charcircuit wrote: post #35

>IPC socket This IPC is a custom built IPC that has no security. This means that any program can do stuff like steal focus or drive other window manager policy if the plugin is there. There is also a plugin that exposes the ability to send key or mouse events. Applications should just use DBus instead of creating their own custom IPC protocols just because they feel like it.

The IPC plugin is optional (you don't have to enable it) and nothing stops you from writing a dbus plugin to accomplish the same tasks :)

Personally, I prefer IPC because it is simpler to implement, debug and use.

Re: Wayfire 0.8

#40

Post by resonious »

dizhn wrote: post #27

One of the developers just responded on the github issue referecing this thread. (Also reopened the issue and removed wontfix) "After a bit of discussion on HackerNews, I got a bit better understanding of the actual problem. People don't want to just configure the keys according to a particular layout - the actual 'issue' here is that they expect the key binding changes together with the layout. Unfortunately, the 0.…

> the actual 'issue' here is that they expect the key binding changes together with the layout.

The issue is that people expect "KEY_Q" to refer to the key that inputs a "q", no? Classic desktop-Linux-level user friendliness.

Post reply on HN