[documancer-devel] new Documancer caching code checked in

[Vaclav S. <vs...@fa...>]

Hi,

I checked in the long-promised generic caching code, any testing would 
be most welcome. Aside from the big internal changes in how the 
updates are carried, there are some UI improvements as well:

* Updating book A's index no longer disables searching in book B.
* You can no longer attempt to search in a book without index.
  Previously, this would result in the UI blocking and waiting
  until the index is regenerated. Now, Documancer will warn you
  the the index is missing (see attached noindex.png) and will
  disable the search box -- it will be enabled again when
  indexing is done (remember: indexing happens in background,
  it's no longer triggered by user action!).
* If a book has index, you can search it even if the index is
  out of date. The index is generated in temporary directory
  and replaces old index when it's fully created, so as long as
  there is at least _some_ index, you can do (potentially inexact)
  searches (see attached oldindex.png).
* Indexing of all books (i.e. even those not currently opened) is
  done in background when you're reading docs, meaning that
  there's a good change that Documancer will already be done
  generating the indexes when you'll need them.

Still missing:

* Prioritization of the updater -- when you select a book in
  Documancer, the updater should stop doing whatever it is it's
  working on and update items owned by currently selected book
  as soon as possible.
* Autodetection of outdated books -- Documancer should check the
  HTML/info/man/whatever files and regenerate the index if they
  changed; currently, you have to do it manually.

Regards,
Vaclav

-- 
PGP key: 0x465264C9, available from http://wwwkeys.pgp.net/