[yocto] [PATCH 2/2] rrs: avoid too many columns in the recipes table

Belen Barros Pena belen.barros.pena at linux.intel.com
Thu Aug 13 06:25:36 PDT 2015


Currently, when you select 'Can't be updated' in the upstream
status filter, the resulting table will add the 'No update reason'
column to the default column set.

Although this is probably useful information to see in the
table itself, it results in too many columns, and a rather
unpleasant layout change.

This patch hides the 'Summary' column whenever you select
'Can't be updated' in the upstream status filter, effectively
replacing the 'Summary' with the 'No update reason' column,
which is probably more relevant in this context. Now you
have less columns distracting you, and a slightly less
jumpy layout change.

A designer would have come up with this solution in the
first place. Sadly, she was never asked.

Signed-off-by: Belen Barros Pena <belen.barros.pena at linux.intel.com>
---
 templates/rrs/recipes.html | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/templates/rrs/recipes.html b/templates/rrs/recipes.html
index 3ac73d2..8927b2f 100644
--- a/templates/rrs/recipes.html
+++ b/templates/rrs/recipes.html
@@ -218,8 +218,10 @@ $(document).ready(function() {
     function applyFilters() {
         if (upstreamStatus == 'Can\'t be updated') {
             $('.no_update_reason_column').show()
+            $('.summary_column').hide()            
         } else {
             $('.no_update_reason_column').hide()
+            $('.summary_column').show()            
         }
 
         if (upstreamStatus == 'All') {
-- 
2.3.2 (Apple Git-55)




More information about the yocto mailing list