Sway 1.0 • Hacker News Board

Re: Sway 1.0

#251

Post by hipjiveguy » Fri, Mar 15, 2019, 11:06 PM UTC

the_gipsy wrote: post #243

leadingthenet wrote: post #184

Earlier quoted context omitted.

> macOS has tried and failed I, along with many millions of people, are using spaces and fullscreen apps daily with no issue. I have used i3 and sway before, and I much prefer the macOS UX. To say that it has failed is sheer arrogance. On what do you base such a ridiculous claim?

I've never seen anybody use fullscreen-apps/spaces/maximized-windows smoothly, ever. It's especially bad on multi-monitor. - New windows appear on unfocused monitor at random. - Can make shortcuts to spaces, but not the fullscreen-apps (which look like spaces to all other effects). There are apps to make shortcuts to apps, but this is useless if you have e.g. two terminals in fullscreen mode, it just targets one wind…

totally agree on maximized windows and spaces - I run 3 monitors, and use neither

Re: Sway 1.0

#252

Post by 89nn » Mon, Mar 18, 2019, 12:25 PM UTC

raehik wrote: post #86

Awesome! Fantastic news. If there's any chance sircmpwn is lurking here, quick question: has there been any further development on IME support? I use Mozc+IBus. Last time I tried on sway it almost worked, but the prediction box didn't show. That was the only gripe I had with sway. It solved all my tiny issues with i3 and made config much nicer too. Certainly making the switch if IME is better (or if I can easily help…

FYI I've been using ibus+anthy on sway for a while now, however recently switched to ibus+mozc because the prediction box in anthy started acting up/disappearing. Mozc seems to be working great so far (and actually what I wanted to use in the first place, but I believe I might have had the same issue you experienced)

Re: Sway 1.0

#253

Post by deevus » Mon, Mar 18, 2019, 10:36 PM UTC

lapinot wrote: post #23

mario0b1 wrote: post #15

Earlier quoted context omitted.

Does "everything else" work with wayland? Like is the compositor the only thing I need to get most applications running without too much hassle? Disclaimer: I haven't read up anything on wayland and don't know too much about how X or it's mechanics work

sway comes with xwayland configured, which makes it zero-effort to run X-only software (eg software that doesn't use a wayland-enabled gui library like gtk3, qt5, sdl2...). The only pain will be if you have a hidpi screen, since xwayland will scale a non-hipdi rendered X window instead of passing down the scaling factor to X (which apparently is tricky). I'm in that case and what caused me the most hassle was firefox…

Still don't see Sway 1.0 in Fedora repo though :(

Re: Sway 1.0

#254

Post by jhasse » Mon, Mar 25, 2019, 3:48 PM UTC

ZeikJT wrote: post #250

mikenew wrote: post #147

Earlier quoted context omitted.

There's a short explanation and a very nice 2 minute video demonstrating how it works. I think expecting people to be able to view a webm video is pretty reasonable.

Reasonable? Maybe. But the web is not restricting anyone to one file format. Why not just add some fallbacks to be even more compatible?

Because that would be more work. Why not switch to a browser which supports webm/VP9?

Re: Sway 1.0

#255

Post by jhasse » Mon, Mar 25, 2019, 3:52 PM UTC

nambit wrote: post #192

ddevault wrote: post #58

Earlier quoted context omitted.

The nvidia drivers still do not support the standard Linux features necessary for sway to work. I recommend using nouveau instead, and buying a graphics card from a vendor which supports open source next time. That's how it is, and I'd like to ask everyone to refrain from drawing this particular flamewar out any further.

You're conflating two things. Is it that they don't support the features or is it that they're proprietary?

The proprietary driver doesn't support the features (i.e. GBM).

Re: Sway 1.0

#256

Post by jhasse » Mon, Mar 25, 2019, 3:54 PM UTC

mises wrote: post #41

jadbox wrote: post #35

Is there an update to the nvidia (proprietary drivers) situation with sway/wayland?

The author still flat-out refuses to support them. This might change if Nvidia open-sources their drivers, which I suspect is part of what he's trying to do.

No, the problem is that the driver uses it's own API called EGLStreams instead of GBM, which everyone else (including Sway) uses. Open-source is not a requirement for Sway support, just GBM support.