-
Notifications
You must be signed in to change notification settings - Fork 22
Consolidate auxiliary information about nodes into getData/setData calls #393
Comments
Sounds like a good idea. Can I propose that we call it metadata and not data? |
Sure, that works for me. The java object interface would be something like
and the nef API interface will be
For simplicity, if you ask for metadata that is not set, you get None (or null) as a response. |
So net.get('name').metadata['key'] = value
value = net.get('name').metadata['key'] I'm not really attached to either way, just putting it out there for discussion. |
That would be an option, but I don't think there's a decision yet as to what |
Hah, yeah for sure 😄 Friday's discussion! |
The idea here is to get rid of the bizarre global variables that serve to associate some sort of information with a particular node in the network. In particular, we have
hrr.Vocabulary.registered
timeview.watches.FuncRepWatchConfig.config
which can both grow without bound, and have no way of removing elements when a network is closed.
This capability would also be able to get rid of the setDocumentation abuse that happens in spa.bg and spa.thalamus
Another use case is storing the x/y/z location of a node
This system should also have an interface to the nef API, allowing something like:
The text was updated successfully, but these errors were encountered: