Re: beagle xesam
Hey dBera, On 02/12/2007, D Bera [EMAIL PROTECTED] wrote: Hi Arun, So beagle-xesam-0.1 was also released yesterday. Congratulations and thanks. Would you mind giving a few details on what exactly it does now ? How can it be used ? Where does it sit between beagle and xesam (pun intended) ? Where does it go from here ? Sorry about the late response. I've been busy heading to http://Foss.in then back. Basically the adaptor as it stands allows Xesam clients to connect to it, and pass it queries. The adaptor acts as a translator between the Xesam API and Beagle's native API. It takes Xesam queries over DBus, passes them on to beagled, and the hits back in Xesam-ese. Beagle-Xesam largely conforms to the latest (RC1) Xesam spec. Currently the only Xesam clients out there are a command-line tool and a simple test GUI that Mikkel Kamstrup Erlandsen has written. These can be found with the xesam-tools package [1]. Hopefully this will change soon, since there are 3 Xesam servers that are now out there (Beagle, Strigi, and Pinot). A simple starting point could be a deskbar [3] plugin that talks Xesam. There are some issues to be resolved. I've catalogued some of these at [2]. One major thing I've not yet added there is that we don't fully support the Xesam user query language per se. It does bear strong resemblance to the standard Beagle query syntax, though, so this should be fine for now. To summarize, the basic adaptor is functional as it stands. The path ahead should become clearer as clients that use the spec arise. -- Arun [1] http://xesam.org/people/kamstrup/xesam-tools/ [2] http://svn.gnome.org/viewvc/beagle/trunk/beagle-xesam/ISSUES?view=markup [3] http://raphael.slinckx.net/deskbar/ ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: source selection patch
Awesome! Thanks D! Dave, let me know if you have any problems, I should have plenty of free time this afternoon. On Dec 11, 2007 5:06 PM, D Bera [EMAIL PROTECTED] wrote: Hey, 'twas rainin' outside so I was stuck. Seeing your IRC message to Kevin and realizing Kevin is busy with school (I just had my last teaching today! Yay!) I made a quick patch. Attaching. Dave, you only need to change UIManager.cs, at 3 places - I marked them as /* Dave:; I dont think I can make it any simpler than this. And while creating the static indexes, you need to pass --tag fubar to it. Hope it helps, - dBera -- - Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user -- Cheers, Kevin Kubasik http://kubasik.net/blog ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Implement inSet in beagle xesam adaptor
Hi
With the new libbeagle interface he is a patch that implements the
missing inSet keyword in the Xesam interface.
--
Anders Rune Jensen
http://people.iola.dk/anders/
Index: src/Parser.cs
===
--- src/Parser.cs (revision 4279)
+++ src/Parser.cs (working copy)
@@ -70,6 +70,7 @@
return q;
}
+
private static string ParseXesamCollectible(XPathNavigator nav, CollectibleType col)
{
// Got XPathNavigator:
@@ -107,7 +108,20 @@
nav.MoveToParent();
break;
case inSet:
- Console.Error.WriteLine(TBD: {0}, nav.Name);
+ nav.MoveToFirstChild();
+
+ string name = ParseXesamField(nav);
+
+ bool first = false;
+ while (nav.MoveToNext()) {
+ if (!first)
+first = true;
+ else
+q += or ;
+ q += name + : + nav.Value;
+ }
+
+ nav.MoveToParent();
break;
case contains:
goto case equals;
@@ -156,7 +170,7 @@
return q;
}
- public static string ParseXesamQuery(string xmlQuery)
+ public static string ParseXesamQuery(string xmlQuery)
{
XmlTextReader tReader = new XmlTextReader(new System.IO.StringReader(xmlQuery));
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Implement inSet in beagle xesam adaptor
What (if any) major parts of the Xesam interface are we missing? Or do we implement poorly? If we are 100%, that's awesome, but if not, I want to look into getting us completely compliant so we can push nautilus/gtkfilechooser supporting Xesam, not individual API's. On Dec 13, 2007 11:27 AM, Arun Raghavan [EMAIL PROTECTED] wrote: On 13/12/2007, Anders Rune Jensen [EMAIL PROTECTED] wrote: Hi With the new libbeagle interface he is a patch that implements the missing inSet keyword in the Xesam interface. Modified a bit and committed (r4280). Thanks! -- Arun Raghavan (http://nemesis.accosted.net) v2sw5Chw4+5ln4pr6$OFck2ma4+9u8w3+1!m?l7+9GSCKi056 e6+9i4b8/9HTAen4+5g4/8APa2Xs8r1/2p5-8 hackerkey.com ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers -- Cheers, Kevin Kubasik http://kubasik.net/blog ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
beagle problem
Sorry for sending again this mail, my email address at ieee.org is only an alias for the address at gmail.com. Hello to everyone, I have beagle 0.3.1 installed on Ubuntu 7.10 Gutsy. Gutsy comes with beagle and libbeagle 0.2.18 in the repositories, so I made my own packages for the newest version, installed them and created the indexes, including the static ones. However some other programs (nautilus and beaglefs) depend on libbeagle0 (i.e. the 0.2.18 version of the library) so I left this package installed and didn't install libbeagle1 (the name I gave to the package for the 0.3.0 version of the library). I have noticed some problems with the searches: beagle-search only finds files in my home directory, while nautilus finds files in my home directory *and* those listed in the static indexes. beagle-search seems to ignore the static indexes, although these are listed by beagle-index-info. Another problem is related to beaglefs that doesn't work at all. When I run it with this command: beaglefs -d Figaro /home/my home dir/gb it gives the following output unique: 1, opcode: INIT (26), nodeid: 0, insize: 56 INIT: 7.8 flags=0x0003 max_readahead=0x0002 INIT: 7.8 flags=0x max_readahead=0x0002 max_write=0x0002 unique: 1, error: 0 (Success), outsize: 40 ** (process:22088): WARNING **: could not handle IsPersistent ** (process:22088): WARNING **: could not handle IsPersistent repeat this line many times ** (process:22088): WARNING **: could not handle IsPersistent ** CRITICAL **: beagle_inode_new: assertion `mime_type *mime_type != '\0'' failed aborting... and doing an ls of the /home/my home dir/gb returns ls: /home/my home dir/gb: Transport endpoint is not connected Please note that fuse is correctly installed and configured, in fact I can use encfs. What is wrong in my setup of beagle? Regards. -- *** * Giuseppe Borzi, Assistant Professor at the * * University of Messina - Department of Civil Engineering * * Address: Contrada di Dio, Messina, I-98166, Italy * * Tel: +390903977323 * * Fax: +390903977480 * * email: [EMAIL PROTECTED]* * url: http://www.webalice.it/gborzi1 * *** signature.asc Description: PGP signature ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem
However some other programs (nautilus and beaglefs) depend on libbeagle0 (i.e. the 0.2.18 version of the library) so I left this package installed and didn't install libbeagle1 (the name I gave to the package for the 0.3.0 version of the library). I have noticed some problems with the searches: beagle-search only finds files in my home directory, while nautilus finds files in my home directory *and* those listed in the static indexes. beagle-search seems to ignore the static indexes, although these are listed by beagle-index-info. Thats pretty weird! Are you sure about this ? What happens when you query using beagle-query ? Do a $ tailf -f ~/.beagle/Log/current-Beagle, then start a query in beagle-search - what gets printed in current-Beagle ? Another problem is related to beaglefs that doesn't work at all. When I run it with this command: libbeagle1 is needed for beagle-0.3.x. libbeagle0 might work in some cases but not guaranteed. - dBera -- - Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem
On Thu, 13 Dec 2007 18:33:44 -0500 Debajyoti Bera [EMAIL PROTECTED] wrote: However some other programs (nautilus and beaglefs) depend on libbeagle0 (i.e. the 0.2.18 version of the library) so I left this package installed and didn't install libbeagle1 (the name I gave to the package for the 0.3.0 version of the library). I have noticed some problems with the searches: beagle-search only finds files in my home directory, while nautilus finds files in my home directory *and* those listed in the static indexes. beagle-search seems to ignore the static indexes, although these are listed by beagle-index-info. Thats pretty weird! Are you sure about this ? What happens when you query using beagle-query ? Do a $ tailf -f ~/.beagle/Log/current-Beagle, then start a query in beagle-search - what gets printed in current-Beagle ? This is the output of searching for gfortran that is in the static indexes (6 hits) and in my homedir (4 hits). I searched with both beagle and nautilus. 20071214 01:09:56.3106 05816 Beagle DEBUG: Parsed query 'gfortran' as text_query 20071214 01:09:56.3111 05816 Beagle DEBUG EX: Caught an exception sending Beagle.SearchTermResponse. Shutting down socket. 20071214 01:09:56.3111 05816 Beagle DEBUG EX: System.IO.IOException: Write failure --- System.Net.Sockets.SocketException: The socket has been shut down 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.Net.Sockets.Socket.Send (System.Byte[] buf, Int32 offset, Int32 size, SocketFlags flags) [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x0] --- End of inner exception stack trace --- 20071214 01:09:56.3111 05816 Beagle DEBUG EX: 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at Beagle.Util.UnclosableStream.Write (System.Byte[] buffer, Int32 offset, Int32 count) [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.IO.BufferedStream.Flush () [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.IO.StreamWriter.Flush () [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.Xml.XmlTextWriter.Flush () [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.Xml.Serialization.XmlSerializer.Serialize (System.Xml.XmlWriter writer, System.Object o, System.Xml.Serialization.XmlSerializerNamespaces namespaces) [0x0] 20071214 01:09:56.3184 05816 Beagle DEBUG: Parsed query 'gfortran' as text_query 20071214 01:09:56.3996 05816 Beagle DEBUG EX: Caught an exception sending Beagle.HitsAddedResponse. Shutting down socket. 20071214 01:09:56.3996 05816 Beagle DEBUG EX: System.IO.IOException: Write failure --- System.Net.Sockets.SocketException: The socket has been shut down 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.Net.Sockets.Socket.Send (System.Byte[] buf, Int32 offset, Int32 size, SocketFlags flags) [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x0] --- End of inner exception stack trace --- 20071214 01:09:56.3996 05816 Beagle DEBUG EX: 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at Beagle.Util.UnclosableStream.Write (System.Byte[] buffer, Int32 offset, Int32 count) [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.IO.BufferedStream.Flush () [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.IO.StreamWriter.Flush () [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.Xml.XmlTextWriter.Flush () [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.Xml.Serialization.XmlSerializer.Serialize (System.Xml.XmlWriter writer, System.Object o, System.Xml.Serialization.XmlSerializerNamespaces namespaces) [0x0] 20071214 01:10:14.2454 05816 Beagle DEBUG: Parsed query 'gfortran' as text_query Another problem is related to beaglefs that doesn't work at all. When I run it with this command: libbeagle1 is needed for beagle-0.3.x. libbeagle0 might work in some cases but not guaranteed. Ok, I'll try to recompile beaglefs with libbeagle1 and report the result. -- *** * Giuseppe Borzi, Assistant Professor at the * * University of Messina - Department of Civil Engineering * * Address: Contrada di Dio, Messina, I-98166, Italy * * Tel: +390903977323 * * Fax: +390903977480 * * email: [EMAIL PROTECTED]* * url: http://www.webalice.it/gborzi1 *
Re: beagle problem
libbeagle1 is needed for beagle-0.3.x. libbeagle0 might work in some cases but not guaranteed. I tried to compile beaglefs with libbeagle 0.3.0, but it fails because beaglefs sources include some calls to beagle_query_add_hit_type which doesn't seem to be available in the new library version. Possibly this explains why beaglefs doesn't work, but in this case it is a beaglefs bug. -- *** * Giuseppe Borzi, Assistant Professor at the * * University of Messina - Department of Civil Engineering * * Address: Contrada di Dio, Messina, I-98166, Italy * * Tel: +390903977323 * * Fax: +390903977480 * * email: [EMAIL PROTECTED]* * url: http://www.webalice.it/gborzi1 * *** signature.asc Description: PGP signature ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem
However some other programs (nautilus and beaglefs) depend on libbeagle0 (i.e. the 0.2.18 version of the library) so I left this package installed and didn't install libbeagle1 (the name I gave to the package for the 0.3.0 version of the library). I have noticed some problems with the searches: beagle-search only finds files in my home directory, while nautilus finds files in my home directory *and* those listed in the static indexes. beagle-search seems to ignore the static indexes, although these are listed by beagle-index-info. Thats pretty weird! Are you sure about this ? What happens when you query using beagle-query ? Do a $ tailf -f ~/.beagle/Log/current-Beagle, then start a query in beagle-search - what gets printed in current-Beagle ? This is the output of searching for gfortran that is in the static indexes (6 hits) and in my homedir (4 hits). I searched with both beagle and nautilus. 20071214 01:09:56.3106 05816 Beagle DEBUG: Parsed query 'gfortran' as text_query 20071214 01:09:56.3111 05816 Beagle DEBUG EX: Caught an exception sending Beagle.SearchTermResponse. Shutting down socket. 20071214 01:09:56.3111 05816 Beagle DEBUG EX: System.IO.IOException: Write failure --- System.Net.Sockets.SocketException: The socket has been shut down 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.Net.Sockets.Socket.Send (System.Byte[] buf, Int32 offset, Int32 size, SocketFlags flags) [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x0] --- End of inner exception stack trace --- 20071214 01:09:56.3111 05816 Beagle DEBUG EX: 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at Beagle.Util.UnclosableStream.Write (System.Byte[] buffer, Int32 offset, Int32 count) [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.IO.BufferedStream.Flush () [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.IO.StreamWriter.Flush () [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.Xml.XmlTextWriter.Flush () [0x0] 20071214 01:09:56.3111 05816 Beagle DEBUG EX: at System.Xml.Serialization.XmlSerializer.Serialize (System.Xml.XmlWriter writer, System.Object o, System.Xml.Serialization.XmlSerializerNamespaces namespaces) [0x0] 20071214 01:09:56.3184 05816 Beagle DEBUG: Parsed query 'gfortran' as text_query 20071214 01:09:56.3996 05816 Beagle DEBUG EX: Caught an exception sending Beagle.HitsAddedResponse. Shutting down socket. 20071214 01:09:56.3996 05816 Beagle DEBUG EX: System.IO.IOException: Write failure --- System.Net.Sockets.SocketException: The socket has been shut down 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.Net.Sockets.Socket.Send (System.Byte[] buf, Int32 offset, Int32 size, SocketFlags flags) [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x0] --- End of inner exception stack trace --- 20071214 01:09:56.3996 05816 Beagle DEBUG EX: 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at Beagle.Util.UnclosableStream.Write (System.Byte[] buffer, Int32 offset, Int32 count) [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.IO.BufferedStream.Flush () [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.IO.StreamWriter.Flush () [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.Xml.XmlTextWriter.Flush () [0x0] 20071214 01:09:56.3996 05816 Beagle DEBUG EX: at System.Xml.Serialization.XmlSerializer.Serialize (System.Xml.XmlWriter writer, System.Object o, System.Xml.Serialization.XmlSerializerNamespaces namespaces) [0x0] 20071214 01:10:14.2454 05816 Beagle DEBUG: Parsed query 'gfortran' as text_query It still does not make sense :( I am surprised nautilus actually worked since it uses incompatible libbeagle0, but I am more surprised that nautilus worked and beagle-search did not! You built and installed everything correctly - right ? Do you get all the results when you do $ beagle-query gfortran -- - Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem
On Thu, 13 Dec 2007 19:51:06 -0500 Debajyoti Bera [EMAIL PROTECTED] wrote: However some other programs (nautilus and beaglefs) depend on libbeagle0 (i.e. the 0.2.18 version of the library) so I left this package installed and didn't install libbeagle1 (the name I gave to the package for the 0.3.0 version of the library). I have noticed some problems with the searches: beagle-search only finds files in my home directory, while nautilus finds files in my home directory *and* those listed in the static indexes. beagle-search seems to ignore the static indexes, although these are listed by beagle-index-info. Thats pretty weird! Are you sure about this ? What happens when you query using beagle-query ? Do a $ tailf -f ~/.beagle/Log/current-Beagle, then start a query in beagle-search - what gets printed in current-Beagle ? This is the output of searching for gfortran that is in the static indexes (6 hits) and in my homedir (4 hits). I searched with both beagle and nautilus. It still does not make sense :( I am surprised nautilus actually worked since it uses incompatible libbeagle0, but I am more surprised that nautilus worked and beagle-search did not! You built and installed everything correctly - right ? Do you get all the results when you do $ beagle-query gfortran beagle-query gfortran gives the correct results, i.e. 4 hits in my homedir, 6 in the static indexes and a new one from the webpages, because I have the firefox-beagle extension installed. I think the install is ok, I modified the debian files of the beagle 0.2.18 package, splitting them in two because of the separation of libbeagle from beagle. But if you think it can be useful, I'll uninstall the beagle packages and install from source. I've made some other test, and I've seen that beagle-search does find files in the applications static index, but fails in the documentation static index. beagle-query and nautilus work fine. BTW, beagle-index-info reports the static indexes as Name: windows (I don't have a windows partition) Count: 0 Crawling: False Name: applications Count: 319 Crawling: False Name: documentation Count: 53585 Crawling: False Thanks for helping me so fast! -- *** * Giuseppe Borzi, Assistant Professor at the * * University of Messina - Department of Civil Engineering * * Address: Contrada di Dio, Messina, I-98166, Italy * * Tel: +390903977323 * * Fax: +390903977480 * * email: [EMAIL PROTECTED]* * url: http://www.webalice.it/gborzi1 * *** signature.asc Description: PGP signature ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem
I've made some other test, and I've seen that beagle-search does find files in the applications static index, but fails in the documentation static index. beagle-query and nautilus work fine. Oh ... beagle-search explicitly excludes documentation index while searching. The documentation index is used by yelp (gnome help browser). Apparently documentation results in beagle-search was confusing users and so it was blacklisted from general search. - dBera -- - Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: beagle problem
On Thu, 13 Dec 2007 20:30:29 -0500 Debajyoti Bera [EMAIL PROTECTED] wrote: I've made some other test, and I've seen that beagle-search does find files in the applications static index, but fails in the documentation static index. beagle-query and nautilus work fine. Oh ... beagle-search explicitly excludes documentation index while searching. The documentation index is used by yelp (gnome help browser). Apparently documentation results in beagle-search was confusing users and so it was blacklisted from general search. - dBera Thanks for the explanation and I'm sorry for wasting your tim. I didn't know this feature of beagle and got confused :-) . -- *** * Giuseppe Borzi, Assistant Professor at the * * University of Messina - Department of Civil Engineering * * Address: Contrada di Dio, Messina, I-98166, Italy * * Tel: +390903977323 * * Fax: +390903977480 * * email: [EMAIL PROTECTED]* * url: http://www.webalice.it/gborzi1 * *** signature.asc Description: PGP signature ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
