- User Since
- Apr 14 2015, 9:17 PM (235 w, 6 d)
Thu, Oct 17
Just add TODO and you are free to push
Thu, Oct 3
I'm not thrilled about having default shortcuts set. We have the shortcuts space quite polluted as it is.
Sep 16 2019
Sep 7 2019
Sep 6 2019
Sep 5 2019
Add the same for directories for completeness
Aug 29 2019
Aug 28 2019
Filtering can be done as far as the KAStats is concerned. The question is how to know inside the KIO slave which application requested its services.
Aug 27 2019
Change everything to plural.
Aug 26 2019
Aug 24 2019
Aug 23 2019
You can also use set*/add* member functions for this so that David doesn't complain. As I said, pipes are mainly there for chaining - easy query creation API to simplify the alternative of set set set set set. But if you set a single field, I'd say set*/add* is a fine option.
This is something I did have initally in kastats, it was killed because while this is tempting
Aug 22 2019
Sorry I missed this one. If I don't react on a ping here, just send me a direct mail.
Aug 19 2019
Looks OK to me, I guess some of our resident KIO experts should review it. What do you think?
Aug 17 2019
Aug 16 2019
Another tiny change, and I think it is ready to land. Unless someone else sees other issues.
Aug 15 2019
Aug 13 2019
Thanks for geting involved this much!
Jul 27 2019
Jul 25 2019
If @kossebau is satisfied, go for it
Jul 24 2019
Joining with ResourceEvent is a problem. At least make it not get joined if the date filter is not present.
Jul 11 2019
Inserting/Removing/Updating a sorted list does not need to resort every time - removing is easy, adding a new item is std::lower_bound (a binary search), and updating is a combination of the two.
Jul 10 2019
You are right, they are randomized.
Jun 26 2019
I think it would be better to put it into kio-extras - activities kio is also there.
I'd add support for HighScoredFirst and RecentlyCreatedFirst. Maybe the protocol could be something like "used:/" or something.
May 1 2019
WRT implementation, I'd also add a link to KMountPoint (https://api.kde.org/frameworks/kio/html/classKMountPoint.html) which provides an interface to fstab/mtab so that Solid/FuseMounts plugin does not need to do any parsing by itself.
I guess that is the main point of this patch. I don't think that anyone is against that. :)
I'm torn between two approaches:
Thanks for working on this.
Apr 4 2019
Apr 2 2019
Mar 24 2019
Mar 23 2019
Accepted, but incomplete ;)
Mar 22 2019
Incorporated David's advice