Hi Mathieu,
To profile, which kind of visualization are you using? A
ROMondrianViewBuilder or a ROView? I'm saying this because a ROView
rendering a set of ROElements without any interaction will maybe help
you to isolate problems related with rendering and problems related with
events.
I believe that yes, first of all it would be useful to use a good method
to select which elements are visible and which of them are not. However,
refreshing only the reached elements might be a bit complicated in the
case you have other elements behind. Ie, when having overlapping
elements maybe you should first find them and then refresh them too,
which maybe can be expensive as you maybe need to do run through the
view's elements. Because of this, I liked the idea of a tile system in
which you refreshed a tile with a set of elements inside. But I
understand the reasons of not liking it because it will add more
complexity to Roassal :)
I also like the idea of using an image to render instead of drawing all
the shape.
Cheers,
Vanessa.
On 06/26/2013 08:50 AM, mathieubmddehouck(a)mailoo.org wrote:
Hi
I just begin looking after point of optimisation into Roassal and I
there are different points :
- firstly, it is not easy to profile
- it seems that when we move the mouse on the visualisation then it
draws everything each time we move the mouse.
And of course the biggest the visualisation is, the hottest the
computer is to be.
So maybe we should either, only draw the visible things (we must know
what is visible easily),
or we should draw the whole visualisation as a picture (bitmap
or svg ) in a buffer and then just navigate in it, and keeping a list
of visible things (not to be drawn but to be checked for interactions).
I think the picture is a good solution (maybe not a perfect one) since
refreshing a picture is fine easier than redrawing the whole
visualisation.
And we should only draw changing elements with another color when
dragging them.
What do you think about that ??
Regards
Mathieu
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev