1. 25 Sep, 2017 1 commit
  2. 21 Sep, 2017 1 commit
    • Christian Hergert's avatar
      source tree reorganization · 9b9db776
      Christian Hergert authored
      As the project has grown, we've let things get a bit out of their
      logical place. This does a bit of cleanup and tries to bring some
      of the embedded resources closer to where they are used.
      
      But more importantly, this allows us to clean some things up to
      the point that we can move forward statically linking a bunch of
      the plugins into libide. The plan here is to speed up the initial
      loading by avoiding lots of disk I/O stats which are currently
      hurting us.
      9b9db776
  3. 15 Sep, 2017 1 commit
  4. 09 Sep, 2017 1 commit
    • Christian Hergert's avatar
      flatpak: work around devhelp · fe416d9f
      Christian Hergert authored
      We need access to the documentation that is provided in the flatpak
      runtimes as they might not be available on the host.
      
      This cheats and symlinks the gtk-doc/html files from ".Docs" runtimes into
      the the data dir used by Builder.
      
      It is very much not an ideal solution, but we need some what to show
      documentation to users in the 3.26 cycle and this is about the best we
      can do as we're already in code freeze.
      fe416d9f
  5. 26 Jun, 2017 1 commit
  6. 19 Jun, 2017 2 commits
  7. 10 Jun, 2017 1 commit
  8. 18 May, 2017 1 commit
  9. 23 Apr, 2017 2 commits
    • Matthew Leeds's avatar
      flatpak: Reload preferences addin on installation changes · 99f180e2
      Matthew Leeds authored
      Since the application addin is already monitoring the flatpak
      installations for changes, the preferences addin can just connect to a
      signal and reload whenever the app addin reloads. This means the flatpak
      SDKs list in the Preferences pane will stay up to date.
      99f180e2
    • Matthew Leeds's avatar
      flatpak: Only get the list of flatpak installations once · 35bbe5da
      Matthew Leeds authored
      Rather than looking for flatpak installations in both
      GbpFlatpakApplicationAddin and GbpFlatpakPreferencesAddin, access the
      former list from the latter to reduce duplication of effort. This also
      means the preferences pane will show runtimes from multiple system
      installations if they exist.
      35bbe5da
  10. 22 Mar, 2017 1 commit
  11. 18 Mar, 2017 3 commits
  12. 14 Mar, 2017 1 commit
  13. 11 Mar, 2017 1 commit
  14. 10 Mar, 2017 1 commit
    • Christian Hergert's avatar
      flatpak: add helper to check for system dependencies · 152a72cd
      Christian Hergert authored
      This will check for flatpak-builder on the host by using:
      
        which flatpak-builder
      
      as that is more reliable than checking the package manager. We will still
      use pkcon to install the package, but we don't need the D-Bus service to
      check for it.
      152a72cd
  15. 07 Mar, 2017 2 commits
  16. 18 Feb, 2017 1 commit
  17. 16 Feb, 2017 3 commits
  18. 18 Nov, 2016 1 commit
    • Matthew Leeds's avatar
      flatpak: Delete our remote on application startup · de3bb5b1
      Matthew Leeds authored
      Since the user cache dir is different on the host OS than from within a
      flatpak (~/.cache/gnome-builder/... vs ~/.var/app/org.gnome.Builder/...),
      the flatpak runtime ends up trying to create a remote with the same name
      as an existing one (if Builder has been run outside a flatpak) and a
      different location, which fails, eventually causing the Run button not
      to work. This commit fixes the issue by deleting the remote we create
      upon application startup.
      de3bb5b1