I have not a clue. Maybe he didn't think of it, thought it wasn't needed, was in a rush, or was expecting help from another developer to add it later. Either way, Baloo was not complete and should not have been released the way it was. You don't release an alpha as a final version. And if you do, you don't not put in GUI switch to shut the thing off, and not warn the user that their hard drive is about to be burned up. I would guess that the idea the KDE team had was indexing for everyone, everywhere, and always, reigning down from the KDE heavens. When it was actually put into practice, and people (like me) started having major problems with baloo_file_cleaner getting stuck in a state that consumed CPU cycles yet was doing nothing, and disk I/O was going crazy, it didn't look so pretty. Hopefully it gets better in time. I never really noticed a Windows installation cause the kind of I/O and CPU utilization that Baloo uses, and would guess either the Baloo code needs more optimization and/or Windows 7 indexing happens at a slower pace. On Tue, May 6, 2014 at 12:27 PM, John Andersen <jsamyth@gmail.com> wrote:

On 5/6/2014 11:33 AM, Sam M wrote:

...

For those that wanted it, a disable checkbox will be available for Baloo under KDE 4.13.1.

https://projects.kde.org/projects/kde/kdelibs/baloo/repository/revisions/77a...

This, I think, is a step in the right direction, as the whole opt-out approach was disliked by many (including me).

About 34 lines of code. Why the hell did Vishesh Handa dig in his heals and not put this in right from the get go?

-- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org