Fix wider/narrower buttons on pt managment screen. Now supports both relative (css) and absolute widths.

Yanked OM browser default implementation for alpha 1, planning on a more modular implementation for alpha 2.

modifications were needed in Zope (only two files). A lot of unused
(or rarely) features were removed from the Interface package. Slightly
deeper imports are needed.

        clients from maintaing pipelined connections to the Zope server
        (Collector #412)

Allows clean implementation of ZCTextIndex's unindex_object method so that it plays better with ZCatalog's unindex behavior.

Completed Zope integration.

 - Land new pluggable index types, specialized for date values and
   date ranges, from branch.

  - Use more conventional "tests" directory to hold unit tests.

Added management interface to query words in the lexicon and in the process uncovered a BTreeItems bug, whee!

revert unintended change: a function return value of None should be marshalled as an xmlrpc boolean False

show that mapping.get(key, default) has a default value for default.

Casey, you have the baton now.

merged toby-xmlrpclib099-branch. Changed ZPublisher xmlrpc support to allow published methods to return None nested inside a data structure

and code accordingly.

Also rewrote the code to never create a new IIBucket unless one is
really needed (for example, if the input list has only one (bucket, weight)
pair, and the weight is 1, the input bucket can be returned as-is; and
this case will be common with score maps produced by an Okapi index).

    so the import machinery is not invoked on each call.

profile with a warm database cache instead of the cold cache.

    right.  Added a comment explaining what it represents in the
    function.

CosineIndex.query_weight():  rewrote to squash code duplication.  No
change in what it returns (it's always returned an upper bound on
possible doc scores, although people probably haven't thought of it
that way before).

Elsewhere:  consequent changes.

Problems:

+ mhindex.py needs repair, but I can't run it.  Note that its current
  use of query_weight isn't legitimate (the usage doesn't conform to
  the IIndex interface -- passing a string is passing "a sequence",
  but not the intended sequence <wink>).

+ ZCTextIndex doesn't pass query_weight() on.

+ We've defined no methods to help clients compute what needs to be
  passed to query_weight (a sequence of only the positive terms).

  I changed mailtest.py to cheat, but it's doing a wrong thing for
  negative terms.

+ I expect it will be impossible to shake people from the belief that
  100.0 * score / query_weight is some kind of "relevance score".  It
  isn't.  So perhaps better not to expose this in ZCTextIndex.