[Nepomuk] Re: [kde-runtime] nepomuk/services/strigi: Removed some notifications: don't annoy users with nepomuk suspended/resumed messages every time they are running on battery.

[Sebastian Trüg]

I see your point and agree that the perfect solution would be to
completely hide from the user. That is what we did in the beginning and
then people complained (and filed bug reports) that they did not know
what was going on. So until we can really hide in terms of resource
usage or a better solution than the notifications come along this has to
stay an imperfect thing. Either way there is someone to complain.

Maybe if we integrated into the power profile configuration so users can
configure if indexing should be stopped during battery usage or not.
Then the whole thing would be more transparent and the notifications
could become unnecessary.

Cheers,
Sebastian

On 05/06/2011 02:15 PM, Davide Bettio wrote:
> Hi,
> 
>> I already reverted it. And I think there even is a bug for it already.
>> However, I fail to see the problem if you get one message about indexing
>> when going to battery.
> 
> You should think as an end user and not as a nepomuk developer. For an end user is important to use the indexing but they don't care about how it works, they don't even care/know about what is nepomuk and they don't need to be notified about every power saving strategy of every process in their system. I like to think that nepomuk should remain invisible to users as a KDE system core component. Please don't forget that nepomuk isn't more special than other components. Have you ever thought about what happens if every developer thinks that its own application is special so it should notify the user? So, please, don't interrupt users with expected behaviours of system components (users expects power saving strategies). Use notifications instead for unexpected events.
> 
> Bye,
> Davide Bettio.
>