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 685050 - Make devices visually distinct
Make devices visually distinct
Status: RESOLVED OBSOLETE
Product: baobab
Classification: Core
Component: general
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: Baobab Maintainers
Baobab Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-09-28 15:01 UTC by Allan Day
Modified: 2021-05-26 09:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Add new volumes on top of the location list (1.22 KB, patch)
2012-09-30 11:59 UTC, Stefano Facchini
none Details | Review
Append new volumes before the "Home folder" location (1.75 KB, patch)
2012-10-02 15:01 UTC, Stefano Facchini
none Details | Review
Append new volumes before the "Home folder" location (1.55 KB, patch)
2012-10-02 15:12 UTC, Stefano Facchini
committed Details | Review
Show the usage level bar only for volumes (1.06 KB, patch)
2012-10-03 09:47 UTC, Stefano Facchini
committed Details | Review

Description Allan Day 2012-09-28 15:01:55 UTC
Right now, the main view contains a list which includes devices as well as folders. I think we should make devices look different from other entries - this will make it clearer what is going on. Perhaps making the background darker would be enough.

Always placing devices at the top of the list would also help.
Comment 1 Paolo Borelli 2012-09-29 10:29:11 UTC
they are always on top of the list :)


That said I agree that we should make the distinction more explicit, but I am not sure the different background would help and/or look very good.


I think the distinction should be made by providing different information on the right hand size of the line since the current level bar etc does not really make perfect sense for a folder. I tried leaving it empty but it looked bad.,,,
Comment 2 Stefano Facchini 2012-09-29 11:19:22 UTC
(In reply to comment #1)

> I think the distinction should be made by providing different information on
> the right hand size of the line since the current level bar etc does not really
> make perfect sense for a folder. I tried leaving it empty but it looked bad.,,,

but now it's not empty anymore, there is an arrow ;-)
The level bar as it is does not really make sense for folders, if possible could we try to remove it for 3.6.1?
Comment 3 Stefano Facchini 2012-09-30 11:59:38 UTC
Created attachment 225420 [details] [review]
Add new volumes on top of the location list

Otherwise new devices connected while baobab is running would be appended at the end of the list
Comment 4 Paolo Borelli 2012-09-30 17:05:18 UTC
Review of attachment 225420 [details] [review]:

I did not test it but prepending does not look correct to me: the "main computer volume" should always stay first and the newly added volumes should be appended after the other volumes.

Basically we should scan the list for the Home location and insert right before
Comment 5 Stefano Facchini 2012-09-30 21:57:16 UTC
(In reply to comment #4)
> Review of attachment 225420 [details] [review]:
> 
> I did not test it but prepending does not look correct to me: the "main
> computer volume" should always stay first and the newly added volumes should be
> appended after the other volumes.
> 
> Basically we should scan the list for the Home location and insert right before

I think, too, that the main volume should come first, but in the mockup there is a USB device before "Joe's computer"... which made me feel allowed to choose the lazy way and just prepend :)
Comment 6 Allan Day 2012-10-01 07:42:55 UTC
(In reply to comment #2)
...
> The level bar as it is does not really make sense for folders, if possible
> could we try to remove it for 3.6.1?

Removing the bars might make sense,

(In reply to comment #4)
> Review of attachment 225420 [details] [review]:
> 
> I did not test it but prepending does not look correct to me: the "main
> computer volume" should always stay first and the newly added volumes should be
> appended after the other volumes.
> 
> Basically we should scan the list for the Home location and insert right before

I don't have a strong view on where extra devices should go, provided that the items for the XDG folders are placed below the volume that contains them.
Comment 7 Stefano Facchini 2012-10-02 15:01:35 UTC
Created attachment 225592 [details] [review]
Append new volumes before the "Home folder" location
Comment 8 Stefano Facchini 2012-10-02 15:12:11 UTC
Created attachment 225594 [details] [review]
Append new volumes before the "Home folder" location
Comment 9 Paolo Borelli 2012-10-03 07:14:11 UTC
Review of attachment 225594 [details] [review]:

Looks good
Comment 10 Stefano Facchini 2012-10-03 09:47:40 UTC
Created attachment 225672 [details] [review]
Show the usage level bar only for volumes
Comment 11 Paolo Borelli 2012-10-03 09:59:29 UTC
Review of attachment 225672 [details] [review]:

I am not 100% sure about simply showing nothing for folders... As a user I still want to know if "Downloads" has enough space to put fedora.iso there. Maybe it is enough to find a way to write that folder X is on volume Y.

Anyway I think this should wait for 3.8

Can you attach a screenie?
Comment 12 Stefano Facchini 2012-10-03 17:01:47 UTC
Comment on attachment 225594 [details] [review]
Append new volumes before the "Home folder" location

Attachment 225594 [details] pushed as f3895ad - Append new volumes before the "Home folder" location
Comment 13 Stefano Facchini 2012-10-13 15:08:08 UTC
Comment on attachment 225672 [details] [review]
Show the usage level bar only for volumes

Attachment 225672 [details] pushed as 74860f7 - Show the usage level bar only for volumes
Comment 14 André Klapper 2021-05-26 09:26:31 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version of Baobab, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new enhancement request ticket at
  https://gitlab.gnome.org/GNOME/baobab/-/issues/

Thank you for your understanding and your help.