Alternatively, make a "loop report engine," analogous to the present archive report engine. Or, adapt the existing report engine so it can work on loop data.
This would be the more general solution. -tk On Sun, Jan 8, 2017 at 5:30 AM, mwall <[email protected]> wrote: > darryn, > > beware that there is no single json to rule them all. > > you might do: > > $current.json > > that emits archive records (or loop data) in json format, only to find > that the json you output is not recognized by the plotting library you want > to use. > > in this respect, a jsongenerator might make more sense than putting json > into cheetahgenerator. that way the jsongenerator could have json > templates that specify how the json will be structured. that might be too > much to add to cheetahgenerator, but would make perfect sense for a > jsongenerator. > > or you might want to do it in a standalone 'jsonservice'. > > many people will want to use this for loop data so they get real-time > displays. if you do it as a generator, you will only ever get archive > records. > > so make a jsonservice that has the option of binding to either > new_loop_packet or new_archive_record, and make it have a simple json > templating system to define how the json output should be structured. > > m >
