Update to new mockup

[jelly]

Here's what files is supposed to (eventually) look like:

Basically:

• The stuff on the left affects the stuff on the right.
• The stuff on the top affects the stuff below it.

(This is basically how UI flow works overall, not just for Files.)

To break it down further, for Files:

1. Bookmarks affect location.
2. Editing affects location.
3. Then location.
4. Then filtering and sorting changes the look of the location.
5. Then actions for that location (which is affected by everything but before, except view filtering and sorting, actually).

So 1 - 3 are inputs to your location (with 3 being your current status) and 4 - 5 how you see and what you do when there.

The widgets in the mockup are all PF conventions, including the inline edit (a standard input, with the buttons without frames, and the check first with the x after).

Originally posted by @garrett in #422 (comment)

[jelly]

Blocked by: #384

[allisonkarlitskaya]

fwiw, I like having separate functional groupings for:

• everything to do with navigation (bookmarks, breadcrumb, edit location, etc.)
• everything to do with how the current location is shown (sort, filter, grid/list, show-hidden, etc.)

and I like that the second group is located physically closer to the area that contains the items (ie: inside of the big white box) instead of at the top beside the navigation area. I also feel like this is less likely to run out of space on mobile.

[garrett]

1. Latest version of all mockups are now at Cockpit Files mockups #471
2. A WIP discussion about merged vs. unmerged bars, with mockups, is now at WIP: Unmerged bars? #474

We should try to keep the exploratory and discussion related discussions as completely separate topics, as to not clutter the design doc. (We can make lots of posts in discussions and close or abandon ones that are no longer relevant, but threads within a discussion get gnarly pretty quickly.)