Hi Chris,

This is not supported since it is hard to define what is the important information to be stored. E.g.: usually it is enough to store widget preferred location of all nodes and a graph structure itself (node and edge objects). But there are other cases which requires more data to store. If the library would have built-in serialization support, then it would have to define an API for storing the node/edge objects since there are represented as "java.lang.Object" and the library does not know how to store/recreate them. Also there file format could vary from plain text file to XML or binary file, ...

For the reasons above, I was scared that the serialization is so different for each use-case that it is hard to write something generic enough. Therefore I have decided to exclude the serialization support from the library.

Anyway, please, let me know if you have an idea how to make the support.

Regards, David

Chris Palmer wrote: