After MetaCG has moved the development to GitHub (which I still think is awesome), we are now working on improving the package. One of these improvements is the addition of Python bindings to explore generated MetaCGs without the need to write C++ programs.
The next improvement is to unify all tools that produce and consume MetaCG and make them use the actual MetaCG graph library. It probably sounds surprising that this is not already the case. However that is simply due to the MetaCG history. Given the research-tool history and that the library itself was actually only factored out after many other things existed, most of the “utility” tools do not yet use the graph library. Instead they simply read the json and implement their own logic on how to find nodes, interpret the graph and so on. Given that the graph library has matured over time and is in a much more stable state than it was years ago, now is the right time to finally fix that issue.
No responses yet