Thanks, Lucio to clarify it!

I also think we were talking on different scenarios.

We can have all the log content display in a table format with filter and search options.

Example:

\/ Logs (It can be a collapsed area - similar to what we have on Ginger)

| <filter input box> | | <advanced search button/link> |
| <logs in a table format>                                              |

When using the <filter input box>, it will filter the content in the log table.
For the <advanced search button/link>, it can open a new dialog with the input boxes for the new search (a request to be sent to the server) or expand the same content:

| <filter input box> | | +/- <advanced search button/link> |
| Plugin: <input box>                      User: <input box>     |
| Date: <date input box>                ...                               |
|                                                           | Search <button>|

The search option will send a new request to the server and update the log table with the new content.

Does that make sense?

Regards,
Aline Manera

On 02/11/2016 12:31 PM, Samuel Henrique De Oliveira Guimaraes wrote:

Exactly. Advanced search will shape the JSON data and then jQuery Bootgrid will reload and display the new results and handle row filtering and sorting.

Samuel

-----Original Message-----
From: Lucio Correia [mailto:luciojhc@linux.vnet.ibm.com] 
Sent: quinta-feira, 11 de fevereiro de 2016 11:27
To: Samuel Henrique De Oliveira Guimaraes <samuel.guimaraes@eldorado.org.br>; Aline Manera <alinefm@linux.vnet.ibm.com>; Kimchi Devel <kimchi-devel@ovirt.org>
Subject: Re: [Kimchi-devel] [RFC] [Wok] Feature: User Activity Log

On 11-02-2016 08:01, Samuel Henrique De Oliveira Guimaraes wrote:

I think jQuery Bootgrid Data API example covers the performance and requests issues:
http://www.jquery-bootgrid.com/Examples#data-api

However for the search options it is not very easy to edit the markup or behavior. The library provides some styling options but I'm not sure if we can just hide the default search/filter bar and create custom search options (combining "date" and "user" for instance). According to the documentation the search function "Searches in all visible columns for the given phrase. If no argument is passed, it will reset the search. This method is chainable". We can transform the data based on a custom advanced search and then destroy/reload jQuery Bootgrid table but it would reset pagination and it would probably break the default search method.

Samuel

I believe we need to separate here between search and filter.

Search will be through REST API, and will return a set of entries as a result. Aline's concern with performance is here.

Filter will be applied to that result returned by search. In my opinion Samuel is referring to filtering. So no need to combine attributes here, just filtering by text in any column.

Search results are downloadable in a txt file. Filter results are not.

Just making sure we are all in the same page.

Thoughts?

Regards,
--
Lucio Correia
Software Engineer
IBM LTC Brazil