Perhaps a poorly-named branch, but I'd like to implement some display of data dependencies. Whimsy swizzles a lot of different data sources into /public and into various scripts, and it's useful to visualize where all the source data is for different things.
Question: what's the fastest (runtime-wise) way to store the test/dataflow.json dependency data? As JSON to be read (locally if possible), or as a new model in whimsy/ASF that simply reflects the JSON structure as hash? Given that I'd like to add a new ASF::Themes _whimsy_dataflow method that any page might want to implement. So for whimsy pages that display big tables of data, they could have a small footer that does a cut-down version of test/dataflow.cgi, just showing dependencies for their own data page. Obviously, this should move out of /test, but I wasn't sure the best place to put it. Perhaps a new www/docs directory, for "things that aren't code, but document how Whimsy works"? Separately, I thought it might be useful to add our own JSON editor/viewer for simple checking of the various JSON files, but 1) I'm not sure it's useful for anyone else, and 2) my local testing is borked on a JS error. But that's why the branch is named that way. -- - Shane https://www.apache.org/foundation/marks/resources
