facets, results and search widgets with pagination
Initial review, additional notes:
- pls search for XXX:rca - you will see my commnets
- when you deal with them, remove XXX:rca - keep only what needs more discussion

gruntfile.js

- watch:less_compile will likely not work

bower.json
- do we still use/need chai-changes?

better naming?
- widget/base/base_widget.js
- ClassNames  -> paginatedBaseWidget
- facet-collection vs base_widget (we should agree on some consistent conventions)
- widget_mixin_method (ideally, it should be clear from the name itself what is inside - try to avoid too generic names)

relative imports
- should be used only for resources inside the widget (module) -- i.e. ./template etc, but not for resources outside (several levels above: ie. ../multi_callback/... use -> js/components/multi_callback...)

about the paginator
- i think the whole thing could be much easier if you think of it as something that just changes apiQuery (adds additional parameters)
- in this way whole layer of inheritance complexity will be removed(and you could remove all paginated_..... files)
placeholder
made some changes suggested by roman, also implemented hierarchical facet highlighting
Merge pull request #24 from aholachek/romanschanges

Romanschanges