Changes for page RealtimeLivetable

Last modified by Vincent Massol on 2024/02/26 17:54

<
From version < 66.7 >
edited by Clément Desableau
on 2020/05/15 11:54
To version < 66.8 >
edited by Clément Desableau
on 2020/05/15 12:16
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -531,6 +531,8 @@
531 531  
532 532  * it might not be clear that the plus sign refers to creating a new level of sort
533 533  
534 +(Note: with this solution we could still keep the behavior of the right-click as an alternative way to open the sort level sub-menu.)
535 +
534 534  === Solution 3 ===
535 535  
536 536  We create a sub-menu above the table where we can specify the order of the columns in the multi-sort. This is the solutions implemented by Notion.
... ... @@ -571,18 +571,8 @@
571 571  
572 572  With this current design, there is no other way to change the way columns are combined together. For now, all the columns are combined with the "AND" operator. In any way, the operator should also stay the same between each columns to keep the behavior understandable.
573 573  
574 -pros:
576 +Here is a test of design on medium / large layout with a lot of filters:
575 575  
576 -* unlimited number of filter for each column
577 -* filters directly accessible: the user can quickly filter, and knows instantly what's being displayed
578 -
579 -cons:
580 -
581 -* we can only use the "AND" operator between columns with this current design.
582 -* the UI can become charged very quickly
583 -
584 -For instance, here is a test of design on medium / large layout with a lot of filters:
585 -
586 586  [[image:image-20200513104407-1.png||height="189" width="788"]]
587 587  
588 588  and on narrower layout:
... ... @@ -595,10 +595,37 @@
595 595  
596 596  However, on average the user is not going to create 3 filters for each columns, and not filters for each columns. So the UI should stay minimal most of the time.
597 597  
590 +Pros:
591 +
592 +* unlimited number of filter for each column
593 +* filters directly accessible: the user can quickly filter, and knows instantly what's being displayed
594 +
595 +Cons:
596 +
597 +* we can only use the "AND" operator between columns with this current design.
598 +* the UI can become heavy very quickly
599 +
598 598  === Solution 2 ===
599 599  
600 600  We create a sub-menu above the table where we can specify the filters we want to apply to each columns. This is the solutions implemented by Notion.
601 601  
604 +Pros:
605 +
606 +* unlimited number of filter for each column
607 +* as opposed to the solution 1, the width of the filters is not a problem anymore
608 +* keeps the UI lite
609 +
610 +Cons:
611 +
612 +* filters not accessible directly: we are adding steps to access the filters
613 +* filters not viewable by default: we can't know with a glance how the columns are filtered
614 +
615 +=== Solution for the tags ===
616 +
617 +We can add a multi select above the Livetable where the user can easily check or uncheck the tags he wants to see in the table.
618 +
619 +The tag select should use the same picker than the selects in the Livetable filters.
620 +
602 602  == Filtering operators ==
603 603  
604 604  Filtering a string is not the same that filtering a number, a date, or a list of values. Thus, we should not provide the same actions for all type of filters, but adapt according to the filter type.

Get Connected