Announcement

Collapse
No announcement yet.

GNOME Shell Picks Up Performance Improvements For Extensions

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

  • GNOME Shell Picks Up Performance Improvements For Extensions

    Phoronix: GNOME Shell Picks Up Performance Improvements For Extensions

    While days too late for squeezing into GNOME 3.34.0, the GNOME Shell has landed a one year old merge request providing various fixes and performance improvements to its extension system...

    http://www.phoronix.com/scan.php?pag...xtensions-Perf

  • #2
    This is perfect on top of
    https://gitlab.gnome.org/GNOME/gnome...rge_requests/1

    GNOME 3.34 makes life so much easier for the downstreams.

    Comment


    • #3
      Last time I tried to write a GNOME Shell extension, I used the gnome-shell-extension-tool, and it generated some ugly JavaScript code, it couldn't use modern JavaScript ES6 classes.
      Last edited by uid313; 09-12-2019, 10:22 AM.

      Comment


      • #4
        uid313

        https://gitlab.gnome.org/GNOME/gnome...ged&search=Es6

        Comment


        • #5
          AFAIK, 3.35 has not been branched yet, so this is all still going into 3.34

          Comment


          • #6
            Originally posted by treba View Post
            AFAIK, 3.35 has not been branched yet, so this is all still going into 3.34
            Possibly 3.34.1

            Comment


            • #7
              3.34.1 might end up eslint clean \o/ The extensions really need to up their CI game. How can they live with poor hosting on github? No wonder some extensions break when they miss out on Gitlab CI.

              https://gitlab.gnome.org/GNOME/gnome...e_requests/716

              Comment


              • #8
                Originally posted by 144Hz View Post
                3.34.1 might end up eslint clean \o/ The extensions really need to up their CI game. How can they live with poor hosting on github? No wonder some extensions break when they miss out on Gitlab CI.

                https://gitlab.gnome.org/GNOME/gnome...e_requests/716
                While Gitlab is surely great, you can have all sorts of external CI hooked up to github as well. Talking about travis-ci etc.

                Comment


                • #9
                  treba Problem is that Github CI features remain unused. On Gitlab they share it between gjs, shell etc.

                  Comment


                  • #10
                    Originally posted by 144Hz View Post
                    3.34.1 might end up eslint clean \o/ The extensions really need to up their CI game. How can they live with poor hosting on github? No wonder some extensions break when they miss out on Gitlab CI.

                    https://gitlab.gnome.org/GNOME/gnome...e_requests/716
                    The extension system imho should just be removed or restricted to only a few areas (e.g. adding things on the top status menu).

                    Comment

                    Working...
                    X