Re: Review Request 117441: Raise match ceiling in the KRunner plugin from 5 to 10
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/117441/#review55262 --- I'm a little hesitant about this because the user may never see emails as KMail only shows the first 8 results or so. The user can scroll but by default they will never see the Emails. Do you think it would make sense interleaving the email results with the file ones? - Vishesh Handa On April 9, 2014, 3:39 a.m., Eike Hein wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/117441/ > --- > > (Updated April 9, 2014, 3:39 a.m.) > > > Review request for Baloo and Vishesh Handa. > > > Repository: baloo > > > Description > --- > > Raising the ceiling would make the Baloo runner more useful in KRunner > frontends like Homerun and Homerun Kicker. > > While it might make sense for Homerun to use Baloo directly, this: > > a) Isn't currently possible in time for SC 4.13 to be released. > > b) Doesn't prevent users from using either the "KRunner" source in Homerun, > or the "Runner: Desktop Search" source. The former is the only way to get a > combined listing with other KRunner plugins, which might be desirable for > some users. > > c) Some users already have the above in their configs, and Baloo is the > natural upgrade path for them (and in fact, the just-released Homerun 1.2.3 > does this automatically). It'd nice if installing SC 4.13 doesn't degrade > their experience -- and 10 was the ceiling in the old nepomuksearch runner. > > It would be awesome if we could get this in before today's 4.13 tag. > > > Diffs > - > > src/runner/baloosearchrunner.cpp b62cb8b > > Diff: https://git.reviewboard.kde.org/r/117441/diff/ > > > Testing > --- > > > Thanks, > > Eike Hein > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Review Request 117441: Raise match ceiling in the KRunner plugin from 5 to 10
> On April 9, 2014, 8:46 a.m., Vishesh Handa wrote: > > I'm a little hesitant about this because the user may never see emails as > > KMail only shows the first 8 results or so. The user can scroll but by > > default they will never see the Emails. > > > > Do you think it would make sense interleaving the email results with the > > file ones? s/KMail/Krunner/ - Vishesh --- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/117441/#review55262 --- On April 9, 2014, 3:39 a.m., Eike Hein wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/117441/ > --- > > (Updated April 9, 2014, 3:39 a.m.) > > > Review request for Baloo and Vishesh Handa. > > > Repository: baloo > > > Description > --- > > Raising the ceiling would make the Baloo runner more useful in KRunner > frontends like Homerun and Homerun Kicker. > > While it might make sense for Homerun to use Baloo directly, this: > > a) Isn't currently possible in time for SC 4.13 to be released. > > b) Doesn't prevent users from using either the "KRunner" source in Homerun, > or the "Runner: Desktop Search" source. The former is the only way to get a > combined listing with other KRunner plugins, which might be desirable for > some users. > > c) Some users already have the above in their configs, and Baloo is the > natural upgrade path for them (and in fact, the just-released Homerun 1.2.3 > does this automatically). It'd nice if installing SC 4.13 doesn't degrade > their experience -- and 10 was the ceiling in the old nepomuksearch runner. > > It would be awesome if we could get this in before today's 4.13 tag. > > > Diffs > - > > src/runner/baloosearchrunner.cpp b62cb8b > > Diff: https://git.reviewboard.kde.org/r/117441/diff/ > > > Testing > --- > > > Thanks, > > Eike Hein > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Review Request 117441: Raise match ceiling in the KRunner plugin from 5 to 10
> On April 9, 2014, 8:46 a.m., Vishesh Handa wrote: > > I'm a little hesitant about this because the user may never see emails as > > KMail only shows the first 8 results or so. The user can scroll but by > > default they will never see the Emails. > > > > Do you think it would make sense interleaving the email results with the > > file ones? > > Vishesh Handa wrote: > s/KMail/Krunner/ How about we do it like this: 1) We fetch max 10 file matches. 2) We fetch max 10 mail matches. 3) We combine them based on how much we got, i.e.: If we have 10 for both we show 5/5; when we have 4/10 we show 4/6, when we have 8/4 we show 8/2, when we have 2/2 we show 2/2. You'd have to be the judge whether the extra search work would offset the UX benefits. Thoughts? - Eike --- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/117441/#review55262 --- On April 9, 2014, 3:39 a.m., Eike Hein wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/117441/ > --- > > (Updated April 9, 2014, 3:39 a.m.) > > > Review request for Baloo and Vishesh Handa. > > > Repository: baloo > > > Description > --- > > Raising the ceiling would make the Baloo runner more useful in KRunner > frontends like Homerun and Homerun Kicker. > > While it might make sense for Homerun to use Baloo directly, this: > > a) Isn't currently possible in time for SC 4.13 to be released. > > b) Doesn't prevent users from using either the "KRunner" source in Homerun, > or the "Runner: Desktop Search" source. The former is the only way to get a > combined listing with other KRunner plugins, which might be desirable for > some users. > > c) Some users already have the above in their configs, and Baloo is the > natural upgrade path for them (and in fact, the just-released Homerun 1.2.3 > does this automatically). It'd nice if installing SC 4.13 doesn't degrade > their experience -- and 10 was the ceiling in the old nepomuksearch runner. > > It would be awesome if we could get this in before today's 4.13 tag. > > > Diffs > - > > src/runner/baloosearchrunner.cpp b62cb8b > > Diff: https://git.reviewboard.kde.org/r/117441/diff/ > > > Testing > --- > > > Thanks, > > Eike Hein > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Review Request 117441: Raise match ceiling in the KRunner plugin from 5 to 10
> On April 9, 2014, 8:46 a.m., Vishesh Handa wrote: > > I'm a little hesitant about this because the user may never see emails as > > KMail only shows the first 8 results or so. The user can scroll but by > > default they will never see the Emails. > > > > Do you think it would make sense interleaving the email results with the > > file ones? > > Vishesh Handa wrote: > s/KMail/Krunner/ > > Eike Hein wrote: > How about we do it like this: > > 1) We fetch max 10 file matches. > 2) We fetch max 10 mail matches. > 3) We combine them based on how much we got, i.e.: If we have 10 for both > we show 5/5; when we have 4/10 we show 4/6, when we have 8/4 we show 8/2, > when we have 2/2 we show 2/2. > > You'd have to be the judge whether the extra search work would offset the > UX benefits. Thoughts? I should add: A simpler algorithm would be to search for max 5 mail items and then search for as many file items as needed to fill up 10 and list them in files;mails order , but because I don't know about the relative costs of the queries I didn't suggest that. - Eike --- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/117441/#review55262 --- On April 9, 2014, 3:39 a.m., Eike Hein wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/117441/ > --- > > (Updated April 9, 2014, 3:39 a.m.) > > > Review request for Baloo and Vishesh Handa. > > > Repository: baloo > > > Description > --- > > Raising the ceiling would make the Baloo runner more useful in KRunner > frontends like Homerun and Homerun Kicker. > > While it might make sense for Homerun to use Baloo directly, this: > > a) Isn't currently possible in time for SC 4.13 to be released. > > b) Doesn't prevent users from using either the "KRunner" source in Homerun, > or the "Runner: Desktop Search" source. The former is the only way to get a > combined listing with other KRunner plugins, which might be desirable for > some users. > > c) Some users already have the above in their configs, and Baloo is the > natural upgrade path for them (and in fact, the just-released Homerun 1.2.3 > does this automatically). It'd nice if installing SC 4.13 doesn't degrade > their experience -- and 10 was the ceiling in the old nepomuksearch runner. > > It would be awesome if we could get this in before today's 4.13 tag. > > > Diffs > - > > src/runner/baloosearchrunner.cpp b62cb8b > > Diff: https://git.reviewboard.kde.org/r/117441/diff/ > > > Testing > --- > > > Thanks, > > Eike Hein > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Review Request 117441: Raise match ceiling in the KRunner plugin from 5 to 10
> On April 9, 2014, 8:46 a.m., Vishesh Handa wrote: > > I'm a little hesitant about this because the user may never see emails as > > KMail only shows the first 8 results or so. The user can scroll but by > > default they will never see the Emails. > > > > Do you think it would make sense interleaving the email results with the > > file ones? > > Vishesh Handa wrote: > s/KMail/Krunner/ > > Eike Hein wrote: > How about we do it like this: > > 1) We fetch max 10 file matches. > 2) We fetch max 10 mail matches. > 3) We combine them based on how much we got, i.e.: If we have 10 for both > we show 5/5; when we have 4/10 we show 4/6, when we have 8/4 we show 8/2, > when we have 2/2 we show 2/2. > > You'd have to be the judge whether the extra search work would offset the > UX benefits. Thoughts? > > Eike Hein wrote: > I should add: A simpler algorithm would be to search for max 5 mail items > and then search for as many file items as needed to fill up 10 and list them > in files;mails order , but because I don't know about the relative costs of > the queries I didn't suggest that. >From a performance point of view searching emails is faster than files. I'm okay with both approaches, whichever is easier. - Vishesh --- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/117441/#review55262 --- On April 9, 2014, 3:39 a.m., Eike Hein wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/117441/ > --- > > (Updated April 9, 2014, 3:39 a.m.) > > > Review request for Baloo and Vishesh Handa. > > > Repository: baloo > > > Description > --- > > Raising the ceiling would make the Baloo runner more useful in KRunner > frontends like Homerun and Homerun Kicker. > > While it might make sense for Homerun to use Baloo directly, this: > > a) Isn't currently possible in time for SC 4.13 to be released. > > b) Doesn't prevent users from using either the "KRunner" source in Homerun, > or the "Runner: Desktop Search" source. The former is the only way to get a > combined listing with other KRunner plugins, which might be desirable for > some users. > > c) Some users already have the above in their configs, and Baloo is the > natural upgrade path for them (and in fact, the just-released Homerun 1.2.3 > does this automatically). It'd nice if installing SC 4.13 doesn't degrade > their experience -- and 10 was the ceiling in the old nepomuksearch runner. > > It would be awesome if we could get this in before today's 4.13 tag. > > > Diffs > - > > src/runner/baloosearchrunner.cpp b62cb8b > > Diff: https://git.reviewboard.kde.org/r/117441/diff/ > > > Testing > --- > > > Thanks, > > Eike Hein > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Review Request 117441: Raise match ceiling in the KRunner plugin from 5 to 10
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/117441/ --- (Updated April 9, 2014, 1:42 p.m.) Review request for Baloo and Vishesh Handa. Changes --- This: - Looks for 10 mail matches first. - Then looks for as many file matches as needed to fill up 10 depending on the number of mail matches, but bounding the latter to 5. - Then adds the matches in file, mail order, up to 10. Bottom line: If there's plenty of matches of either type it'll show 5/5 as before, otherwise it'll try to fill up the 10 in some other way if it can, but never add more than 10. Repository: baloo Description --- Raising the ceiling would make the Baloo runner more useful in KRunner frontends like Homerun and Homerun Kicker. While it might make sense for Homerun to use Baloo directly, this: a) Isn't currently possible in time for SC 4.13 to be released. b) Doesn't prevent users from using either the "KRunner" source in Homerun, or the "Runner: Desktop Search" source. The former is the only way to get a combined listing with other KRunner plugins, which might be desirable for some users. c) Some users already have the above in their configs, and Baloo is the natural upgrade path for them (and in fact, the just-released Homerun 1.2.3 does this automatically). It'd nice if installing SC 4.13 doesn't degrade their experience -- and 10 was the ceiling in the old nepomuksearch runner. It would be awesome if we could get this in before today's 4.13 tag. Diffs (updated) - src/runner/baloosearchrunner.cpp b62cb8b Diff: https://git.reviewboard.kde.org/r/117441/diff/ Testing --- Thanks, Eike Hein >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Review Request 117441: Raise match ceiling in the KRunner plugin from 5 to 10
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/117441/#review55289 --- Ship it! - Vishesh Handa On April 9, 2014, 1:42 p.m., Eike Hein wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/117441/ > --- > > (Updated April 9, 2014, 1:42 p.m.) > > > Review request for Baloo and Vishesh Handa. > > > Repository: baloo > > > Description > --- > > Raising the ceiling would make the Baloo runner more useful in KRunner > frontends like Homerun and Homerun Kicker. > > While it might make sense for Homerun to use Baloo directly, this: > > a) Isn't currently possible in time for SC 4.13 to be released. > > b) Doesn't prevent users from using either the "KRunner" source in Homerun, > or the "Runner: Desktop Search" source. The former is the only way to get a > combined listing with other KRunner plugins, which might be desirable for > some users. > > c) Some users already have the above in their configs, and Baloo is the > natural upgrade path for them (and in fact, the just-released Homerun 1.2.3 > does this automatically). It'd nice if installing SC 4.13 doesn't degrade > their experience -- and 10 was the ceiling in the old nepomuksearch runner. > > It would be awesome if we could get this in before today's 4.13 tag. > > > Diffs > - > > src/runner/baloosearchrunner.cpp b62cb8b > > Diff: https://git.reviewboard.kde.org/r/117441/diff/ > > > Testing > --- > > > Thanks, > > Eike Hein > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Review Request 117441: Raise match ceiling in the KRunner plugin from 5 to 10
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/117441/#review55288 --- Ship it! - Vishesh Handa On April 9, 2014, 1:42 p.m., Eike Hein wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/117441/ > --- > > (Updated April 9, 2014, 1:42 p.m.) > > > Review request for Baloo and Vishesh Handa. > > > Repository: baloo > > > Description > --- > > Raising the ceiling would make the Baloo runner more useful in KRunner > frontends like Homerun and Homerun Kicker. > > While it might make sense for Homerun to use Baloo directly, this: > > a) Isn't currently possible in time for SC 4.13 to be released. > > b) Doesn't prevent users from using either the "KRunner" source in Homerun, > or the "Runner: Desktop Search" source. The former is the only way to get a > combined listing with other KRunner plugins, which might be desirable for > some users. > > c) Some users already have the above in their configs, and Baloo is the > natural upgrade path for them (and in fact, the just-released Homerun 1.2.3 > does this automatically). It'd nice if installing SC 4.13 doesn't degrade > their experience -- and 10 was the ceiling in the old nepomuksearch runner. > > It would be awesome if we could get this in before today's 4.13 tag. > > > Diffs > - > > src/runner/baloosearchrunner.cpp b62cb8b > > Diff: https://git.reviewboard.kde.org/r/117441/diff/ > > > Testing > --- > > > Thanks, > > Eike Hein > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Review Request 117441: Raise match ceiling in the KRunner plugin from 5 to 10
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/117441/ --- (Updated April 9, 2014, 1:55 p.m.) Status -- This change has been marked as submitted. Review request for Baloo and Vishesh Handa. Repository: baloo Description --- Raising the ceiling would make the Baloo runner more useful in KRunner frontends like Homerun and Homerun Kicker. While it might make sense for Homerun to use Baloo directly, this: a) Isn't currently possible in time for SC 4.13 to be released. b) Doesn't prevent users from using either the "KRunner" source in Homerun, or the "Runner: Desktop Search" source. The former is the only way to get a combined listing with other KRunner plugins, which might be desirable for some users. c) Some users already have the above in their configs, and Baloo is the natural upgrade path for them (and in fact, the just-released Homerun 1.2.3 does this automatically). It'd nice if installing SC 4.13 doesn't degrade their experience -- and 10 was the ceiling in the old nepomuksearch runner. It would be awesome if we could get this in before today's 4.13 tag. Diffs - src/runner/baloosearchrunner.cpp b62cb8b Diff: https://git.reviewboard.kde.org/r/117441/diff/ Testing --- Thanks, Eike Hein >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Review Request 117441: Raise match ceiling in the KRunner plugin from 5 to 10
> On April 9, 2014, 1:46 p.m., Vishesh Handa wrote: > > Pushed as 8df8be6ac. - Eike --- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/117441/#review55289 --- On April 9, 2014, 1:55 p.m., Eike Hein wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/117441/ > --- > > (Updated April 9, 2014, 1:55 p.m.) > > > Review request for Baloo and Vishesh Handa. > > > Repository: baloo > > > Description > --- > > Raising the ceiling would make the Baloo runner more useful in KRunner > frontends like Homerun and Homerun Kicker. > > While it might make sense for Homerun to use Baloo directly, this: > > a) Isn't currently possible in time for SC 4.13 to be released. > > b) Doesn't prevent users from using either the "KRunner" source in Homerun, > or the "Runner: Desktop Search" source. The former is the only way to get a > combined listing with other KRunner plugins, which might be desirable for > some users. > > c) Some users already have the above in their configs, and Baloo is the > natural upgrade path for them (and in fact, the just-released Homerun 1.2.3 > does this automatically). It'd nice if installing SC 4.13 doesn't degrade > their experience -- and 10 was the ceiling in the old nepomuksearch runner. > > It would be awesome if we could get this in before today's 4.13 tag. > > > Diffs > - > > src/runner/baloosearchrunner.cpp b62cb8b > > Diff: https://git.reviewboard.kde.org/r/117441/diff/ > > > Testing > --- > > > Thanks, > > Eike Hein > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Disabling baloo-integration possible?
Hi Vishesh, On 08 Apr 2014, at 10:36 , Vishesh Handa wrote: >> will it be possible to run KDE without baloo enabled? > Yes. You can go to System Settings -> Desktop Search -> Exclude Folders, and > add your $HOME directory over there. > > Otherwise you can also edit the baloofilerc file and add the following - > > [Basic Settings] > Indexing-Enabled=false actually I was more thinking along the lines of: 1) not install baloo at all 2) configure KDE and all relevant apps in such a way that they don’t expect any services from baloo Is that doable? Greets, Marko >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Disabling baloo-integration possible?
El Dimecres, 9 d'abril de 2014, a les 21:29:43, mk-li...@email.de va escriure: > Hi Vishesh, > > On 08 Apr 2014, at 10:36 , Vishesh Handa wrote: > >> will it be possible to run KDE without baloo enabled? > > > > Yes. You can go to System Settings -> Desktop Search -> Exclude Folders, > > and add your $HOME directory over there. > > > > Otherwise you can also edit the baloofilerc file and add the following - > > > > [Basic Settings] > > Indexing-Enabled=false > > actually I was more thinking along the lines of: > > 1) not install baloo at all > > 2) configure KDE and all relevant apps in such a way that they don’t expect > any services from baloo > > Is that doable? How is this a development question? Remember this is kde-devel, not a support forum. If you want to check if that is possible. Try it out yourself. Cheers, Albert > > Greets, > Marko > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe > >> << >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Disabling baloo-integration possible?
Hi Albert, On 09 Apr 2014, at 22:01 , Albert Astals Cid wrote: > How is this a development question? Remember this is kde-devel, not a support > forum. it is not? > If you want to check if that is possible. Try it out yourself. I am not a KDE developer, just a port maintainer, and I thought I AM on the correct list to ask such questions. If this is not the case I apologise herewith and try to find a KDE user list which already covers baloo. (But honestly, because baloo is a new tool, I thought this IS the only place where I could ask such a basic question...) Greets, Marko >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Disabling baloo-integration possible?
Hi, 2014-04-09 21:29 GMT+02:00: > Hi Vishesh, > > On 08 Apr 2014, at 10:36 , Vishesh Handa wrote: >>> will it be possible to run KDE without baloo enabled? >> Yes. You can go to System Settings -> Desktop Search -> Exclude Folders, and >> add your $HOME directory over there. >> >> Otherwise you can also edit the baloofilerc file and add the following - >> >> [Basic Settings] >> Indexing-Enabled=false > > actually I was more thinking along the lines of: > > 1) not install baloo at all > > 2) configure KDE and all relevant apps in such a way that they don't > expect any services from baloo > > Is that doable? yes, but you might not be able to build and/or use all KDE applications correctly. kdelibs itself does not depend on Baloo at all. While building another module that makes use of Baloo, CMake will try to find the Baloo header files. If they are not found, one of the following things will happen: (a) The module is built and can be used correctly (but obviously, without any of the features provided by Baloo). This is the case, e.g., for kde-baseapps/Dolphin. (b) The module fails to build (c) The module can be built, but fails to work at runtime. I'm not quite sure, but everything related to KDE PIM might be in the (b) or (c) category. Best regards, Frank >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Disabling baloo-integration possible?
El Dimecres, 9 d'abril de 2014, a les 22:11:49, mk-li...@email.de va escriure: > Hi Albert, > > On 09 Apr 2014, at 22:01 , Albert Astals Cid wrote: > > How is this a development question? Remember this is kde-devel, not a > > support forum. > > it is not? No, it is not, if we had to do user support in this list it would get crowded to a point of being unusable, support goes in bugs.kde.org for bugs, and other channels like forums, the k...@kde.org mailing list, some software specific lists, and a long list of places. > > If you want to check if that is possible. Try it out yourself. > > I am not a KDE developer, just a port maintainer, and I thought I AM on the > correct list to ask such questions. So you are a packager, ok, the it's not user support and I guess it is kind on topic. If you had given all the information on the beginning it would have been better :) Now onto your questions (note i have nothing to do with baloo) You are asking if you can compile stuff without baloo. You don't need to be a "KDE developer" to try that. Have you tried? 1) not install baloo at all Of course, you're free to not install baloo 2) configure KDE and all relevant apps in such a way that they don’t expect any services from baloo What is "KDE"? If an application doesn't need baloo, it will obviosuly work. If an application needs baloo it may either have feature degradation or may simply not compile. For those that do not compile and the program still makes sense without baloo I'm sure the authors will accept patches. Simply replace baloo with libjpeg and the answers will be the same. Cheers, Albert > > If this is not the case I apologise herewith and try to find a KDE user list > which already covers baloo. (But honestly, because baloo is a new tool, I > thought this IS the only place where I could ask such a basic question...) > > Greets, > Marko > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe > >> << >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Disabling baloo-integration possible?
Hi Frank, thanks again for your constructive feedback! :) On 09 Apr 2014, at 22:24 , Frank Reininghaus wrote: > yes, but you might not be able to build and/or use all KDE > applications correctly. kdelibs itself does not depend on Baloo at > all. okay, good to know that kdelibs itself doesn’t need baloo. > I'm not quite sure, but everything related to KDE PIM might be in the > (b) or (c) category. Well, I had hoped that also some other apps would not require baloo during build or runtime. So, I think it will be rather impossible to skip installing baloo after all and I should rather follow Vishesh’s advice and configuring baloo using its configuration file. Greets, Marko >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Disabling baloo-integration possible?
Hi, 2014-04-09 23:37 GMT+02:00: > Hi Frank, > > thanks again for your constructive feedback! :) > > On 09 Apr 2014, at 22:24 , Frank Reininghaus wrote: >> yes, but you might not be able to build and/or use all KDE >> applications correctly. kdelibs itself does not depend on Baloo at >> all. > okay, good to know that kdelibs itself doesn't need baloo. > >> I'm not quite sure, but everything related to KDE PIM might be in the >> (b) or (c) category. > Well, I had hoped that also some other apps would not require baloo during > build or runtime. I think that there are many KDE apps which do not require Baloo at all. I'm not sure if there is a full list somewhere, but you can always build KDE modules and watch for any Baloo-related output from CMake. If there is none, then everything will most likely work fine without Baloo. Cheers, Frank >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Disabling baloo-integration possible?
Hi Albert, On 09 Apr 2014, at 22:28 , Albert Astals Cid wrote: > No, it is not, if we had to do user support in this list it would get crowded I got it. > So you are a packager, ok, the it's not user support and I guess it is kind > on > topic. If you had given all the information on the beginning it would have > been better :) It’s okay. I got PM from Mario clarifying things. I am maintaining KMyMoney on MacPorts and because of it I of course also try to keep KDE afloat on OSX/MacPorts. I am NOT the main KDE maintainer there, but I know that many OSX users do not need another indexing service due to the existence of Spotlight (which is Apple’s baloo). I personally mostly don’t need any indexer, except that I am forced by my email program Mail.app to enable Spotlight for detailed searching features in emails. > You are asking if you can compile stuff without baloo. You don't need to be a > "KDE developer" to try that. Have you tried? No, because I am not yet able to build anything else than the 4.12.4 (which my machine could successfully finish only just now) I cannot test the 4.13. > 1) not install baloo at all > Of course, you're free to not install baloo OK, but with the problems Frank already described... > 2) configure KDE and all relevant apps in such a way that they don’t expect > any services from baloo > What is "KDE”? :) You are right, I meant kdelibs there. But thanks to Frank I already understood that kdelibs itself doesn’t need baloo after all. > Simply replace baloo with libjpeg and the answers will be the same. So, ok, as I wrote in my reply to Frank: I should preferably simply use Vishesh’s suggestion and modify baloo’s configuration file. Greets, Marko >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Disabling baloo-integration possible?
Hi again, On 09 Apr 2014, at 23:53 , Frank Reininghaus wrote: > I think that there are many KDE apps which do not require Baloo at all. I could imagine that too. > I'm not sure if there is a full list somewhere, but you can > always build KDE modules and watch for any Baloo-related output from > CMake. If there is none, then everything will most likely work fine > without Baloo. OK, perhaps we could think about introducing baloo as an opt-in port variant which would only be installed if the user specifically asks for it. But that - of course - could cause a lot of stress during port maintenance. I guess it is better to install baloo and simply disable it. This case should be handled safely by all baloo-dependent KDE applications. Greets, Marko >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Disabling baloo-integration possible?
El Dijous, 10 d'abril de 2014, a les 00:12:55, mk-li...@email.de va escriure: > Hi again, > > On 09 Apr 2014, at 23:53 , Frank Reininghaus wrote: > > I think that there are many KDE apps which do not require Baloo at all. > > I could imagine that too. > > > I'm not sure if there is a full list somewhere, but you can > > always build KDE modules and watch for any Baloo-related output from > > CMake. If there is none, then everything will most likely work fine > > without Baloo. > > OK, perhaps we could think about introducing baloo as an opt-in port variant > which would only be installed if the user specifically asks for it. But > that - of course - could cause a lot of stress during port maintenance. > > I guess it is better to install baloo and simply disable it. This case > should be handled safely by all baloo-dependent KDE applications. Again not Baloo guy here, but as far as I know you can't disable "Baloo", what Vishesh told you is how to disable it's file indexer (baloofile), but if you use KMail it(akonadi_baloo_indexer) will still index your emails into the Baloo database, and may be other baloo_stuff (not aware of others existing) running. Vishesh/Dan/someone feel free to correct me. Cheers, Albert > > Greets, > Marko > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe > >> << >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Disabling baloo-integration possible?
On 10 Apr 2014, at 00:18 , Albert Astals Cid wrote: > Again not Baloo guy here, but as far as I know you can't disable "Baloo", > what > Vishesh told you is how to disable it's file indexer (baloofile), but if you > use KMail it(akonadi_baloo_indexer) will still index your emails into the > Baloo database, and may be other baloo_stuff (not aware of others existing) > running. Oh… No, one would perhaps not use KMail on OSX, because its Mail.app is sufficient for most stuff, although it also has some shortcomings. So, I wonder what baloo would be doing on OSX to get its hands into the user’s emails… I hope Vishesh can clarify this! Sure one doesn’t want to see any collisions between OSX’ Spotlight indexer on one side and baloo on the other. As I pointed out: I would like to tell baloo - if I am after all forced to install it anyways - that it should sleep and do NOTHING. Greets, Marko >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Disabling baloo-integration possible?
Am Donnerstag, 10. April 2014 schrieb : > So, I wonder what baloo would be doing on OSX to get its hands into the user’s emails… > I hope Vishesh can clarify this! > > Sure one doesn’t want to see any collisions between OSX’ Spotlight indexer on one side and baloo on the other. i assume, ideally the api would just abstract spotlight on osx? would require someone developing an osx backend. cheers, thomas >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Disabling baloo-integration possible?
On Thu, 10 Apr 2014 12:18:56 AM Albert Astals Cid wrote: > but if you > use KMail it(akonadi_baloo_indexer) will still index your emails into the > Baloo database, and may be other baloo_stuff (not aware of others existing) > running. Contacts and calendar as well. If the akonadi_baloo resource is removed, will Akonadi auto re-add it? -- Lindsay signature.asc Description: This is a digitally signed message part. >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Disabling baloo-integration possible?
On 10 Apr 2014, at 00:40 , Thomas Lübking wrote: > i assume, ideally the api would just abstract spotlight on osx? > would require someone developing an osx backend. Yes, Thomas, that would be ideal. Since I am not an OSX developer I have no clue as to how open Apple’s API’s regarding Spotlight are… But that could definitely be a good way to integrate more seamlessly on the OSX platform. Greets, Marko >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Disabling baloo-integration possible?
On Apr 9, 2014, at 3:47 PM, mk-li...@email.de wrote: > On 10 Apr 2014, at 00:40 , Thomas Lübking wrote: >> i assume, ideally the api would just abstract spotlight on osx? >> would require someone developing an osx backend. > > Yes, Thomas, that would be ideal. > > Since I am not an OSX developer I have no clue as to how open Apple’s API’s > regarding Spotlight are… I quick scan of these pages suggests the API is open enough: https://developer.apple.com/library/mac/documentation/carbon/conceptual/spotlightquery/Concepts/Introduction.html https://developer.apple.com/library/mac/documentation/Carbon/Reference/MDQueryRef/Reference/reference.html http://www.macdevcenter.com/pub/a/mac/2005/07/12/spotlight.html?page=last http://www.macdevcenter.com/pub/a/mac/2005/07/12/spotlight.html Regards, Bradley Giesbrecht (pixilla) signature.asc Description: Message signed with OpenPGP using GPGMail >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Disabling baloo-integration possible?
On 10/04/2014, at 8:40 AM, Thomas Lübking wrote: > Am Donnerstag, 10. April 2014 schrieb : > > > So, I wonder what baloo would be doing on OSX to get its hands into the > > user’s emails… > > I hope Vishesh can clarify this! > > > > Sure one doesn’t want to see any collisions between OSX’ Spotlight indexer > > on one side and baloo on the other. > > i assume, ideally the api would just abstract spotlight on osx? > would require someone developing an osx backend. Oops, I see Bradley has just beaten me to the punch. Never mind, here is some additional info about Spotlight. "Introduction to Spotlight" is here: https://developer.apple.com/library/mac/documentation/Carbon/Conceptual/MetadataIntro/MetadataIntro.html A rough (and quick) idea of the architecture is here in "How Does Spotlight Work?": https://developer.apple.com/library/mac/documentation/Carbon/Conceptual/MetadataIntro/Concepts/HowDoesItWork.html#//apple_ref/doc/uid/TP40001847-CJBEJBHH The "Finder" referred to as a client in that article is Apple OS X's file manager. Its "Info" function uses Spotlight to get the available metadata on any file and display a panel. A quick search on "Spotlight" in the Documentation section of the Xcode app (Apple's IDE application, similar in scope to KDevelop) showed plenty of references to library classes one could use to deliver metadata, etc. Also programming examples. These classes and examples are in Objective C and are non-free, I assume, but they are at least public. I do not know if Qt4-Mac has an interface to them, but probably not. However Qt4-Mac does include lots of examples of how to bridge between C++ and Objective C libraries, because it uses native OS X classes for QMainWindow, widgets, etc. ATM interfacing to Spotlight would have to be low on the list of KDE priorities. Marko and I are currently engaged in setting up a list of known problems that affect KDE on the OS X platform, either generally or for specific apps. Then we propose to get MacPorts and KDE experts together to find the root causes and fix them, either in the KDE codebase or the MacPorts base, wherever the trail leads. Some of the problems are showstoppers. I do not use Spotlight much, but it is sometimes handy for digging up old emails. The thing I really like about Spotlight is its unobtrusive and user-friendly interface. It is just a simple, small magnifying glass icon at the top right of the screen (equivalent to bottom right in Plasma, I seem to remember). If you click on it, a text-entry widget appears and you enter your term. Then a drop-down panel shows the results. If you hover over a result, you see a quick display of the message or whatever. If you click it, the result opens in the application where it belongs (e.g. Apple Mail). Very quick. Cheers, Ian W. > > cheers, > thomas >>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe << >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
