Re: Policy question

[Martin Sevior <msevior seviorpc ph unimelb edu au>]

On Fri, 2004-04-30 at 09:59, Christopher Orr wrote:
> On 29/04/04 19:54, Lukas Lipka wrote:
> > But that would drop out most of the keywords and dashboard woudlnt
> > generate relevant matches.
> 
> What Stephen meant was that you would still match against all keywords, 
> but the most-common matches would come straight from memory, while the 
> less-common keywords would still be sent to sqlite as usual.  Hence 
> "it's quicker than usual most of the time". :)
> 
> > On Thu, 2004-04-29 at 15:21, Stephen Caldwell wrote:
> >>Maybe instead of loading the entire set of mappings, you can load just
> >>load the most frequently used keywords. This way you can reduce the
> >>amount of storage required and it's quicker than usual most of the time.
> 
> It's certainly something to think about, as I indexed part of my home 
> directory and ended up with a 70MB database.  Queries took a *very* long 
> time.  I think it's time for me to experiment with postgres..
> 
> Also, in case anyone else has been trying to use the indexer with 
> non-text files, Julian's fix of setting UseShellExecute to false works 
> nicely.  I just managed to successfully index a large number of papers 
> in PS format, which gave some interesting results in Dashboard!
> 

For what it's worth I think this indexer combined with dashboard is THE
killer app for GNOME. With the rise of the awareness of what google can
do for the internet, ordinary users are now asking "Why can't I google
my desktop?". The indexer already brings in a number of non-GNOME-core
apps, why sell it short now? 

Go for postgres!

Cheers

Martin

> Chris
> _______________________________________________
> Dashboard-hackers mailing list
> Dashboard-hackers gnome org
> http://mail.gnome.org/mailman/listinfo/dashboard-hackers