Hi guys,
Here is my short question … is it “thinkable” to implement a kind of “double-buffering” for the Vaadin (GWT) Client side renderer?
That means … the whole UI component tree refresh in the browser should happens in a “background” v-app dom element (which is invisible during the dom update), then after this the “background” v-app dom becomes the visible one and the current v-app dom element becomes the background thing …
With this I would have the chance to “adjust” the current shown “view-area” before the real new up2date ui is shown … Background is … our UI is very very “dynamic”, after each user interaction the UI can potential show or hide, before or after the current user-position elements all the time. So this cause a very ugly UI jumping effects. And I hope I can fix this with this double-buffering + “adjust scroll-position” idea.
I tried to explain the jump-effect here in this image a little bit
Thanks.
Hercules