1. 15 Jul, 2019 1 commit
  2. 03 Jul, 2019 1 commit
  3. 02 Jul, 2019 19 commits
  4. 29 Jun, 2019 2 commits
  5. 28 Jun, 2019 7 commits
    • Florian Müllner's avatar
      window-list: Add window picker button · 92db87f7
      Florian Müllner authored
      With the latest changes, GNOME Classic has become so classic that it
      is bordering dull. Salvage at least a tiny piece of GNOME 3 in form
      of a window-pick button which toggles an exposé-like reduced overview.
      
      !73
      92db87f7
    • Florian Müllner's avatar
      classic: Disable overview · 82d20110
      Florian Müllner authored
      The overview is one of the defining features of GNOME 3, and thus
      almost by definition at odds with the classic session, which
      emulates a traditional GNOME 2 desktop.
      
      Even with the less prominent placement inside the application menu
      it never quite fit in - it doesn't help that besides the different
      UI paradigma, the overview keeps its "normal" styling which differs
      greatly with classic's normal mode.
      
      So besides removing the "Activities" button via the session mode
      definition, now that the apps-menu extension doesn't replace it anymore,
      disable the overview completely in the classic session.
      
      !69
      82d20110
    • Florian Müllner's avatar
      apps-menu: Hide overview when launching app · 545b8115
      Florian Müllner authored
      Now that we no longer hide the overview when the menu is opened,
      it is possible to activate menu entries from the overview. Start
      hiding the overview in that case, which is consistent with app
      launching elsewhere.
      
      !69
      545b8115
    • Florian Müllner's avatar
      apps-menu: Stop hiding the overview when toggled · d99d0a06
      Florian Müllner authored
      Now that the extension no longer doubles as the "Activities" button,
      that behavior is confusing.
      
      !69
      d99d0a06
    • Florian Müllner's avatar
      apps-menu: Stop taking over Activities button · 6105eecf
      Florian Müllner authored
      We don't want the "Activities" button in GNOME Classic, but the current
      way of handling it is confusing:
      
       - the button is hidden, but the corresponding hot corner
         sometimes works (when the application menu isn't open)
      
       - the button is effectively moved inside the menu, although
         it's clearly not an app or category
      
       - the apps-menu can be used independent from classic mode, in
         which case removing the "Activities" button may not be wanted
      
      Address those points by removing any handling of the activities button
      from the apps-menu extension. We will remove it again from the classic
      session via a session mode tweak.
      
      !69
      6105eecf
    • Florian Müllner's avatar
      places-menu: Don't hardcode position · d1254d9b
      Florian Müllner authored
      The extension currently assumes that we have the "Activities" button
      at the left of the top bar. This is currently true, not only in the
      regular session, but also in GNOME classic where the button is hidden
      (but still present).
      
      However this is about to change: We will stop taking over the button
      from the apps-menu extension, and instead disable "Activities" from
      the session mode definition.
      
      Prepare for this by adding the places menu before the application menu
      instead of assuming a hardcoded position.
      
      !69
      d1254d9b
    • Florian Müllner's avatar
      cleanup: Re-order imports · 2db4589d
      Florian Müllner authored
      They should be grouped between external (GI/gjs) and shell and in
      alphabetical order. Until commit bab4be1a ExtensionUtils was special
      as it was required for some imports, but that's no longer the case
      for most extensions.
      
      !76
      2db4589d
  6. 27 Jun, 2019 1 commit
    • Florian Müllner's avatar
      apps-menu: Add missing chain-up · dfeb99fc
      Florian Müllner authored
      PanelMenu.Button is a bit weird in that it also "contains" its parent
      actor. That container is supposed to be destroyed with the button, but
      as we currently don't chain up to the parent class' _onDestroy(), we
      leave behind an empty container every time the extension is disabled.
      
      Fix this by adding the missing chain-up.
      
      !75
      dfeb99fc
  7. 24 Jun, 2019 3 commits
  8. 29 May, 2019 5 commits
  9. 22 May, 2019 1 commit