https://bugs.kde.org/show_bug.cgi?id=286689
Bill Werrel <werr...@mail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |werr...@mail.com
--- Comment #10 from Bill Werrel <werr...@mail.com> ---
I'd just like to add that this would be a very useful feature. My main use case
is I have a directory tree I'd like to sort through and delete any large
files/folders in order to free up some space or to reduce the size prior
backing up/transferring to other media.
Currently this requires the tedious process of selecting groups of folders,
opening properties to get the total size, then subdividing the search into
smaller groups of folders, until I can drill down one level and rinse and
repeat with another group of folders.
Using du is not a great solution due to the flattening of the tree structure in
the output. It would be much easier with the hierarchical view provided by file
managers such as Dolphin where I can start by opening the largest folder, then
the largest subfolder, etc until I quickly find the space hog - usually a DVD
ISO I forgot to delete.
Obviously automatically finding the size of all folders would be a bad idea.
The way I envision this feature would work would be something like right-click
on a folder and select "show folder size". At this point Dolphin finds (and
remembers) the size of all folders in subtree under the selected folder.
Dolphin could display something in the folder size column to indicate it is
still computing the size. The user can then browse down into subfolders of this
folder and see the size of each folder. Once Dolphin has read and cached all
the sizes this should quick and much more usable than having to open properties
on each folder.
The user could do the same with any other folder in the filesystem and Dolphin
continues to cache subtree folder sizes in all the "folder size enabled"
subtrees. When exiting Dolphin the cached sizes are lost so the user will need
to enable them again next time. Dolphin could also have a global "stop reading
folder sizes" menu option to release all cached sizes.
As for performance I don't think would be too bad. I brought up properties on
one of my larger trees. It took less than 15 seconds to total up 2TB in 250,000
files and 30,000 sub-folders. This is on a 7200rpm disk.
--
You are receiving this mail because:
You are watching all bug changes.
