Page History

...

• Config tree is still slow
  
  • When comparing M5's config tree with a Vaadin prototype using the same JCR containers, there is still quite a big latency in the config tree when expanding a node.
    
    • Try without config app's inplace editing (uses a field factory) => no significant improvement
    • Try without MagnoliaTable / TreeTable => no significant improvement
    • Try without cell style generator => no significant improvement
  • The tree seems to repaint (scrollbar flickers a bit) several times more than in the prototype (scrollbar might blink once at all).
    
    • Investigate whether MagnoliaTable/TreeTable does explicit repaint, refreshes row cache, or forces layout again.
    • Replacement with regular Table/TreeTable shows no significant improvement either.
  • Column widths are actually updated for all the table, when expanding/collapsing nodes!
    • This is mostly visible when expanding a node deeper in the tree than any other expanded node: first column increases width, though the width update does happen all the time.
    • This does not occur in separate prototype.

• Expanding / collapsing Collapsing can still jump
  
  • -Briefly while repainting

Remarks

• It is interesting to note that our JCR containers are fine; they are not causing performance flaws.
  
  • Some methods however should be left unsupported since the container should be read-only, in other words, persistance is not managed by the container.
    
    • There is interesting insight on this in the Vaadin book section about SQL container.
• Vaadin Table is too tightly coupled with lazy data model mechanism - there should be a way to disable page buffering mechanism entirely.
  
  • There will eventually be a new Table component in a not-so-soon future Vaadin 7 version

...