----- Original Message -----
From: Hans-Christoph Steiner hans@at.or.at To: Jonathan Wilkes jancsika@yahoo.com Cc: "pd-list@iem.at" pd-list@iem.at Sent: Thursday, January 17, 2013 7:00 PM Subject: Re: [PD] search plugin time optimisation
On 01/17/2013 06:33 PM, Jonathan Wilkes wrote:
----- Original Message -----
From: Hans-Christoph Steiner hans@at.or.at To: Jonathan Wilkes jancsika@yahoo.com Cc: "pd-list@iem.at" pd-list@iem.at Sent: Thursday, January 17, 2013 5:06 PM Subject: Re: [PD] search plugin time optimisation
[...]
* Note that my measurements are just for read times. Xapian will
be
writing to an index so
you'll have to factor in write times for _each_ string of file
contents. Those probably aren't
insignificant digits.
The Debian package could generate the cache right after installation.
Mac and
Windows would have to happen on first launch. The benefits of this
would be
real, but it would also take a real amount of work to implement ;)
For the record I have zero interest in investigating how to integrate Xapian into Pd-extended, making sure the tcl bindings actually work and
aren't
just abandonware, making sure it actually works with comparable results on each OS (as opposed to, say, opening and closing files with tcl), and
integrating
Xapian into the Pd-extended build process for OSX and Windows. Those caveats aside I'd be happy to revise the search plugin to use the
Xapian API.
wiki.tcl.tk runs on tclxapian, so its maintained.
Ah, I didn't know that. Good.
The needed packages are all in Debian, so adding xapian support to Pd-extended on Debian-derivs will be trivial (Depends: tclxapian).
Then I'll do "apt-get install tclxapian" and use "package require xapian" in the search plugin and test building an index/searching. But anything outside my current editor window like conf files or xapian/tcl source will be considered soldered firmly onto my motherboard. I.e., I ain't touching it.
-Jonathan
If we get that far, I'll be happy to add xapian to the Pd-extended Windows and Mac OS X builds.
.hc