Description: Beagle is a lucene-based desktop search tool written in Mono. kio-beagle is a kio-slave to perform beagle query. Beagle kio-slave allows users to query beagle in konqueror, open_file dialog box or Alt-F2-command-line.
This is a KDE4 port of the earlier kio-beagle-0.3.1 and requires beagle-0.3.x. Several new features were added including * save queries as .desktop files * easy access to help file * provide easy way to start or stop beagle or run beagle-settings
Requirements: * kde-4.0.2 * beagle-0.3.0
Visit http://beagle-project.org for information on beagle.Last changelog:
0.4.0 * Update for 0.4.0 release. * Add support for CPack based dist tarballs. * Cleanups, fixes (handle archive results). * Feature: Option to save queries as desktop files. * Feature: Show help files in beagle * Feature: Show beagle related tools (starting, stopping beagled and beagle-settings) in beagle
0.3.90 * port to KDE4 by Stephan Binner
0.3.1 * Added some more i18n() strings to allow translations. * Dont hardcode beagle-include path.
0.3 * Updated kio-slave to work with current beagle API. * Added proper handling of emails, applications, feeds,
You are doing a beagle frontend for kde
beagle is itself a frontend of lucene for gnome...
kiolucene (http://kioclucene.objectis.net/) does it directly
Hi Gentoo'ers,
an ebuild for kio-beagle, that works with beagle 0.2.x can be found here:
https://lepetitfou.dyndns.org/wiki/view/Werkstatt/GentooPortageOverlay
Note: To compile kio-beagle agains the api changes in newer beagle versions I borrowed two patches from the suse guys, so credit goes to them.
Hi all,
kio-beagle wont build with the latest beagle (0.2.1). There was some change in beagle api which caused this. While this isnt difficult to fix, I am working with the developer of kwest to write a better kio-slave for clucene and beagle. The project is named "kwest" and its near the point of a release. kwest will provide bettern beagle experience, with increased robustness, ability to save searches and more query options.
I will link kwest release announcement here too ... so keep watching this space.
Till then, thanks for your patience.
- dBera
Does kio-beagle 0.2 support beagle 0.2.1?
I want to compile kio-beagle-0.2 on Gentoo (and make the ebuild open, of course) but get the following error message:
beaglesearch.cpp: In static member function `static QString* BeagleSearch::get_uri_from_feed_hit(BeagleHit*)':
beaglesearch.cpp:114: error: `beagle_hit_get_property' undeclared (first use this function)
beaglesearch.cpp:114: error: (Each undeclared identifier is reported only once for each function it appears in.)
beaglesearch.cpp: In static member function `static void BeagleSearch::hits_added_cb(BeagleQuery*, BeagleHitsAddedResponse*)':
beaglesearch.cpp:131: error: `beagle_hit_get_property' undeclared (first use this function)
Could that be caused by the newer beagle version (0.2.1 instead of 0.1.5)?
What do you think, how much work would it be for you to check and fix this?
I downloaded this source. I have beagle 0.1.5 from cvs running on SuSE 10.0. When I try to run ./configure I get:
"configure: error: cannot find sources (acinclude.m4) in . or .."
Any idea what the problem might be. I think running a beagle query through a Konqueror query would be so cool because when I find the file/e-mail/web link that I want Konqueror will open the default application for that type. I won't have to let beagle open what it wants to use.
That looks like some kind of autotools error (autoconf/autpmake stuff...). Did you run ./autogen.sh first (you said you are using beagle CVS checkout, right ?)
Also, if you are looking for KDE client for beagle (to use KDE applications to open search results), search for 'yabi' in kde-apps.org.
I get exactly the same thing, and I'm using the 0.2 tarball (as the other poster also said he was). The tarball is broken (or at least the INSTALL instructions are wrong, but the former is much more likely).
Ahh... its a cvs checkout. Try running
$ make -f Makefile.cvs
first, followed by ./configure etc.
Writing from memory, so I am not sure.
Good luck,
- d.
Hi There! This is my first post!! I'm trying to compile kio_slave, but at 'configure' time, i receive this message: "configure: error: cannot find sources (acinclude.m4) in . or ..". What hell is going on here? Thank u very much!
Andrea
Are you aware of kio-clucene?
http://kde-apps.org/content/show.php?content=23874
It's based on Lucene (C++ port of Lucene) the same backend like Begle. So it provides the same searching capablities. But it has
much less dependencies (no Mono, no inotify ...), the code is more mature and additional features, like saving results to virtual folders.
I can see only ONE advantage of your project, Beagle is capable of automatic indexing (based on inotify).
Would you mind to work cooperatively on one project to make it more polished, to add NEW features - like automatic indexing or share document plugins with KAT - instead of creating new competing project?
There is too much duplicated projects with the same aim (or nearly the same):
Gwenview vs. ShowImg
Kaffeine vs. KMPlayer vs. KPlayer
etc. etc.
Thats a good idea. Please make beagle:/ and kio_clucene:/ one project and work togheter. You can still support both search engines, beagle and lucene, but one kio-slave would be makes easier for users.
Nevertheless from the point of usability, the kioslave should have a name which is easier to remark, e.g. find:/ or search:/
Beagle and Kio_lucene really USE THE SAME SEARCH ENGINE!!! Lucene!
Lucene it a mature Java project with a port to C++ and Mono, they are like one-egg twins. Kio-lucene uses C++ port and Beagle uses Mono port. Guess which is quicker ;-)
See:
http://lucene.apache.org/java/docs/index.htmlhttp://www.dotlucene.net/http://clucene.sourceforge.net/
Beangle is a just layer above Lucene. Layer which offers:
1) integration with Gnome
2) gnome app for viewing results
3) automatic background indexing
(using kernel inotify)
4) smart recognition of already indexed
files using extended file attributes
1 and 2) we don't need in KDE. Kio_Lucene already offers this for KDE/Konqueror
3 and 4) cool features, but should be implemented in KDE/KIO using KDED service (configurable from KCenter) + KDirWatch (can use inotify, if present in kernel) for checking file changes.
This feature should stay optional, as many user, including me, prefers manual index creation (or a Cron job).
As I can see, Beagle gets much more better propagation. Kio_lucene is nearly unknown.
BTW: Beagle also depends on filesystem extended attributes. Not all filesystems support them (FAT,NTFS,..) and even ext3 in many distributions is set not to use them by default.
This is from FAQ:
Do I really need extended attributes? Isn't there a fallback in place?
Yes, this is possible using an sqlite-based fallback. However, using this as the primary store is very slow, so using extended attributes is recommended.
As I can see, Beagle gets much more better propagation. Kio_lucene is nearly unknown.
One possible reason kio-lucene is less used - the name: difficult to remember and means nothing, spell and so on. I always have to guess/remember what the hell the name was. (lucien, lucern, lucent, lumen, lament etc.)
I use kio-locate cause it's, well "locate:/"
so far beagle is easier to recall than "cement", err.. "clement", err.. you know what I mean.
Yes, you are right. "protocol" name should change to something like "search:/" as someone suggested. Try to bother author.
But indeed it's not matter of the name. Beagle as a project is much better known.
It's really slightly more older a propably mature but kio_clucene is utterly uknown.
Valid points. A few minor comments: 1 & 2) They are not really true. Beagle is more of a search backend - they do have a gecko-based frontend (but you can also search using your webbrowser like Google Desktop Search). As for opening files, they *generally* use gnome-mimetype information to open hits but they can use KDE apps too (the version shipped in NLD does that). 3 & 4) With inotify and extended attributes things become real fast. And with current kernel having inotify and all modern filesystems having extended_attr, they are a very minimal minimum_requirement. If you dont like beagle indexing automatically, there are well defined tools and settings available to do manual indexing, indexing only certain directories etc. A side point: beagle has its strength in indexing desktop content. It can index files no doubt, allow searching among indexes over network, allows searching of contacts/appointments, weblogs, allows searching of browser history pages. I am not saying they are unique to beagle or cant be implemented in others, its just that beagle is in a quite mature stage now. Last of all, I am in contact with kio_clucene project guys and am trying to use his well written interface to search beagle index. If there is any second release of beagle-kio, it will in form of kio_clucene. Wish me luck.
A great feature would be to make virtual folders for saved searches (like KMail does).
So if someone is searching for all documents containing a specific word, he just klicks on this folder and gets the results. With each search you will get a new virtual folder. If you like it, keep the folder. If you do not need the search results just delete it.
So if I type beagle:/ I can see all my saved searches as folder. If I will start a new search I just type beagle:/whatever
Users can then even have everything sortet in virtual folders, like:
documents (doc,sxw,otd, etc)
pictures
sounds
textfiles
pdfs
html-files
This would be a great step towards non hierarchical filesystem (without needing such a filesystem :-) )
I knew about Kat, but it's just 'another app'. Integration within Konqueror is better (I think). Also Beagle works much faster for me, than Kat.
kio_clucene I didn't know. This seems to be great, too (see my comment).
beagle is getting included in most distributions. But it is in a rapid development stage - so there might be some problems in installing and running it. The best place to check (apart from their web-site and mailing list) is the irc channel #dashboard on irc.gimp.net
Ratings & Comments
25 Comments
You are doing a beagle frontend for kde beagle is itself a frontend of lucene for gnome... kiolucene (http://kioclucene.objectis.net/) does it directly
Hi Gentoo'ers, an ebuild for kio-beagle, that works with beagle 0.2.x can be found here: https://lepetitfou.dyndns.org/wiki/view/Werkstatt/GentooPortageOverlay Note: To compile kio-beagle agains the api changes in newer beagle versions I borrowed two patches from the suse guys, so credit goes to them.
Hi all, kio-beagle wont build with the latest beagle (0.2.1). There was some change in beagle api which caused this. While this isnt difficult to fix, I am working with the developer of kwest to write a better kio-slave for clucene and beagle. The project is named "kwest" and its near the point of a release. kwest will provide bettern beagle experience, with increased robustness, ability to save searches and more query options. I will link kwest release announcement here too ... so keep watching this space. Till then, thanks for your patience. - dBera
Does kio-beagle 0.2 support beagle 0.2.1? I want to compile kio-beagle-0.2 on Gentoo (and make the ebuild open, of course) but get the following error message: beaglesearch.cpp: In static member function `static QString* BeagleSearch::get_uri_from_feed_hit(BeagleHit*)': beaglesearch.cpp:114: error: `beagle_hit_get_property' undeclared (first use this function) beaglesearch.cpp:114: error: (Each undeclared identifier is reported only once for each function it appears in.) beaglesearch.cpp: In static member function `static void BeagleSearch::hits_added_cb(BeagleQuery*, BeagleHitsAddedResponse*)': beaglesearch.cpp:131: error: `beagle_hit_get_property' undeclared (first use this function) Could that be caused by the newer beagle version (0.2.1 instead of 0.1.5)? What do you think, how much work would it be for you to check and fix this?
I downloaded this source. I have beagle 0.1.5 from cvs running on SuSE 10.0. When I try to run ./configure I get: "configure: error: cannot find sources (acinclude.m4) in . or .." Any idea what the problem might be. I think running a beagle query through a Konqueror query would be so cool because when I find the file/e-mail/web link that I want Konqueror will open the default application for that type. I won't have to let beagle open what it wants to use.
That looks like some kind of autotools error (autoconf/autpmake stuff...). Did you run ./autogen.sh first (you said you are using beagle CVS checkout, right ?) Also, if you are looking for KDE client for beagle (to use KDE applications to open search results), search for 'yabi' in kde-apps.org.
I get exactly the same thing, and I'm using the 0.2 tarball (as the other poster also said he was). The tarball is broken (or at least the INSTALL instructions are wrong, but the former is much more likely).
Ahh... its a cvs checkout. Try running $ make -f Makefile.cvs first, followed by ./configure etc. Writing from memory, so I am not sure. Good luck, - d.
I was just poking around to see how I might hack some konqueror/beagle magic and I ran across this. Very nice.
Hi There! This is my first post!! I'm trying to compile kio_slave, but at 'configure' time, i receive this message: "configure: error: cannot find sources (acinclude.m4) in . or ..". What hell is going on here? Thank u very much! Andrea
run this before the ./configure command: make -f Makefile.cvs after that run ./configure; make ; make install J.
Are you aware of kio-clucene? http://kde-apps.org/content/show.php?content=23874 It's based on Lucene (C++ port of Lucene) the same backend like Begle. So it provides the same searching capablities. But it has much less dependencies (no Mono, no inotify ...), the code is more mature and additional features, like saving results to virtual folders. I can see only ONE advantage of your project, Beagle is capable of automatic indexing (based on inotify). Would you mind to work cooperatively on one project to make it more polished, to add NEW features - like automatic indexing or share document plugins with KAT - instead of creating new competing project? There is too much duplicated projects with the same aim (or nearly the same): Gwenview vs. ShowImg Kaffeine vs. KMPlayer vs. KPlayer etc. etc.
Thats a good idea. Please make beagle:/ and kio_clucene:/ one project and work togheter. You can still support both search engines, beagle and lucene, but one kio-slave would be makes easier for users.
Nevertheless from the point of usability, the kioslave should have a name which is easier to remark, e.g. find:/ or search:/
Beagle and Kio_lucene really USE THE SAME SEARCH ENGINE!!! Lucene! Lucene it a mature Java project with a port to C++ and Mono, they are like one-egg twins. Kio-lucene uses C++ port and Beagle uses Mono port. Guess which is quicker ;-) See: http://lucene.apache.org/java/docs/index.html http://www.dotlucene.net/ http://clucene.sourceforge.net/ Beangle is a just layer above Lucene. Layer which offers: 1) integration with Gnome 2) gnome app for viewing results 3) automatic background indexing (using kernel inotify) 4) smart recognition of already indexed files using extended file attributes 1 and 2) we don't need in KDE. Kio_Lucene already offers this for KDE/Konqueror 3 and 4) cool features, but should be implemented in KDE/KIO using KDED service (configurable from KCenter) + KDirWatch (can use inotify, if present in kernel) for checking file changes. This feature should stay optional, as many user, including me, prefers manual index creation (or a Cron job). As I can see, Beagle gets much more better propagation. Kio_lucene is nearly unknown. BTW: Beagle also depends on filesystem extended attributes. Not all filesystems support them (FAT,NTFS,..) and even ext3 in many distributions is set not to use them by default. This is from FAQ: Do I really need extended attributes? Isn't there a fallback in place? Yes, this is possible using an sqlite-based fallback. However, using this as the primary store is very slow, so using extended attributes is recommended.
As I can see, Beagle gets much more better propagation. Kio_lucene is nearly unknown. One possible reason kio-lucene is less used - the name: difficult to remember and means nothing, spell and so on. I always have to guess/remember what the hell the name was. (lucien, lucern, lucent, lumen, lament etc.) I use kio-locate cause it's, well "locate:/" so far beagle is easier to recall than "cement", err.. "clement", err.. you know what I mean.
Yes, you are right. "protocol" name should change to something like "search:/" as someone suggested. Try to bother author. But indeed it's not matter of the name. Beagle as a project is much better known. It's really slightly more older a propably mature but kio_clucene is utterly uknown.
Valid points. A few minor comments: 1 & 2) They are not really true. Beagle is more of a search backend - they do have a gecko-based frontend (but you can also search using your webbrowser like Google Desktop Search). As for opening files, they *generally* use gnome-mimetype information to open hits but they can use KDE apps too (the version shipped in NLD does that). 3 & 4) With inotify and extended attributes things become real fast. And with current kernel having inotify and all modern filesystems having extended_attr, they are a very minimal minimum_requirement. If you dont like beagle indexing automatically, there are well defined tools and settings available to do manual indexing, indexing only certain directories etc. A side point: beagle has its strength in indexing desktop content. It can index files no doubt, allow searching among indexes over network, allows searching of contacts/appointments, weblogs, allows searching of browser history pages. I am not saying they are unique to beagle or cant be implemented in others, its just that beagle is in a quite mature stage now. Last of all, I am in contact with kio_clucene project guys and am trying to use his well written interface to search beagle index. If there is any second release of beagle-kio, it will in form of kio_clucene. Wish me luck.
I like your app very much. Please go on!
A great feature would be to make virtual folders for saved searches (like KMail does). So if someone is searching for all documents containing a specific word, he just klicks on this folder and gets the results. With each search you will get a new virtual folder. If you like it, keep the folder. If you do not need the search results just delete it. So if I type beagle:/ I can see all my saved searches as folder. If I will start a new search I just type beagle:/whatever
Users can then even have everything sortet in virtual folders, like:
- documents (doc,sxw,otd, etc)
- pictures
- sounds
- textfiles
- pdfs
- html-files
This would be a great step towards non hierarchical filesystem (without needing such a filesystem :-) )Look at projects Kio_clucene http://kde-apps.org/content/show.php?content=23874 Kat - Desktop Search Environment http://kde-apps.org/content/show.php?content=22135 ..the functionality is already there
I knew about Kat, but it's just 'another app'. Integration within Konqueror is better (I think). Also Beagle works much faster for me, than Kat. kio_clucene I didn't know. This seems to be great, too (see my comment).
kat exist... why should use beagle
nobody is forcing you to :-). seriously, its the free software world - like it use it, dont like it find something else or write your own.
there is something wrogn with the archive. can you repackage it?
It seems to work for me. Anyway, adding an external link: http://cs-people.bu.edu/dbera/blogdata/kio_beagle-0.2.tar.gz MD5sum 66ad8ac6ee0add0a4be74279ab7d4934 kio_beagle-0.2.tar.gz
beagle is getting included in most distributions. But it is in a rapid development stage - so there might be some problems in installing and running it. The best place to check (apart from their web-site and mailing list) is the irc channel #dashboard on irc.gimp.net