Changes for page RealtimeLivetable

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

<
From version < 67.5 >
edited by Clément Desableau
on 2020/05/15 14:35
To version < 67.6 >
edited by Clément Desableau
on 2020/05/15 15:06
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -391,7 +391,7 @@
391 391  pros:
392 392  
393 393  * development very active (new release every 2~~3 months)
394 -* implementation modular: we can easily overwrite and adapt the existing functionalities
394 +* modular implementation: we can easily overwrite and adapt the existing functionalities
395 395  * already comes with intended features like: create table from existing element, styling cells by column, or fetch data from server
396 396  
397 397  cons:
... ... @@ -414,7 +414,7 @@
414 414  
415 415  == Solution 2: Using a framework ==
416 416  
417 -We could also re-write entirely the Livetable component by ourselves. As opposed to the solution 1, this would imply more development time, but greater flexibility and maintainability. Instead of using existing code that we have to adapt, we would already build code that meet our needs in the first place.
417 +We could also re-write entirely the Livetable component by ourselves. As opposed to the solution 1, this would imply a little more development time, but greater flexibility and maintainability. Instead of using existing code that we have to adapt, we would already build code that meet our needs in the first place.
418 418  
419 419  In this case, we should use a framework to fasten the development, by automatically binding the HTML table to the JSON object, and helping with event handling.
420 420  
... ... @@ -444,7 +444,6 @@
444 444  
445 445  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.
446 446  
447 -
448 448  == Sorting ==
449 449  
450 450  For the moment, we can only sort the table according to one column.
... ... @@ -481,14 +481,14 @@
481 481  
482 482  [[image:image-20200511112456-11.png||height="88" width="563"]]
483 483  
484 -Not all the columns have to sort the data, here only //Title// and //Date// are used (unused columns shows a triangle only on hover):
483 +Not all the columns have to sort the data, here only //Title// and //Date// are used (unused columns shows a ghost triangle on hover):
485 485  
486 486  [[image:image-20200511160945-2.png||height="89" width="561"]]
487 487  
488 488  When we left-click on the icon (or the whole title):
489 489  
490 -* if the column was already sorting, it changes the direction of the sort (asc / desc)
491 -* else, it became the new level-one sort
489 +* if the column was already sorting (at any level), it changes the direction of the sort (asc / desc)
490 +* else, it became the new level-1 sort
492 492  
493 493  When we right-click on the icon, a sub-menu appears to let us choose the level of sort we want:
494 494  
... ... @@ -497,7 +497,7 @@
497 497  * if we click on the current sort level, it changes its direction
498 498  * else, it overrides the existing sort of the chosen level
499 499  
500 -There are only the first three levels in the sub menu, and more will be displayed if the previous are used.
499 +Only the useful levels are displayed in the sub-menu: an already sorting column cannot show lower level sorts, and a non-sorting column will show levels until the lowest level possible in the current configuration.
501 501  
502 502  Pros:
503 503  

Get Connected