Re: baloo monitor visibility
Am Samstag, 18. Juli 2015, 13:04:38 schrieb Vishesh Handa: I was hoping to get it into KInfoCenter, and maybe have a way to launch that from the KCM. +1 for Kinfocenter ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: baloo monitor visibility
On Sat, Jul 18, 2015, 4:05 AM Vishesh Handa wrote: I was hoping to get it into KInfoCenter, and maybe have a way to launch that from the KCM Works for me. - Andrew ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: baloo monitor visibility
It seems this desktop search monitor fits squarely into the powerful when needed bucket. In that sense I don't think it is necessary to expose it through any of the primary search interfaces (Alt-F2 or application menu). That doesn't mean it should be completely hidden away since when it is actually needed, it shouldn't be difficult to find. I'm thinking perhaps we fold it into Search kcm as an indication of the status of the search system. It could be helpful there if the user wants to make a change to the search settings based on that information. I think we should still do the plasmoid for the instances where the user might like to do some long term monitoring. I'd suggest providing a way to access the Search kcm from the plasmoid in case that user would like to make some changes based on what they're seeing. That's my 2c. Hope it helps, Andrew On Fri, Jul 17, 2015 at 1:33 AM Harald Sitter sit...@kde.org wrote: On Wed, Jul 15, 2015 at 10:39 AM, Pinak Ahuja pinak.ah...@gmail.com wrote: In fact I'm working on a plasmoid with the monitor's functionality, which will show up in the tray. Maybe we can hide the monitor from applications and add a button to plasmoid? i.e. if we do end up shipping the plasmoid. I think that would give it much more context, so that'd be cool. Mark and Martin do have a point in that it potentially being valuable without context though (such as when run from krunner by someone who knows what it does). I am not sure having it completely standalone is necessarily the way to go about this though. In particular I'd much rather have it be a KCM in ksysguard as it is a diagnostic tool for all intents and purposes (or kinfocenter... or fold it into the regular baloo KCM?). The one and only problem I have with the tool being in the menu is that it lacks any sort of context and at least to me file search is part of the workspace at large, so it being listed as a utility feels a lot like if for example the plasma wallpaper configuration was listed there. Perhaps you could ask the visual design group for some input on this? HS ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
baloo monitor visibility
ahoy ahoy I have just come across the new baloo monitor and it appears to me that it is supposed to be installed by default which makes it appear by default on all plasma systems. Is that in fact the intended behavior here (i.e. desktop file, visible by default, installed by default)? If so, it most decidedly needs a GenericName set to say 'File Indexing Monitor' as right now it says 'Baloo Monitor' which means literally nothing seeing as Baloo has been kept a pretty hidden name up until now. https://bugs.kde.org/show_bug.cgi?id=350233 Also just my two cents: IMO it would make contextually more sense to have the utility NoDisplay=true (have it not show up in the actual menu) but a button to launch it in the File Search KCM. At least I would not look for this in the application menu ;) HS ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: baloo monitor visibility
Am Mittwoch, 15. Juli 2015, 09:56:07 schrieb Harald Sitter: ahoy ahoy Hi Harald, I have just come across the new baloo monitor and it appears to me that it is supposed to be installed by default which makes it appear by default on all plasma systems. Is that in fact the intended behavior here (i.e. desktop file, visible by default, installed by default)? If so, it most decidedly needs a GenericName set to say 'File Indexing Monitor' as right now it says 'Baloo Monitor' which means literally nothing seeing as Baloo has been kept a pretty hidden name up until now. https://bugs.kde.org/show_bug.cgi?id=350233 Also just my two cents: IMO it would make contextually more sense to have the utility NoDisplay=true (have it not show up in the actual menu) but a button to launch it in the File Search KCM. At least I would not look for this in the application menu ;) I usually just use Alt-F2 or search in Kickoff menu to find things. So I bet I would find it there :) I agree about the generic name. Ciao, -- Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: baloo monitor visibility
snip Also just my two cents: IMO it would make contextually more sense to have the utility NoDisplay=true (have it not show up in the actual menu) but a button to launch it in the File Search KCM. At least I would not look for this in the application menu ;) Why would you want to hide a application? The only reason i can think of is when it's a very specific other desktop application that has no use in the plasma desktop. And that's why there is the OnlyShowIn property [1]. Btw, that spec linked at [1] misses Plasma [2], which how we call the KDE Desktop these days. If the application is a standalone application (which this seems to be) then i would not hide it from the application menu. [1] http://standards.freedesktop.org/menu-spec/latest/ar01s03.html [2] http://standards.freedesktop.org/menu-spec/latest/apb.html ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
