https://bugs.kde.org/show_bug.cgi?id=333774

Nate Graham <n...@kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REPORTED                    |NEEDSINFO
         Resolution|---                         |WAITINGFORINFO
                 CC|                            |n...@kde.org

--- Comment #5 from Nate Graham <n...@kde.org> ---
(In reply to David Kremer from comment #0)
> 1) Fine tuning on files
> One should be able to exclude from indexation certain types of files. I
> think especially about for exemple, size limitation for indexing, as
> suggested by vHanda. But one could choose also to not index videos, music,
> text, pdf document, whatever type of document could come into play.
This doesn't really make sense IMO. What's the use case?


> One should also be able to exclude/include folder to be indexed with check
> boxes in a given filesystem tree (~/ but could be another place).
Already implemented. :)


> One should
> as well be able to choose the place to store metadata. And one should be
> able to do that without manually write this into a text rc configuration
> file.
What's the use case? Why?


> One should be able to evaluate the time the baloo process should do to index
> everything in a given folder, and provide a progress bar for the user.
> Something like : "the indexing process is going to take about 3 hours. Do
> you want still to launch it ? Yes/No/Exclude some more directories from the
> indexing process"
This is already (more or less) implemented in the File Indexing Monitor page of
the Info Center app.


> One should as well be able to slow down the process of reading the hard
> drive. This is not normal that the process consumes so much computer
> resources. Probably it will mean internal optimization really difficult to
> make, about which I am not aware so I cannot say much about this.
Already tracked by separate bug reports.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to