Installed 'autocomplete' jQuery widget.

I will probably need this because figuring out what to type in is a bitch. IE9
does not support <datalist>s much to my disappointment. I was hoping that the
default css would suffice but everything looks way too transparent and I get a
stupid message on how many items I may select from.
Improved ui stylesheet to make it look more OS-native.

(Windows XP that is). I couldn't figure out why the border attribute wasn't
doing anything, so I used a 1px margin and a dark bg color to mimic something
similar. Henceforth, <li> items have white background and a 65% sans-serif
font, which looks kind-of OS native on Windows XP.
I also removed the silly 3D effect on item selection and inverted the colors
instead.
Initiated suggestions on text input focus.

This renders the minified version useless since it does not adhere to my
awesome improvements.
Removed minimized jquery-ui css and javascript.
Added 'maxItems' option to limit menu size.

Not sure if I can use it this way because there is no indication that the list
was abridged. It defaults to Infinity for this reason.
Initialized 'content' <input> as autocomplete widget.

This is an early testing stage and needs the following improvement:
- patterns with parantheses create no match because these have RegExp special
  meaning. It makes sense but may be somewhat counter-intuitive for those not
  familiar with the syntax.
  Employing the [ {label:.., value:...}, .. ] source array option might just
  fix it.
- I set a fixed type as first array element of start_key/end_key, when in the
  real application I should initiate one $.getJSON for every document type.
Solved two issues as discussed in the last commit.

The string replacement is pretty neat; Unfortunately autocomplete seems to find
its matches based on the 'label' property, instead of 'value' (or vice versa).
The list therefore vanishes after I select a converted item. E.g. if my items
label is '2009/10', its value is '2009\/10', and nothing matches the backslash.
These multiple $.getJSONs are only working half-way and I end up with duplicate
suggestions. This is a result of my poor _view design. I think the type should
go to the end despite its ghastly look.
Improved _view/fields-values.

This new view makes more use of the reduce function by providing a count, a
range for numbers and if the field happens to be an object or array, I can
probably think of something too.
'doc.type' was moved to the end of the array key because I want to histogram
identical field names of different doc types.
Changed application according to new _view/fields-values.

This looks way simpler than before, but I may end up getting suggestions that
are not really in my current selection. It erases duplicate suggestions on the
other hand.
Fixed wrong autocomplete suggestions.

That certainly was easy: I just put value.label at the highest priority and now
suggestions keep showing up even after an item was selected (and its value was
copied into the text input).
I definitely should file some pull requests to these people, this seems a lot
like work in progress.
Fixed wrong jQuery selection.
Updated autocomplete suggestions on filter removal.

Removing counts as editing and therefore the filter selection box may
change. I also removed an accidental two-space.
Cleared filter text input if field selection has changed.

There was one tricky part that I have to shift the autocomplete update just
inbetween these form val() statements. Otherwise the update would either work
with the wrong field name or clear the search term if I want to delete (i.e.
edit) a filter.