Announcement

Collapse
No announcement yet.

Two Areas KDE Can Use Help Right Now In Porting For Plasma 6.0

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

  • Two Areas KDE Can Use Help Right Now In Porting For Plasma 6.0

    Phoronix: Two Areas KDE Can Use Help Right Now In Porting For Plasma 6.0

    Longtime KDE developer David Edmundson has issued a call for help in porting work for Plasma 6.0...

    http://www.phoronix.com/scan.php?pag...0-Porting-Help

  • #2
    New and shiny stuff instead of fixing Plasma5 and Freeing Qt5..

    Comment


    • #3
      I am already afraid by all the breakage & functionality loss Plasma 6 will bring.
      I can't help but to think KDE lacks capable core developers - Plasma 5 is still full of small glitches and problems, and bug reports sometimes stay open for a long long time. On the other side the lets-rewrite-the-whole-thing-again group seems to strike again.

      Comment


      • #4
        Originally posted by 144Hz View Post
        New and shiny stuff instead of fixing Plasma5 and Freeing Qt5..
        Feel free to rewrite Qt. No one is stopping you.

        The rest of us aren't going to complain that they want to modernize and unify the way their backends work or want to provide a consistent user experience and interfaces in their control panel. Also, since a lot of people like to complain about how difficult Plasma is to configure, them working on the UX can be seen as both shiny and new as well as fixing bugs.

        Comment


        • #5
          Plasma 6 should be Wayland-only.

          Comment


          • #6
            I so hate QML... Anything done in QML is instantly recognizable in the desktop. Be it round corners instead of square, or a complete different functionality of lists. Not to mention that QML loading takes time... I mean, KMail is started and usable before the plasma desktop is done loading all its stuff. I might be considered cheating because I use a system-wide DB instance, but still.
            Plus its IMO a PITA to use and interface with C++. As much as I love Qt, I hate QML.

            Comment


            • #7
              Originally posted by StarterX4 View Post
              Plasma 6 should be Wayland-only.
              Ideally/in a perfect world, I agree.

              Comment


              • #8
                skeevy420 No need for rewrites. Just Freeing it up. V6 will likely focus on javascript for the interwebs anyway...

                Comment


                • #9
                  StarterX4 Qt doesn’t care about wayland for desktops. They care about embedded systems and that’s it. That conflict is bigger than QML vs C++.

                  Comment


                  • #10
                    Originally posted by Linuxhippy View Post
                    I am already afraid by all the breakage & functionality loss Plasma 6 will bring.
                    I can't help but to think KDE lacks capable core developers - Plasma 5 is still full of small glitches and problems, and bug reports sometimes stay open for a long long time. On the other side the lets-rewrite-the-whole-thing-again group seems to strike again.
                    In the KDE devs defense, the last time I randomly browsed their bug tracker I saw a decent amount of bugs where a person posts a bug and never followed up when devs tried to contact them with questions like "did 5.12 fix your issue?". Fedora has so many bugs like that that they're considering just dropping them.

                    A bunch of open bug reports doesn't necessarily mean a bunch of bugs when you have cases like KDE and Fedora where the bug reporter doesn't follow the process to get the bug closed.

                    Comment

                    Working...
                    X