Closed Garbash closed 9 years ago
This is a big one. I've already got one reason to delve into the current layout code (in d3) because I want it to take into account pictures, so this is the same - treat every node as a rectangle instead of a point.
TBD time :(
I'll start working on it though.
For moral and because it makes sense can we have an extra milestone with the fixes? the CRI milestone has been reached afaict, we are at iterations time.
The simplest and short term doable solution for both of my problems is to treat nodes as circles. The radius will be chosen so that text/images will not overlap. This will not be perfect of course, but should look ok. I'll try to do this tonight.
wrt new milestone - I think it would be easier to just keep this one for bugs and track remaining features. A new milestone would just repeat the same thing. Graph viz issues are global we can open a separate milestone for that. Would that be helpful?
wrt short term solution - Let's discuss the nodes as circles solution on Sunday. For example, I can foresee some issues with that when the node text is very large.
Closing this as, Overlapping is currently treated by implementing the Ring layout, enhancing selection and hover preview.
This is unreadable from a few perspectives, but surely the critical one is that overlapping edge/node text cannot be read. One possible fix is that the node/edge text itself would have some weak repulsive power that would prevent overlap.
@alon any other solutions/suggestions how implement this?