mike-devel/boost_dep_graph

boost_dep_graph's Issues

Investigate enormous memory requirements

Depending on the window size the app requires several hundred megabytes of main memory which seems ridiculous.

When the window is shrunk down, this goes down to ~50MB which is still a lot, but it indicates it is not directly related to any of the data structures directly visible in code (whose size and number stay constant after the initial creation of the graph).

Handle relative include paths

The current assumption is that all boost headers are included via <boost/...> or "boost/...", but e.g. the tests in boost outcome include their own library headers via a relative path e.g.:

 #include "../../include/boost/outcome/outcome.hpp"

Ideally, this should also be handled correctly as well

Autoresize

Currently, the scene size (not the display size or the zoom factor) is hard coded and tuned to the normal boost dependency graph. This should be automatically adjusted depending on the number of nodes in one level and the number of levels in the graph.