Hi Clement,
Pretty exciting.
As Alex says, your desired algorithm is pretty specific, but it looks similar to a UML layout. If you could find one that would fit your needs, it would be a valuable addition to point us to it. Perhaps we can find the resources to implement it.
Now, about your workflow. Roassal alone can already provide value added on top of existing default tools, and it's great that you could show what you could do in one hour. It takes a bit of leap of faith, but then you do not want to go back :).
But, I think you would benefit even more by taking a look at the GTInspector and other related tools. For example, here are a couple of posts that might be of interest (they talk precisely about code analysis in Pharo):
I would actually be interested in helping you build tools that would match your case. The reason is that in order to show the value of these tools we need custom problems - and you happen to have identified some. Could you describe the needs you have in more details?
As far as I can see, the visualization is derived from source code. This can be seen as being similar to how an AST is derived from source code. The GTInspector already provides an implementation of understanding this mapping. For example, in an image with GTInspector (just download the Moose one for quick tests) do:
(Collection>>#collect:) parseTree inspect�
and you get a picture like the attached one.
If you give me more concrete things to look at, I can try to help.
Cheers,
Doru