New Design for Visualize

[stormpython]

Changes to the appearance of the visualize interface.

[stormpython]

jenkins test it

[rashidkpc]

Move colors out to variables, reuse kibanaGrays

[rashidkpc]

This ul inside another ul doesn't feel right. It sort of feels like you're going for a table, but I don't think we need a table here either. If you're doing this just to put the Type header there, let's just get rid of the type header. Its not an important item

[rashidkpc]

@panda01 Can you also look at this, see if I missed anything?

[stormpython]

Yeah, I caught that. Still working on more changes.

[rashidkpc]

this should be assigning self.hits to the result of the ternary instead of returning it.

[rashidkpc]

Polished design via @alt74 for step 2. We should implement that index pattern selection as a reusable directive, paginated, selectable list. There's lots of places that could be reused. Heck, we could probably reuse it in the future to simplify the saved object loader. Should be able to borrow most/all of the saved object finder styles and code.

The directive should have an isolate scope that takes 3 parameters:

scope: {
  perPage: '=', // The number of items to show on each page
  list: '=', // An array of objects
  onSelect: '=', // a function to pass the selected object to
}

The objects in the list should either require a title property, or you could make that property configurable

[stormpython]

There is a bug in the kbn-href directive. The pull request that corrects it is #6517. This will need to be merged into this pr.

[rashidkpc]

This should be the same height

[rashidkpc]

There's a hover effect on the active tab, but not on the inactive ones. This should be the other way around

[rashidkpc]

Put this inside the saved-object-finder above. Same with all of the .finder* classes

[stormpython]

@rashidkpc, I am confused. Aren't they already under the saved-object-finder?

[rashidkpc]

So they are, my bad

[rashidkpc]

This LGTM now, merging