1. 22 Mar, 2018 1 commit
  2. 23 Jan, 2018 2 commits
  3. 19 Jan, 2018 1 commit
    • Christian Hergert's avatar
      buildui: track changes to pipeline PTY · 1729b355
      Christian Hergert authored
      When the PTY changes, we need to connect it to the terminal. This fixes an
      issue where the pipeline is not ready on startup so that the user wont
      see the PTY at all, even when the runtime installation succeeds.
      
      #354
      1729b355
  4. 23 Nov, 2017 6 commits
  5. 11 Oct, 2017 1 commit
  6. 03 Oct, 2017 1 commit
  7. 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
  8. 05 Jun, 2017 2 commits
  9. 08 May, 2017 2 commits
  10. 23 Mar, 2017 1 commit
  11. 01 Mar, 2017 1 commit
  12. 26 Feb, 2017 1 commit
  13. 15 Feb, 2017 1 commit
  14. 14 Feb, 2017 1 commit
  15. 10 Feb, 2017 2 commits
  16. 18 Dec, 2016 2 commits
  17. 13 Dec, 2016 1 commit
  18. 12 Dec, 2016 1 commit
    • kritarth's avatar
      Disable 'scroll-on-output' in build log panel · 60b5efe4
      kritarth authored
      Currently, the build log panel is bound to scroll to end whenever new output
      is added to the buffer using gtk_text_view_scroll_to_mark. In order to disable
      this auto-scrolling I added horizontal and vertical GtkAdjustments. These
      adjustments are initialised in gbp_build_log_panel_init(). They point to
      the adjustments of GtkScrolledWindow scroller. With these adjustments I check
      if the user has scrolled back or right manually.
      
      expression1: value >= upper - page_size - offset
      This expression returns true if the user has not scrolled vertically back.
      The 'offset' is defined as VERTICAL_AUTOSCROLL_TOLERENCE - this means the
      limit upto which scroll-on-output will still work even if the user has
      manually scrolled.
      
      Similarly HORIZONTAL_AUTOSCROLL_TOLERENCE is defined.
      Detection of horizontal scrolling is done by
      expression2: value <= HORIZONTAL_AUTOSCROLL_TOLERENCE
      HORIZONTAL_AUTOSCROLL_TOLERENCE is set to 3 because the left-margin of text_view is also set at 3.
      
      if (expression1 && expression2) then
              set the vertical adjustment to upper - page_size
              apply this adjustment to the container
      
      https://bugzilla.gnome.org/show_bug.cgi?id=775642
      60b5efe4
  19. 10 May, 2016 1 commit
  20. 04 May, 2016 1 commit
  21. 23 Mar, 2016 1 commit
    • Christian Hergert's avatar
      panel: rebase IdeLayout and IdeLayoutPane on panel-gtk · e9c4d1f2
      Christian Hergert authored
      Just in time for 3.20, we are landing the panel cleanup. This primarily
      allows us to improve things for the dot releases without breaking ABI,
      and additionally will fix a bunch of resize warnings introduced by gadgets
      in GTK+.
      
      To the user, things should be pretty much the same. However, we've laid
      the groundwork to be able to incrementally add panel dragging and
      reordering in upcoming releases.
      
      Additionally, we'll be able to add a floating layer to the system in good
      time (PnlDockOverlay).
      e9c4d1f2
  22. 16 Feb, 2016 1 commit
  23. 15 Feb, 2016 1 commit
  24. 23 Dec, 2015 1 commit
    • Christian Hergert's avatar
      build-log: don't muck with insert/selection mark · 7f51c1c9
      Christian Hergert authored
      We want to just scroll to the bottom, without touching the insert/selcetion
      mark. "move-cursor" does this just fine.
      
      We still need to deal with the problem of where the user has manually
      scrolled up, and not continue to autoscroll.
      7f51c1c9
  25. 22 Dec, 2015 4 commits