LXQt 1.4 Debuts As Last Planned Qt5 Desktop Release

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • phoronix
    Administrator
    • Jan 2007
    • 67292

    LXQt 1.4 Debuts As Last Planned Qt5 Desktop Release

    Phoronix: LXQt 1.4 Debuts As Last Planned Qt5 Desktop Release

    LXQt 1.4 debuted today as the newest feature release for this lightweight Qt desktop environment that was formed years ago as the merging of the LXDE and Razor-qt projects...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite
  • guglovich
    Senior Member
    • Jul 2017
    • 291

    #2
    Your bets on a drop in productivity?

    Comment

    • babali
      Phoronix Member
      • Jul 2011
      • 93

      #3
      Now they can begin to work on Qt6 port.

      Comment

      • rafanelli
        Phoronix Member
        • Apr 2022
        • 60

        #4
        Originally posted by babali View Post
        Now they can begin to work on Qt6 port.
        It seems to be in full swing for over a year.


        Here a repo with info, configs and screenshots(!) on how to get LXQt to work with Wayland with various compositors. There used to be a LXQt+mutter-with-patchs. But now the LabWC seems to be favorite.

        LXQt implementation in Wayland compositors. Contribute to stefonarch/LXQt-Wayland-files development by creating an account on GitHub.


        It contains start up scripts for:
        • startlxqthyprland
        • startlxqtkwin
        • startlxqtlabwc
        • startlxqtsway
        • startlxqtwayfire​

        Comment

        • Weasel
          Senior Member
          • Feb 2017
          • 4495

          #5
          Ah the bliss of backwards-incompatible libraries. 90% of the work is spent migrating from one ABI version to the next. Over, and over, and over, and over, and over, and over again.

          Ask GIMP.

          Comment

          • Steffo
            Senior Member
            • Jan 2013
            • 604

            #6
            Originally posted by Weasel View Post
            Ah the bliss of backwards-incompatible libraries. 90% of the work is spent migrating from one ABI version to the next. Over, and over, and over, and over, and over, and over again.

            Ask GIMP.
            You don't want using old APIs forever. Technical debts lead to unmaintainability.

            Comment

            • ClosedSource
              Senior Member
              • Feb 2022
              • 279

              #7
              Originally posted by Steffo View Post

              You don't want using old APIs forever. Technical debts lead to unmaintainability.
              Absolutely. But for smaller volunteer projects without enough developers, unless the porting is straightforward, the developers might wish to spend their contribution time working on internal code, features, and bug fixes instead. GIMP and XFCE are good examples of nice projects that could use more volunteer contributors.

              Comment

              • Steffo
                Senior Member
                • Jan 2013
                • 604

                #8
                Originally posted by ClosedSource View Post

                Absolutely. But for smaller volunteer projects without enough developers, unless the porting is straightforward, the developers might wish to spend their contribution time working on internal code, features, and bug fixes instead. GIMP and XFCE are good examples of nice projects that could use more volunteer contributors.
                I have to say, that Qt applications are much more straightforward to port.
                And if you don't want to port applications, then dort port them and live with the consequences.

                Comment

                • guzz46
                  Phoronix Member
                  • Jan 2012
                  • 100

                  #9
                  My favorite desktop, its very modular and they make it very easy to use your window manager of choice, when used with kwin its like using plasma without the bugs.

                  Comment

                  • rafanelli
                    Phoronix Member
                    • Apr 2022
                    • 60

                    #10
                    Originally posted by Weasel View Post
                    Ask GIMP.
                    Wasn't it GIMP that had their toolkit "blessed" to become The (wonderful) GTK? If it was a Qt project from the start, ORRRRR if they never had their toolkit forked, they had a lot less trouble. The good thing of the forking is, they do not have to implement Wayland and other new features for "their" GTK themselves

                    Comment

                    Working...
                    X