Announcement

Collapse
No announcement yet.

Why KDE's KWin Doesn't Integrate Weston/QtCompositor For Wayland Support

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

  • Why KDE's KWin Doesn't Integrate Weston/QtCompositor For Wayland Support

    Phoronix: Why KDE's KWin Doesn't Integrate Weston/QtCompositor For Wayland Support

    KDE developers have been porting their Plasma 5 + KDE Frameworks 5 stack over to Wayland, but at this point it's not nearly as mature as the GNOME Wayland support. As such, KDE developers have to fend off questions from time-to-time why they don't "just integrate QtCompositor" or the Weston library for speeding up their efforts...

    http://www.phoronix.com/scan.php?pag...positor-Weston

  • #2
    Beause it's better to reinvent the wheel.

    Comment


    • #3
      Originally posted by newwen View Post
      Beause it's better to reinvent the wheel.
      Sometimes it is. What happened to compiz. In the end it was too unstable... And KDE made the right choice of integrating compositor into kwin and not using compiz.

      Comment


      • #4
        Originally posted by newwen View Post
        Beause it's better to reinvent the wheel.
        as you read my blog post, you might have noticed that the tires don't fit.

        Comment


        • #5
          Originally posted by newwen View Post
          Beause it's better to reinvent the wheel.
          not when 1 out of 2 happened
          - everything was checked before reaching that decision
          - original project was made with custom compositors in mind, so making custom compositor for KDE actually follows the guidelines

          note that in this case both happened and one must admit due diligence. i'm no KDE user, but this decision is probably best in the long run

          Comment


          • #6
            Originally posted by mgraesslin View Post
            as you read my blog post, you might have noticed that the tires don't fit.
            Or if the wheels are square which most definitely was the case with Weston at least some time back. As a user wanting to use Plasma I approve of the idea of rather doing things properly than fast but I am a little concerned that it appears as an end-user if DM for Wayland was still a reasonably open question for KDE. GDM already defaults to Wayland at this point

            Comment


            • #7
              KDE has always been very independant, which is both a weakness and a strenght.

              Anyway on the long run they always provide a good and complete environment, if you stick to stable releases.

              Comment


              • #8
                Originally posted by mgraesslin View Post
                as you read my blog post, you might have noticed that the tires don't fit.
                Maybe the car is just too big?

                Comment


                • #9
                  Originally posted by nanonyme View Post
                  Or if the wheels are square which most definitely was the case with Weston at least some time back. As a user wanting to use Plasma I approve of the idea of rather doing things properly than fast but I am a little concerned that it appears as an end-user if DM for Wayland was still a reasonably open question for KDE. GDM already defaults to Wayland at this point
                  Well wayland port missed sddm 0.9, but maybe it's ready for next version.

                  Comment


                  • #10
                    Originally posted by Passso View Post
                    KDE has always been very independant, which is both a weakness and a strenght.

                    Anyway on the long run they always provide a good and complete environment, if you stick to stable releases.
                    independant? The frameworks they are making is usable by any DE you want. They are building sofware that can be used by other project and DE, and these project might even contribute back.

                    It's contribution between multiple projects. independant? I say a leader!

                    I just feel that the gnome community is going in their bubble, not thinking about other projects.
                    Just look at what happened at KdeConnect, they rebuilt everything (the protocol) and they used the excuse "we didn't know other projects existed" and then they continued with their things...

                    I really hope thing will change and promote contribution and communication between project, even with GNOME and KDE.
                    It would be cool if we still have diversity without doing the same work 2 time.

                    Comment

                    Working...
                    X