Announcement

Collapse
No announcement yet.

KDE Continuing To See More Wayland Improvements, Fixes To Dolphin

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Nth_man
    replied
    Originally posted by R41N3R View Post
    I wonder if anybody is still developing Kmail, at least on my systems it refuses to work with IMAP and Wayland is completely broken.
    Today, at last, Google has solved one important thing:
    “Google has approved KMail access to Gmail via Google Sign-in today”:
    https://bugs.kde.org/show_bug.cgi?id=404990

    The last PIM report:
    https://www.dvratil.cz/2020/05/march...il-in-kde-pim/

    Leave a comment:


  • BangoMopar
    replied
    Originally posted by V1tol View Post
    And that's a big win for users. At least someon is working on KWin issues instead of doing redesigns and other very important stuff. I don't care whether my System Settings is a list or icon grid, but I do care when KWin crashes after I exit a Steam game (this does not happen on any other environment on the same system).
    I have around 100+ games on Steam and play often. This has never, to my memory anyway, ever happened to me.

    Leave a comment:


  • bug77
    replied
    Originally posted by sandy8925 View Post

    Except that X11 doesn't work well for many modern use cases (and even use cases that have been around for decades). The X11 developers are the ones highlighting these problems and working on Wayland.

    The compositor/window manager needs more control to work correctly, and allowing any random app to access anything and do anything is BAD.
    Well, obviously Wayland has some more sorting out to do, otherwise it would have displaced X by now. I was just saying, some people are more forgiving than others about the limitations they will live with.

    Leave a comment:


  • Nth_man
    replied
    Originally posted by ngraham View Post

    I think that all of this happening is unlikely, but hey, stranger things have happened.
    In the business world they have similar tools:

    Your boss has asked you to develop a new service that will boost customer retention, and you've come up with several ideas that you think might work.

    The problem is, you're not sure which ones will have the biggest impact. And you don't have the time and resources to implement each idea fully. So, which idea should you move forward with?

    https://www.mindtools.com/pages/arti...xperiments.htm



    Leave a comment:


  • Nocifer
    replied
    Originally posted by ngraham View Post
    Some very, very interesting stuff that I can't requote here because the quote would be too long
    This... changes things. Alright, I stand corrected then. It seems that because I lacked the proper context (and because, just like his blog post announcing the fork, Roman's choice of wording for his tasks on Phabricator and his attitude in general all serve to make him seem like he's the no.1 guy as regards to KWin's Wayland development nowadays) what I perceived as Roman taking the initiative and you guys spurring him on, was really Roman stirring things up and you guys diplomatically trying to defuse the situation.

    Regarding KWinFT itself, I should hope that despite the interpersonal friction you mentioned, and from a purely technical point of view, the end result will be merely an evolution of the current KWin with some extra but useful bells and whistles on top and so (if it's really any good) it will eventually be able to replace its parent or, more realistically, get merged back into it without any serious (technical or non-technical) issues.

    Well. Here's to hoping that between this situation and The Qt Company's shenanigans, KDE comes out stronger and better in the end - and with rock solid Wayland support as well :-)

    Leave a comment:


  • sandy8925
    replied
    Originally posted by bug77 View Post

    I doubt anyone is a Wayland fan (as in, having Wayland posters hanging over their beds). It's just people that like the new and jump on that when given a chance and people who (for various reasons) value things that work more.
    The "readiness" thing is a (very successful) red herring.
    Except that X11 doesn't work well for many modern use cases (and even use cases that have been around for decades). The X11 developers are the ones highlighting these problems and working on Wayland.

    The compositor/window manager needs more control to work correctly, and allowing any random app to access anything and do anything is BAD.

    Leave a comment:


  • Volta
    replied
    Originally posted by frank007 View Post

    It's exactly the opposite. You are another wayland's fan (or other?).
    No, but you have no clue or worse. X is not developed anymore and many of it's developers moved to Wayland. Prove me wrong or shut up X fanboy. X is far from ready and bug free, but they decided to leave this crap.
    Last edited by Volta; 20 April 2020, 04:08 AM.

    Leave a comment:


  • Guest's Avatar
    Guest replied
    Originally posted by Volta View Post

    X is dead and Wayland is natural choice. Nobody smart will stick to X (those who're leeching on Linux' graphic stack will catch up later, maybe, but I hope they won't).
    It's exactly the opposite. You are another wayland's fan (or other?).

    Leave a comment:


  • ngraham
    replied
    Originally posted by bug77 View Post
    ngraham It would be nice if you could give us a little more information about the apparently conflicting views about Kwin. If you can, of course, as you may not be aware of enough details.
    I think I just did, no?

    Originally posted by bug77 View Post
    I have a very vague feeling that Roman wanted to turn Kwin into a Wayland compositor that can also support X11, while the rest of the team wants to keep Kwin an X11 compositor that can also support Wayland.
    I don't have enough technical understanding of the issues at play to comment. However as Martin wrote in his blog post, if he was writing a Wayland compositor from scratch, he would not start with KWin but rather build a whole new one from the ground up. So that would seem to throw water on the idea of KWinFT being a Wayland compositor first and blowing up X11 compatibility when necessary.

    Leave a comment:


  • Awesomeness
    replied
    Originally posted by ngraham View Post
    I'm hopeful that we can re-integrate Roman into upstream KWin development and incorporate some of his improvements.
    If TQtC really reversed their course WRT Qt Open Source releases, Plasma 6 would be one to 1.5 years off, so not insanely long. If KWinFT turns out to be technologically superior, just take that for KWin 6.0.

    Leave a comment:

Working...
X