State of Toaster tables

State of Toaster tables

[Barros Pena, Belen]

As part of the Bootstrap 3 migration work, Michael Wood moved most of the
tables in the build data section to tables.py:

* packages installed
* packages built
* recipes
* tasks (and its variations to report time, CPU usage and disk I/O)

There are a few tables still not migrated to the tables.py framework,
because they are a bit particular:

1. The "directory structure" table, which uses an additional jQuery
plugin. This table would benefit from a search feature, but it would
require some thinking, since the table includes expand/collapse
functionality

2. The "BitBake variables" table. We are planning some enhancements for
this table (https://bugzilla.yoctoproject.org/show_bug.cgi?id=5811), so we
should probably just migrate this table as part of that work

3. All tables in the details pages (recipes, packages built and packages
installed). Here comes a breakdown:

3.1 Recipe tasks. Page: recipe details. Lists all the tasks executed to
build a certain recipe

3.2 Recipe packages. Page: recipe details. Lists all the packages produced
by a certain recipe

3.3 Recipe dependencies. Page: recipe details. Lists the dependencies of a
certain recipe

3.4 Recipe reverse dependencies. Page: recipe details. Lists the reverse
dependencies of a certain recipe

3.5 Generated files. Page: built package details. Lists the files
generated by a package that was built, but not installed in a rootfs

3.6 Package dependencies. Page: built package details. Lists the files
generated by a package that was built, but not installed in a rootfs

3.7 Generated files. Page: installed package details. Lists the files
generated by a package that was installed in a rootfs

3.8 Package dependencies. Page: installed package details. Lists the
dependencies of a package that was installed in a rootfs

3.9 Package reverse dependencies. Page: installed package details. Lists
the reverse dependencies of a package that was installed in a rootfs

All the 3.x tables have the following in common:

1. They show in a page with a 2-column layout (like the tables shown in
the layer details pages, or custom recipe details pages)

2. They are generally short and simple (although there are exceptions. For
example, some packages can have more than 100 reverse dependencies, and
some packages produce a ton of files).

There are 2 more tables in the build data section that might not be worth
changing at all:

* the table of layers we show in the "Summary" tab of the Configuration
page 
* the "Prebuilt task could be based on" table that we provide for
"Prebuilt" tasks in the task details page

Any questions, let me know

Cheers

Belén