1. 12 Feb, 2014 1 commit
  2. 29 Jan, 2014 1 commit
  3. 25 Jan, 2014 1 commit
  4. 24 Jan, 2014 2 commits
  5. 18 Jan, 2014 1 commit
    • Allison Karlitskaya's avatar
      quartz: add a default application menu · fdc66af5
      Allison Karlitskaya authored
      When running on quartz, it is no longer expected for applications to
      provide their own application menu.  Instead, they should simply ensure
      that they provide "app.about", "app.preferences" and "app.quit" actions
      (which many apps are already doing).
      
      A default menu will be shown that looks like the one presented by all
      other Mac OS applications, containing menu items for the above actions,
      as well as the typical "Hide app", "Hide Others and "Show All" items and
      the "Services" submenu.
      
      If an application does explicitly set an application menu (via
      gtk_application_set_app_menu()) then it will be respected, as before.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=720552
      fdc66af5
  6. 31 May, 2013 1 commit
  7. 16 Apr, 2013 1 commit
    • Tristan Van Berkom's avatar
      Load the file chooser's widgets from the .ui file · a6f9ef0d
      Tristan Van Berkom authored
      This is Tristan's *excellent* work, minus the old code for the shortcuts bar - that is all done
      in GtkPlacesSidebar now.
      
      The UI gets loaded from a Glade resource; most of the old code to create the UI by hand is gone.
      
      There is still code for save_widgets_create(); this needs to be moved into the UI file, but it
      is not a big deal.
      
      gtk_file_chooser_default_init() calls a new post_process_ui() that takes care of all the things
      that cannot be done directly in Glade.
      a6f9ef0d
  8. 11 Apr, 2013 1 commit
  9. 08 Apr, 2013 23 commits
  10. 03 Apr, 2012 1 commit
  11. 13 Mar, 2012 1 commit
  12. 09 Feb, 2012 1 commit
    • Alexander Larsson's avatar
      Remove all default css and make Raleigh a pure fallback theme · cdc6e827
      Alexander Larsson authored
      It was problematic to maintain Raleigh going forward, as any
      changes in it affected all themes. Also, its more robust if
      each theme is a full standalone css rather than relying on
      an inherited css base.
      
      So, this changes Raleigh to a standalone theme that we can tweak
      without accidentally breaking other themes, and makes the
      default theme empty. In fact, we don't even add the default
      provider anymore as its always empty.
      cdc6e827
  13. 16 Jan, 2012 3 commits