Open jacmarjorie opened 10 years ago
I see this being a ways down the road, unfortunately...
It would require us to create a standard model object that we export to a user's local machine, or host on a server somewhere that we could reload in the browser.
Definitely a feature we'll want to create eventually, though.
The more I thought about this, the less difficult I found this issue. With the options
class... we can easily export all their customized settings in lightweight metadata. When they reload the tree, it just plugs back into our options
object and begins functioning from where it left off. We don't need to store all the custom functionality (which is obvious to me now).
Then, we just need to save the position of their nodes. The edges and everything else can be redrawn by the treeviewer each time they load up.
Allow a user to upload a tree and return to it later for further edits