After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 731316 - Some fixes to the headerbar
Some fixes to the headerbar
Status: RESOLVED FIXED
Product: california
Classification: Other
Component: ux
master
Other Linux
: Normal normal
: 0.2.0
Assigned To: California Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-06-06 05:38 UTC by Yosef Or Boczko
Modified: 2014-06-13 18:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Show close button in the headerbar when not build for unity (998 bytes, patch)
2014-06-06 05:42 UTC, Yosef Or Boczko
none Details | Review
Fix the size of the window menu (1.28 KB, patch)
2014-06-06 05:42 UTC, Yosef Or Boczko
none Details | Review
Fix the order of the buttons in the end of the headerbar (1.13 KB, patch)
2014-06-06 05:43 UTC, Yosef Or Boczko
none Details | Review

Description Yosef Or Boczko 2014-06-06 05:38:19 UTC
See the patches (merge them if you want).
Comment 1 Yosef Or Boczko 2014-06-06 05:42:41 UTC
Created attachment 277992 [details] [review]
Show close button in the headerbar when not build for unity
Comment 2 Yosef Or Boczko 2014-06-06 05:42:58 UTC
Created attachment 277993 [details] [review]
Fix the size of the window menu
Comment 3 Yosef Or Boczko 2014-06-06 05:43:17 UTC
Created attachment 277994 [details] [review]
Fix the order of the buttons in the end of the headerbar

Since we target for GTK+ 3.12, we needs to pack the buttons
by the new order, which changes in GTK+ 3.12:
https://git.gnome.org/browse/gtk+/tree/README.in#n85
Comment 4 Jim Nelson 2014-06-10 21:30:58 UTC
For the first patch, I removed the close button from the header bar because the window menu now has Quit (that is, to conserve space on the headerbar).  Is the general consensus out there that we should have a close button and a Quit menu item, or one or the other?

I've applied the second patch, thanks.  Pushed to master, commit 07e1da

Regarding the third patch, California is still built against 3.10, so I can't take this as-is.  We need to only use it for 3.12 and onward.  Vala doesn't offer a way to do this, we'll need to make a flag in automake that is set when GTK+ version >= 3.12.
Comment 5 Jim Nelson 2014-06-10 21:32:24 UTC
Mistake, the commit is commit 4984f5
Comment 6 Yosef Or Boczko 2014-06-10 21:43:08 UTC
(In reply to comment #4)
> For the first patch, I removed the close button from the header bar because the
> window menu now has Quit (that is, to conserve space on the headerbar).  Is the
> general consensus out there that we should have a close button and a Quit menu
> item, or one or the other?

You needs to remove the Quit item from the gear menu because we have it in the
app menu.
Also, you always want a close button in the main window because this is part
of the GNOME 3 HIG.
Infact (from GTK+ 3.12) it not only a close button, it can to be also minimize,
maximize and appmenu buttons depend on the “gtk-decoration-layout” property
of the default GtkSettings (and can be set in dconf/gsettings somewhere):
https://developer.gnome.org/gtk3/3.12/GtkSettings.html#GtkSettings--gtk-decoration-layout

> 
> I've applied the second patch, thanks.  Pushed to master, commit 07e1da
> 
> Regarding the third patch, California is still built against 3.10, so I can't
> take this as-is.  We need to only use it for 3.12 and onward.  Vala doesn't
> offer a way to do this, we'll need to make a flag in automake that is set when
> GTK+ version >= 3.12.

Hmm, ok.
Comment 7 Jim Nelson 2014-06-13 18:59:25 UTC
I applied your first patch and removed the Quit item: commit 7874c1

The 3.12 button ordering patch is committed as well but with some automake checking for conditional compilation: commit 1e6ade