You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, whenever we want to look at the visualization of a graph generated from a trace, we have to export it to a json file to then load it into a visualization written in JavaScript that runs in a browser.
This was made this way, because I new how to use d3 and the visualization is ultimately just a tool for insight-gaining. It has some problems though. When we moved the aggregations back into squeak, that also meant that we could no longer have a look into the aggregations that we made. The way back to the data broke off.
To shorten the feedback look and allow for some kind of going back to the data, it would be good to have the visualization in squeak too.
Hints & Thoughts
one way would be to re-implement d3-force in squeak. For a discussion on that, have a look at the wiki.
The text was updated successfully, but these errors were encountered:
Just three very random pointers, not necessarily of your interest:
There is MagicMouse which allows you to embed a browser (for instance for your localhost HTML w/ JS) in Squeak as a scalable Morph. This way you could use real D3.js
Iirc Roassal3 has a force direct graph visualization type that should work in latest Squeak Trunk
Another implementation of force direct graphs should be included in the block management of Sandblocks
Describe the solution you'd like
Currently, whenever we want to look at the visualization of a graph generated from a trace, we have to export it to a json file to then load it into a visualization written in JavaScript that runs in a browser.
This was made this way, because I new how to use d3 and the visualization is ultimately just a tool for insight-gaining. It has some problems though. When we moved the aggregations back into squeak, that also meant that we could no longer have a look into the aggregations that we made. The way back to the data broke off.
To shorten the feedback look and allow for some kind of going back to the data, it would be good to have the visualization in squeak too.
Hints & Thoughts
The text was updated successfully, but these errors were encountered: