I would like to know the data flow diagram of Cesium.
A http://en.wikipedia.org/wiki/Call_graph or http://en.wikipedia.org/wiki/Control_flow_graph would be nice. Can eclipse produce a graph like this for Cesium? When an error occurs the browser will yield a call order about 8 functions deep.
I want not Control_flow_graph.
I’d like to know DTD(Data Flow Diagram) or UML(Unified Modeling Language) of Cesium API.
I will say that we are long overdue for writing up a general architecture overview for Ceisum, but I think our tutorials paint a decent picture for the time being.
You’d think browsers would have a way to make a graph while a program is running. Sure it might not explore all of the possible branches, but it would at least be something.
Perhaps one could make a program that simply adds this to the beginning of every function of selected files:
And this before each function call in that function
console.log(“caller name calling callee name”);
Then the function names would be logged as the program ran using as many of the program functions as possible. Then have another program analyze the resulting log, removing the many repeated patterns, and provide a pretty good base graph automatically. From a base graph one could manually annotate as to why it would branch this way or that way.