---- Reported by shotwell-maint@gnome.bugs 2013-07-14 02:50:00 -0700 ----

Original Redmine bug id: 7241
Original URL: http://redmine.yorba.org/issues/7241
Searchable id: yorba-bug-7241
Original author: Alexander Wilms
Original description:

Most Gnome apps and probably also elementary apps will be moving to HeaderBars
(https://developer.gnome.org/gtk3/3.9/GtkHeaderBar.html). They save space and
are more touch-friendly than classic window decoration + menus.

Related issues:
related to shotwell - Feature #6883: Use gnome-shell's AppMenu (Open)



---- Additional Comments From shotwell-maint@gnome.bugs 2013-07-24 09:57:00 -0700 ----

### History

####

#1

Updated by Alexander Wilms 4 months ago

  * **Description** updated (diff)

####

#2

Updated by Joe Bylund 4 months ago

Alexander,

Is there an app that already has this implemented to compare?

####

#3

Updated by Alexander Wilms 4 months ago

Yes, Music (https://wiki.gnome.org/Music), Calendar (http://blog.michiwend.com
/wp-content/uploads/2013/01/Bildschirmfoto-vom-2013-01-18-005640.png,
https://git.gnome.org/browse/gnome-calendar/ ) and probably more

Also there's a great mockup using one for a photo management app:
http://bassultra.deviantart.com/art/Photo-Management-App-385256095

####

#4

Updated by Alexander Wilms 4 months ago

  * **Description** updated (diff)

####

#5

Updated by Yosef Or Boczko 4 months ago

also baobab, bijiben, gnome-clocks and gnome-weather.

####

#6

Updated by Joe Bylund 4 months ago

I'm not sure I see how that could replace the menus that shotwell currently
has.

####

#7

Updated by Alexander Wilms 4 months ago

Most actions should be shown in the context where they make sense. The
remaining menu items could be shown in a gear menu. I could ask the guy who
made the mockup to include other ways to access these features.

####

#8

Updated by Jim Nelson 4 months ago

  * **Status** changed from _Open_ to _Need Information_

I think what you're advocating is that common actions are in the header bar
(via buttons and other simple controls), that app-wide commands are in the
Application Menu, and the rest goes into a gear menu.

But if you look at all the commands in the Shotwell menu today, that's a
pretty overloaded gear menu. I'm unconvinced at this point that this design
philosophy makes sense for an application like Shotwell. Before proceeding, we
would need to see mockups of the various views Shotwell has today: library
view, single-photo / editing view, and the event directories (where you can
see events with a key photo).

####

#9

Updated by Jim Nelson 4 months ago

  * **Status** changed from _Need Information_ to _Open_

Actually, looking closer at GtkHeaderBar, I see that its only concern is
displaying a centered title and subtitle regardless of surrounding children.
The larger discussion of menus and such properly belong in #6883.

####

#10

Updated by Alexander Wilms 4 months ago

Harvey added a few more views: http://bassultra.deviantart.com/art/Photos-
view-modes-386467782

####

#11

Updated by Joe Bylund 4 months ago

Alexander,

I gather the buttons up top are for things like "people", "tags", "events".
But it looks like it wouldn't be possible to drag a photo from an event to a
tag? It would be hard to convince me to switch unless the new layout
reproduces current functionality.

-Joe

####

#12

Updated by Alexander Wilms 4 months ago

The connected buttons are for the following views: library, events, locations,
people

The 'Albums' entry in the side pane should actually read 'Tags'. The workflow
of adding tags to photos is shown in this mockup:
http://bassultra.deviantart.com/art/Photo-Management-App-385256095



--- Bug imported by chaz@yorba.org 2013-11-25 22:11 UTC  ---

This bug was previously known as _bug_ 7241 at http://redmine.yorba.org/show_bug.cgi?id=7241

Unknown Component 
   Using default product and component set in Parameters 
Unknown version " in product shotwell. 
   Setting version to "!unspecified".
Unknown milestone "unknown in product shotwell. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Resolution set on an open status.
   Dropping resolution