Re: Working With Conduit
- From: "D Bera" <dbera web gmail com>
- To: kevin kubasik net
- Cc: dashboard-hackers gnome org
- Subject: Re: Working With Conduit
- Date: Thu, 6 Dec 2007 08:22:59 -0500
> > That about covers it. kkubasik suggested python-beagle, which I have
> > been experimenting with a little bit. Looking very handy so far.
> >
> > I'm going to create a few prototypes and then i'll be back with
> > another part of my plan :-)
Great! Let us know how it goes.
> As you narrow in, there is a good chance we will need more special
> query keywords (or mappings) (you can list all of them with a
> beagle-query --keywords) , so just something to keep in mind as we
The query keywords in beagle-query --keywords are "fancy names for
human beings" :). If you know the internal property name you want to
query (e.g. as displayed by beagle-query) and whether it is a text or
a keyword property (information available only from the source file),
then you can use
(for text properties) property:name=value
(for keyword properties) keyword:name=value
They work for _any_ property. beagle-query --keywords gives a list of
keywords that are mapped to some of the most popular internal property
names and types.
Hope that helps,
- dBera
--
-----------------------------------------------------
Debajyoti Bera @ http://dtecht.blogspot.com
beagle / KDE fan
Mandriva / Inspiron-1100 user
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]