Tough one. In Mondrian, this is not possible to solve. Perhaps by moving to Roassal
we would have a better chance.

Alex, do you want to give a try to work on this one (hint: it's a cool case study :))?

This problem cannot occur in Roassal. Roassal has been designed to not depend on the
underlying gui framework . 

Doru, simply changing "mondrian" for "roassal" in #metamodelMapIn: is apparently a good
start. However, when I click on a node in the view, the tree widget do not get updated.
It is as if the event are not listened. Any idea?

The current implementation is based on drawing the visualization from scratch for every
selection. The scrolling is thus, reset after every redraw.

However, with Roassal we should be able to update the visualization. That is why I
said it can be a nice case study for Roassal.

I see. But redrawing the whole visualization is not a problem in this particular case.
The tree is really small. If I would have hundred thousands of nodes then yes, something
smarter will have to be done for the selection and the scrolling. But currently this
situation has not shown up.

I understood that the pb of Nicolas is to reset the visible frame on the most left
when I select something on the most right. This problem does not occur in Roassal.

I was thinking about using a roassal visu instead of a mondrian one. But the events
are still broken. Any idea how to fix this?

I do not understand what you mean by events. I just updated the browser to use Roassal
instead of Mondrian, and it works. I just had to:
- replace curvedLine with line because there is no curved line at the moment.
- fixed line width

The next step is to not redraw, but just to animate the existing visualization. That
is needed because if you redraw the Roassal visualization from scratch, the scrollbar
will be reset, too.

Not for 4.7

This issue waits for the ROFocusView to work properly within a Glamour context

Maybe my answer to http://code.google.com/p/moose-technology/issues/detail?id=870 helps