Changes for page RealtimeLivetable

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -461,6 +461,8 @@
461	461
462	462	Notion also allows the user to modify not only the data but also the structure of the table (adding / removing columns, changing type of column, ...). When displaying a Livetable on a page this is not desired, the user should only be able to modify permanently the data. What we could do is let the user perform several operations on the columns only on its local instance of the Livetable, like re-ordering, showing or hiding them.
463	463
	464	+As several display layout would be available (table, cards, ...), we also need to consider if we want these features to be implemented in the same way for each layout. If it's the case, that means less development time, and more coherence between the layouts. However, certain layout could have a better suited implementation that would be more intuitive for the user.
	465	+
464	464	== Sorting ==
465	465
466	466	For the moment, we can only sort the table according to one column.
...	...	@@ -495,12 +495,10 @@
495	495
496	496	(Or with color to be more distinguishable from each other)
497	497
498		-[[image:image-20200511112456-11.png||height="88" width="563"]]
	500	+[[image:image-20200511160945-2.png||height="89" width="561"]]
499	499
500	500	Not all the columns have to sort the data, here only //Title// and //Date// are used (unused columns shows a ghost triangle on hover):
501	501
502		-[[image:image-20200511160945-2.png||height="89" width="561"]]
503		-
504	504	When we left-click on the icon (or the whole title):
505	505
506	506	* if the column was already sorting (at any level), it changes the direction of the sort (asc / desc)
...	...	@@ -553,9 +553,9 @@
553	553
554	554	=== Solution 3 ===
555	555
556		-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.
	556	+We create a sub-menu above the table where we can specify the order of the columns in the multi-sort. This solution would work on any layout.
557	557
558		-We could still display the triangle icon in the header to indicate that the column is currently sorting the table.
	558	+We could still display the triangle icon in the table header to indicate that the column is currently sorting the table.
559	559
560	560	== Filtering ==
561	561
...	...	@@ -616,7 +616,7 @@
616	616
617	617	=== Solution 2 ===
618	618
619		-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.
	619	+We create a sub-menu above the table where we can specify the filters we want to apply to each columns (as Notion does). This solution would work on any layout.
620	620
621	621	Pros:
622	622
...	...	@@ -631,10 +631,12 @@
631	631
632	632	=== Solution for the tag cloud ===
633	633
634		-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.
635		-
636	636	The tag select should use the same picker than the selects in the Livetable filters.
637	637
	636	+If we choose the solution 1, 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.
	637	+
	638	+If we choose the solution 2, we can add a special "tags" property in the filtering sub-menu above the table.
	639	+
638	638	== Filtering operators ==
639	639
640	640	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.