search

cockpit-project / cockpit-files

A Featureful File Browser for Cockpit (Modernized and tested version of https://github.com/45Drives/cockpit-navigator)
GNU Lesser General Public License v2.1
49 stars 26 forks source link

Update to new mockup #452

Open jelly opened 5 months ago

jelly commented 5 months ago

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

image

Basically:

(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 https://github.com/cockpit-project/cockpit-files/issues/422#issuecomment-2095567330

jelly commented 5 months ago

Blocked by: https://github.com/cockpit-project/cockpit-files/pull/384

allisonkarlitskaya commented 4 months ago

fwiw, I like having separate functional groupings for:

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 commented 4 months ago
  1. Latest version of all mockups are now at https://github.com/cockpit-project/cockpit-files/discussions/471
  2. A WIP discussion about merged vs. unmerged bars, with mockups, is now at https://github.com/cockpit-project/cockpit-files/discussions/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.)