[Development] New API design for file system operations

Jason H jhihn at gmx.com
Mon Feb 11 19:16:16 CET 2019

> The question for me is: why would an application (that is not a file explorer) want to do any of this? I honestly don’t see the use case.

When I filed the bug against KIO not having a "trash" feature it was because I was working in digikam (photo library) in KDE - this is MANY years ago (2004,  https://bugs.kde.org/show_bug.cgi?id=88615 ). Anyway, I deleted the library in the application, and ALL my photos went *poof*. I looked in the trash... Nothing. I expected my user-generated data to to be recoverable in the trash. 

So the use case, is when the user has generated data that the application does not own, where it should not assume ownership of said data and the user has requested it be removed. 
The user has requested the data be removed but not destroyed, so in a way that the data can be potentially recovered. 

More information about the Development mailing list