ToDo

• There are some strange behaviours when there are set requests in graphs which come after empty graphs. Actually data gets inserted in other graphs, then. This is a design flaw, so the user should be warned about it. To fix it, we must redesign the concept of graph (also also data) handling. This will possibly require some API changes, while the behaviour must stay consistent for working templates.

• Revise the build system - consider autoconf/automake (or something more lightweight?)

• We still have that feature of applying the style of the first graph to all others. This could cause significant pain with the new features (like Protected graph, Copy-data, etc.). Maybe we should drop that one feature in favor of the others.

Member GraceTMPL::Data::saveinfo (FILE *f, const StringVec *daSet=0)

Make this a stream

Member GraceTMPL::Graph::savedata (FILE *f, StringMap *literalData, int dataonly=0)

Make this a stream

Member GraceTMPL::Graph::saveinfo (FILE *f, const StringVec *daGraph=0, const StringVecMap *daSets=0, const StringVecMap *daStrings=0)

Make this a stream

Member GraceTMPL::Save::enablePipe (int i)

Decide upon pipe policy in case of missing template.

Member GraceTMPL::Save::tmpl_

More than one template for more than one output file? Probably not!

---