aboutsummaryrefslogtreecommitdiffstats
path: root/src/ephy-page-menu-action.c
Commit message (Collapse)AuthorAgeFilesLines
* Make ephy_window_get_ui_manager return a GtkUIManager, not a GObjectXan Lopez2012-01-211-1/+1
| | | | | No clue why it was doing that, but seems pointless. I wish I could make it private but it's used all over the place.
* ephy-page-menu-action: do not query the action proxies during disposeXan Lopez2012-01-181-9/+5
| | | | | That was a bad idea. Just store the proxy used for the visibility hack in the private data too.
* ephy-page-menu-action: disconnect the visible handler on disposeXan Lopez2012-01-171-0/+10
|
* ephy-page-menu-action: set the DROPDOWN type hint on the page menuCosimo Cecchi2012-01-171-0/+4
| | | | | So that the WM will use shadows on it as if it was generated from a menubar.
* ephy-page-menu-action: set the style class in the button, not the menuXan Lopez2012-01-171-12/+12
|
* ephy-page-menu-action: hang on to our menuXan Lopez2012-01-171-2/+14
|
* ephy-page-menu: set a style class when our menu is visibleXan Lopez2012-01-171-24/+53
| | | | To aid with styling.
* ephy-page-menu: fix warningXan Lopez2012-01-171-1/+1
|
* ephy-page-menu: activate on button pressXan Lopez2012-01-171-16/+41
| | | | Requested by the Design Team.
* Refactor GtkActions with attached EphyWindowsXan Lopez2012-01-171-2/+2
| | | | | Make a GtkAction subclass that only holds an EphyWindow and nothing else, and use it throughout. Allows us to kill some duplicated code.
* ephy-toolbar: use normal GtkButtons for the toolbarXan Lopez2012-01-171-3/+3
| | | | It's harder to get the theming right with GtkToolButtons :/
* Stop using GtkUIManager to create the toolbarXan Lopez2012-01-171-2/+4
| | | | Otherwise it's difficult to get the right layout for theming.
* ephy-page-menu-action: try to use the actual activate event when possibleXan Lopez2012-01-141-1/+12
| | | | Otherwise fallback to faking it as before.
* Drop menubar and create an actions menu button in the toolbarXan Lopez2012-01-141-0/+90
Similar to Chrome's wrench menu, but used only (in the future) for page-related actions. For now we have mechanically moved most stuff there, now we need to start removing them one by one when appropriate.