Filters

["Barros Pena, Belen" <belen.barros.pena@intel.com>]

I've reviewed all the filters we are going to need for Toaster. It turns
out that only 6 pages will need filters: all builds table, configuration
(for the variables table), tasks table, time, CPU and Disk I/O. However,
the time, CPU and Disk I/O tables are exactly the same as the tasks table,
just with a different set of columns shown by default. Therefore, I hope
we'll be able to reuse the work done for the tasks table filters.

The other tables are made of fields I expect we can make searchable (types
CharField, FilePathField and TextField). Alex: if this is not the case,
please let me know.

The full list of filters:

* For the all builds table (http://www.yoctoproject.org/toaster/):
Outcome, Started on, Completed on, Failed tasks, Errors and Warnings
* For the variables table
(http://www.yoctoproject.org/toaster/build-configuration.html): Set in
file and Description
* For the tasks, time, CPU and Disk I/O tables
(http://www.yoctoproject.org/toaster/all-tasks.html): Order, Executed,
Outcome and Cache attempt

I have reduced all the filters to 3 types:

1. most of them are made of a set of mutually exclusive options. In those,
I've replaced the <select> control with radio buttons, purely because they
allow us to provide help information using the same mechanism as in the
rest of the UI

2. The Order filter in the tasks / time / CPU and disk I/O tables includes
an order range

3. The Started on and Completed on filters in the all builds table include
a date range and use the default calendar widget from jQueryUI

I will produce detailed design documentation next week. In the meantime,
I've pushed all the changes to the prototype
(http://www.yoctoproject.org/toaster) so you can have a look at the
filters and raise any implementation problems.

Cheers

Belén