Bug 212829 - Hierarchal Places in Dolphin places panel
Summary: Hierarchal Places in Dolphin places panel
Status: RESOLVED INTENTIONAL
Alias: None
Product: kfile
Classification: Applications
Component: kfileplacesview (show other bugs)
Version: unspecified
Platform: unspecified Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: Lukáš Tinkl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-03 01:00 UTC by KDE Brainstorm Submissions
Modified: 2018-04-09 19:47 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Mockup (48.60 KB, image/png)
2009-11-03 01:01 UTC, KDE Brainstorm Submissions
Details

Note You need to log in before you can comment on or make changes to this bug.
Description KDE Brainstorm Submissions 2009-11-03 01:00:12 UTC
Version:            (using KDE 4.3.2)
Installed from:    I Don't Know

This is an idea for the place panel in Dolphin, which lists places you want to visit often as well as removable media:

See attachment for mockup

In this idea, there are places that are contained within other places. You can see it in the "Crypto 1" item, which has "subcrypt a" and "subcrypt b" items branching off of it. This idea is only applicable to certain sorts of places. So for instance if you attach an external hard drive containing two partitions, it will display one entry for the entire device, then below that it will show two entries, one for each partition. You can mount and unmount the two partitions independently in the normal manner, but you can also mount and unmount the entire device. This allows you to be sure your device has been fully unmounted before you disconnect it, and makes it easier to unmount all of its partitions.

This also applies to encrypted volumes, which can contain multiple sub-volumes. In the case of encrypted volumes, if there is only one sub-volume the encrypted volumes will be replaced with the sub-volume. Mounting the encrypted volumes automatically mounts the sub-volumes as well, unmounting the sub-volume unmounts the encrypted volume. There is only ever one icon. Presently you end up with two places, one essentially useless place for the encrypted volume and a second for the single sub-volume. They both have to be mounted and unmounted separately. If there are more than one sub-partition they are displayed as sub-volumes of the encrypted volume (which itself can be a sub-volume of a device). They can be mounted or unmounted individually or as a group.

Similarly, it could apply to devices like digital cameras, cell phones, and media players that have both built-in storage space and a separate memory card. There could be a single icon for the whole device, allowing you to easily unmount the entire device. Then within that there would be two (or more) additional devices, the on-board storage and the memory card. The two can be accessed and mounted or unmounted independently.

There is also applies to network folders. If you set a place that is a subfolder of a network drive, the network drive is added to your places and the subfolder is added as a subfolder of that network drive in your places.

It may also apply to nepomuk saved searches, depending on how those are implemented.



This feature request was originally submitted through KDE Brainstorm, and has been submitted to Bugzilla due to popular demand. Original idea: http://forum.kde.org/brainstorm.php?mode=idea&i=38881
Comment 1 KDE Brainstorm Submissions 2009-11-03 01:01:06 UTC
Created attachment 38043 [details]
Mockup
Comment 2 Kevin Ottens 2010-06-26 13:48:48 UTC
*** Bug 169751 has been marked as a duplicate of this bug. ***
Comment 3 Christoph Feck 2010-08-08 00:20:47 UTC
*** Bug 168110 has been marked as a duplicate of this bug. ***
Comment 4 Sergei Andreev 2012-01-05 13:57:27 UTC
*** This bug has been confirmed by popular vote. ***
Comment 5 Nate Graham 2018-04-09 19:47:05 UTC
We already have part of this (groups/categories for different types of places panel entries). Another part depicted in your mockup--collapsible sections-- is tracked with Bug 389803.

The remainder--allowing Places Panel entries to be hierarchical children of others-- would just confuse the heck out most people, though. Most users don't (and won't, and can't) understand abstract hierarchical file storage. Also, the way this code is currently implemented, it' looks tortuously difficult to me, if not nearly impossible.