linux/poky.git/bitbake/lib/toaster/toastergui/buildtables.py, branch uninative-1.5

bitbake: toaster: tasks Remove recipe version from defaults

2016-09-07T23:33:46+00:00

The 'Recipe version' column should not be part of the set of columns shown by default in the tasks table. Set the hidden property for that column to 'True' so that it doesn't show when you load that table for the first time. [YOCTO #10179] (Bitbake rev: 249dd31fcaabbec32fdee30b0c84be90d4f92430) Signed-off-by: Belen Barros Pena Signed-off-by: Michael Wood Signed-off-by: Richard Purdie

bitbake: toaster: updte build tables for locally imported layers

2016-08-10T23:09:29+00:00

Update the build tables section for locally imported layers. Here we do not provide informations such as branch or commit. Because those are locally imported layer(s). [YOCO #9911] (Bitbake rev: 1b0934b45d3704de604405826de9fc1da51ceae1) Signed-off-by: Sujith H Signed-off-by: Richard Purdie

bitbake: toaster: set non-hideable columns for built recipes table

2016-07-26T07:10:36+00:00

None of the columns in the built recipes table are marked as not hideable, so it is possible to remove all the columns and make the table disappear. Set the recipe name and version columns as not hideable. Also rename the "Name" column to "Recipe", for consistency with the design and with other recipe tables. [YOCTO #9833] (Bitbake rev: 3abd0ac300462e6d1335018cf2d0420de7cc8b76) Signed-off-by: Elliot Smith Signed-off-by: Ed Bartosh Signed-off-by: Richard Purdie

bitbake: toaster: set non-hideable columns for build tasks table

2016-07-26T07:10:36+00:00

The task, recipe and order columns in the build tasks table should not be hideable. If they are, it's possible for the table to have all of its columns hidden so that it no longer displays. Set the hideable property to prevent these columns from being hidden. [YOCTO #9833] (Bitbake rev: dc1781e3783724823fd6b0c2d65f6b2771e8d0be) Signed-off-by: Elliot Smith Signed-off-by: Ed Bartosh Signed-off-by: Richard Purdie

bitbake: toaster: BuildTasksTable filters remove outcome NA option

2016-06-15T07:35:05+00:00

In the 'outcome' filter for tasks, remove the 'not applicable' option, since it should not be exposed to users. (Bitbake rev: 4e21817b0d7a91e634bdb2069850627c38fde053) Signed-off-by: Belen Barros Pena Signed-off-by: Michael Wood Signed-off-by: Richard Purdie

bitbake: toaster: BuiltPackagesTable format empty state in packages table

2016-06-15T07:35:05+00:00

The explanatory message in the empty state of the packages built table was missing some spaces. (Bitbake rev: 70f600f86ec4d536004d968919e86d2afa58d585) Signed-off-by: Belen Barros Pena Signed-off-by: Michael Wood Signed-off-by: Richard Purdie

bitbake: toaster: port all build analysis pages to bootstrap 3

2016-06-15T07:35:05+00:00

Port all the pages in the build analysis area to bootstrap version 3. (Bitbake rev: f963b73f0bf32db2df39dd79d8d85184c280cda0) Signed-off-by: Belen Barros Pena Signed-off-by: Michael Wood Signed-off-by: Richard Purdie

bitbake: toaster: buildtables Remove links from non name fields

2016-06-15T07:35:05+00:00

Design change to have no links for non-named fields in BuiltPackagesTable. BuiltRecipesTables and BuildTasksTable. Additionally: - Fix class and elements for Bootstrap3 in help text. - Change title of InstalledPackages table to Packages Included. - Change which columns are default shown/hidden columns. (Bitbake rev: 7c377e161a90184a4786e33951d8c0e30688ba3b) Signed-off-by: Belen Barros Pena Signed-off-by: Michael Wood Signed-off-by: Richard Purdie

bitbake: toaster: Rework displaying package dependencies across Toaster

2016-06-15T07:35:04+00:00

After porting the build table to a unified mechanism for showing dependencies in tables it highlighted that the dependencies selected to be shown were un-filtered. i.e. all dependencies from all contexts were shown. The context for a package's dependencies is based on the target that they were installed onto, or if not installed then a "None" target. Depending on where the template for the dependencies are show we need to switch this target which is why a filter and utility function on the model is added. Additionally to use the same templates in the build analysis we also need to optionally add links to the build data for the packages being displayed as dependencies. Customising a Custom image recipes may or may not have a target depending on whether they have been built or not, if not we do a best effort at getting the dependencies by using the last known target on that package to get the dependency information. [YOCTO #9676] (Bitbake rev: 31e7c26cc31a7c8c78c1464fa01581683bfd2965) Signed-off-by: Michael Wood Signed-off-by: Richard Purdie

bitbake: toaster: port Installed packages table to ToasterTable

2016-06-15T07:35:04+00:00

(Bitbake rev: 2418c092abd9a503becf5e786125f8cdddd8652c) Signed-off-by: Michael Wood Signed-off-by: Richard Purdie