|
a/src/doc/user/usermanual.sgml |
|
b/src/doc/user/usermanual.sgml |
|
... |
|
... |
477 |
</sect1>
|
477 |
</sect1>
|
478 |
|
478 |
|
479 |
<sect1 id="rcl.indexing.beaglequeue">
|
479 |
<sect1 id="rcl.indexing.beaglequeue">
|
480 |
<title>Using Beagle WEB browser plugins</title>
|
480 |
<title>Using Beagle WEB browser plugins</title>
|
481 |
|
481 |
|
482 |
<para><application>Beagle</application> is a concurrent desktop
|
482 |
<para><application>Beagle</application> is (was?) a concurrent desktop
|
483 |
indexer, built on Lucene and the Mono project (C#), for which a
|
483 |
indexer, built on Lucene and the Mono project (C#), for which a
|
484 |
number of add-on browser plugins were written. These work by
|
484 |
number of add-on browser plugins were written. These work by
|
485 |
copying visited web pages to an indexing queue directory, which the
|
485 |
copying visited web pages to an indexing queue directory, which the
|
486 |
indexer then processes.</para>
|
486 |
indexer then processes. Especially, there is a
|
|
|
487 |
<application>Firefox</application> extension.</para>
|
487 |
|
488 |
|
488 |
<para>If, for any reason, you so happen to prefer &RCL; to
|
489 |
<para>If, for any reason, you so happen to prefer &RCL; to
|
489 |
<application>Beagle</application>, you can still use
|
490 |
<application>Beagle</application>, you can still use the
|
490 |
the browser plugins (they are written in Javascript and completely
|
491 |
<application>Firefox</application> plugin, which is written in
|
491 |
independant of C#, Beagle, Lucene...). &RCL; can process the
|
492 |
Javascript and completely independant of C#, Beagle, Lucene..., and
|
492 |
<application>Beagle</application> queue directory. Of course, this
|
493 |
set &RCL; to process the <application>Beagle</application> queue
|
493 |
supposes that <application>Beagle</application> is not running,
|
494 |
directory. This supposes that <application>Beagle</application> is
|
494 |
else both programs will fight for the same files.</para>
|
495 |
not running, else both programs will fight for the same
|
|
|
496 |
files.</para>
|
495 |
|
497 |
|
496 |
<para>This feature can be enabled in the GUI indexing configuration
|
498 |
<para>This feature can be enabled in the GUI indexing configuration
|
497 |
panel, or by editing the configuration file (set
|
499 |
panel, or by editing the configuration file (set
|
498 |
<literal>processbeaglequeue</literal> to 1).</para>
|
500 |
<literal>processbeaglequeue</literal> to 1).</para>
|
|
|
501 |
|
|
|
502 |
<para>There are more recent instructions about how to find and
|
|
|
503 |
install the <application>Firefox</application> extension on the
|
|
|
504 |
<ulink url="https://bitbucket.org/medoc/recoll/wiki/IndexBeagleWeb">
|
|
|
505 |
Recoll wiki</ulink>.</para>
|
|
|
506 |
|
499 |
</sect1>
|
507 |
</sect1>
|
500 |
|
508 |
|
501 |
<sect1 id="rcl.indexing.periodic">
|
509 |
<sect1 id="rcl.indexing.periodic">
|
502 |
<title>Periodic indexing</title>
|
510 |
<title>Periodic indexing</title>
|
503 |
|
511 |
|
504 |
<sect2 id="rcl.indexing.periodic.exec">
|
512 |
<sect2 id="rcl.indexing.periodic.exec">
|